 Mark has a question. I think this is a good one. We may not have all the answers here, but says, I have a list that is suddenly decided that it doesn't want to retain the setting for allow items in this list to be edited using quick edit in the details pane. I keep setting it to yes and can use grid view, but my next session is reverted to no again. Any ideas how it can force the list to retain the yes setting? I have some Office admin folk who are used to doing a quick edit in this list, and they're very confused that their spreadsheet isn't working. I don't have the will to try to educate them on how to get to the settings nor that it isn't a spreadsheet. They just want to get on with their tasks. Yes, they're calling it a spreadsheet, but it's a list. Mark knows that. That's good. I mean, I don't know why we retain it. Permissions. Yes. Yes. I don't know why I wouldn't retain the setting because I've never seen that, but the lowing in fruit is to create a view that's based on the data sheet view that there is no other option. You don't have to switch, and either you make that the default or the quick training of saying, hey, just change to the data sheet view. I have that a lot. When I work with large data sheets that I put into list, I listify them. Yes, we're going to make that a verb. I listify them and we're going to, when I want to work in that, I have a working view that I use that's in data sheet view, but not everybody needs that, not everybody needs that detail, and it's a personal view for me to use. Each person can have their own personal view. If you don't want to make it a public view, you'd have to teach the person to make their own view, or you could just make it a public view and then everybody has access to it all the time with the primary fields that they need. I have two questions, really. Two things there is, where was the SharePoint actually created? What are the permissions around it for the people that are coming in? Because he might have that, but they won't have that particular permission or the view to be able to go in and edit. Because if they haven't got those edits rights, then it's not going to work for them in terms of adding content. Permissions is a big one around where it was done, created, and is it through Teams? If they created it, and it's actually in Teams, because then the view is going to be different for anyone that's going in in the first place. It's a limited view because it's the app. Like the light version of this, not the SharePoint version, so how are they accessing it? Because they might not be accessing it through SharePoint. They might be accessing it in other ways. So there's lots of different ways to come at it. So it depends on what you're doing potentially as well. It could be some of the causes. I agree with Sherry. The first thing I would do is go and create that as another view, because if you're asking people to go through to change the view, who knows what's going on there? I mean, nine times out of 10, if it's anything of SharePoints involved. It's always a permissions issue. But to change that, set up that new view and see if the issue remains. If they could go in and do the quick edits that way, if they can't, then it's more fundamental. And it is you need to go and look at the permissions. Because that was my first thought is that you have the permissions in there. You have an edit capability, but somebody has higher level capability. They may not even have that level. So they may just not have the right permissions. Simple as that. Yeah. And it's just as many clicks to switch it to grid sheet view is to hit a dropdown and change it to another view. So it's not like you're making it harder for them. I know. But that would be one thing that I would do to try to root out this issue. To see if it's something else that's going on. If you create that as a public view that they can access without switching the view yourself and then see if they can do the edit. You know, maybe that fixes the problem or it's just a more fundamental permissions issue. And maybe they need to do a bit of training on lists in the organization on top of that. So they understand it's not a SharePoint and they can get how to actually work. Well, it's on a spreadsheet. Yeah, yeah, it's on a spreadsheet. It's on a spreadsheet. Yeah. I can help with that. Yeah. Yeah, exactly. We can all help with that one. Because, yeah, I mean, fundamentally, if people don't know what they're looking at and they don't know what they're editing or how they're supposed to edit it or what's involved, then they're going to get confused because they're going to click around and do what they're not supposed to do. See, I have this post-it note on my monitor that says lists are not spreadsheets. Also, SharePoint is not a database. Just as a reminder, I just leave it on there. Yeah. I'm joking, of course. List can be spreadsheets if you download them. That's the nice thing. And SharePoint can be a database. List can be spreadsheets. Yes. And I would say that SharePoint can be a database. It shouldn't be, but it can be. Yeah. It can be. The other thing I'll say is lists is also evolving. So there's little things that are going on in there at the moment because there's so many changes happening. It just could be a temporary glitch as part of an update. And that might actually rectify itself because there has been a few things happening across that space, too. So should we have started with? Have you tried turning it off and on again? Should that be? Yeah. We tried a new list. It transferred things over. A new list. A new new list. And the shameless plug to that point, the lists aren't new. They've been around for 20 years. They were just called SharePoint lists before. Now they call them Microsoft lists. So those SharePoint lists, if you go actually into SharePoint, there's a lot more functionality in there than meets the eye because how it's presented in lists and or teams is simplified because people wanted it simplified, but there's a lot of power there. It's been a while since I've done that, but early on with lists within teams, if I would get frustrated, I just found myself opening up within SharePoint and just working there. So that would be, that's another thing. Go and try that. Go and see if the problem is consistent over in SharePoint. Yeah, give them access to another list and see if the same thing is happening.