 Mike says, I have a SharePoint list I need to archive to reduce the number of items in the list. I need to be able to recall the data on demand as it contains employee performance data that must be compiled and averaged at the end of the year. Any ideas? I love the list. Again, this is, we just kind of answered one of these previously, but in changing your views and using that magical little today option in your filters. If you look in the descriptions of the filters, there's two dynamic fields that one of them looks at me, it's in square brackets. So it looks at the logged in user. The other one looks at today and using that date as a dynamic date. So you don't have to constantly go in, you know, 30 days later and change the day it's referring to. So you can say, I need everything from today, mine it, something like everything greater than today minus or 365 or something like that. And it gives you everything within the last year. I did that just yesterday for some things. Any other ideas? No, the only other thing that I've really seen is having a column that's very specific. As you said, you can filter it that you can be archive. You can call it archive and then tick off everything that's archive as an actual, whether it's a radio button or a tick box or whatever you kind of create there and then that can just be filtered out of the list and then you can bring it back when you need to. So yeah, creating that kind of extra metadata. Yeah, I mean, the only thing I was going to add is like, again, going back to my the old school, you know, the 25 years ago, building out looking at data and having this, this issue. Was making sure that all we captured that we left within it was for us, it was like that 13 months. So you can look at January of 2022 against January of 2021 and that rolling cycle. Anything older than that automatically got archive got pulled back out of there. So making sure that you're only keeping what you need to keep. If you're still hitting the limitations. Sherry, I think you nailed it. It's, it's the create the views. Yeah, you can store the data, but you just, what do you really need to access on a daily basis? I mean, I also see where, you know, is it a year by year that you're keeping and that you can actually then export that data maybe to Excel have it there in a folder that's archive SharePoint, you know, kind of something like that where you get information you can still go back to it. Although it's not part of your main list anymore because you've kind of got rid of it and you've started it. But I have seen it where he got a year on year. We create a new list so that we haven't got a massive list. And then, you know, it's part of an, you know, a part of the archive process. If you need to be able to then go back to it at some point. The hardest part about that is pulling it back together because it looks like he's trying to do some data analysis on performance. So now you got to put it back together. It's a rolling, it's a rolling calendar. Yeah. And you could potentially then have, you know, multiple old repositories. How do you bring all of it together to see the, the history and then I, you know, for me, then I go is lists actually the right technology for you to use should you be using another system and like a proper, you know, system when it comes to performance. There's a lot of different awesome, you know, HR reporting performance type stuff that you could be using that's going to give you what you need. And it may be that list is not the technology for you for what you want to do. Well, there's a discussion. There's now right. Let's use the data. So pre dataverse. Right. I would have gone in and I would have taken some kind of workflow. SharePoint workflow when it was still a SharePoint workflow. Now it's power out of me created a clone list move them over and then what I had to go. For me, it would have Microsoft access to bring them back together and do a joint table and SQL query and blah, blah, blah. We don't have to do that anymore. Microsoft makes it very easy, especially with the dataverse. You know, you can now store that and it's it's meant for that SharePoint lists like, you know, can you build a database? Well, it goes back to the SharePoint is not a database. Yeah, if you're doing database things with it. Then that's exactly your point. Dataverse is there for that. It's an Azure discussion. Move it out of the list. Yeah. Do you say it all the time Christian, you know, should we is SharePoint a database. Yes, could we. Yeah. Not necessarily. I think you might need something a little extra potentially. For sure. It's Azure. And, you know, it just a paraphrase paraphrase spinal tap. Azure goes to 11 SharePoint. You're all the way up all the way up. Where are you going to go? Azure to 11.