 So Marcello asks, I have a text field multi-line in a list we've created. How can I store something like five megabytes of text in this field? Five megabytes of text? Unless you can compress it to 64k, you can't. I mean, it's pretty straightforward and Norm was nice enough to put the link in there. But just under 64k. Yeah, and it sounds more impressive than it is. It's almost 64,000 characters. I mean, you're trying to do the math on that to see if that's going to be five meg. It's not really possible. So I guess I would go back to what are you trying to achieve? Perhaps using the attachment feature in the list to the item might make more sense or having some other type of storage mechanism, maybe using a document library with the URL link column, any of those types of things. But you may have to work around because even if you were to get five megs of data inside of that column, it might be hard to interact with. What are you doing with five megs of text in the first place? I mean, come on, really. Is there a dissertation or something? I mean, copy and paste it into an image field. It almost has the feel of somebody trying to like UU encode a small file and put it in there. Yeah. What are you trying to do there? That's the name column. It's a really long name. Well, but I think it really goes back to it. If you were trying to do something that's beyond the scope of what that list was intended, expand the talk with the owner of that if you're not the owner and add a new column with a new column type, there's something that's relevant or what? Yeah. I mean, it was very specific about five megs of text. That is a weird. I think an attachment makes the most sense. Yeah. Right. I wonder if it's script. That to me sounds like a developer question. They always try to push things out of the box. Yeah. Just don't. Again, that's like how are you using the list if you're trying to use it for your code management? Wrong solution for that. Go use DevOps. Go and use your SEM platform. Don't try to use lists. Get your own free repository somewhere. Right. What is the classic? What is SharePoint slash list good for? And what is it not good for? Yep. Absolutely nothing. I was going to leave it on the box. Use SharePoint a database. Go. Yeah. That's actually a great topic. No, it's not. People still think that Excel is a great database. No. It's a valid thing. It's a question that keeps popping up, Sean. In fact, my content team, my marketing team, that's on one of the questions. They would love a guest post on that topic because people keep asking that question, the questions around that. Send me a note. I'll write it for you. It's a way to correct people on, like, no, it's not and this is why. And why would people ask that? What are people attempting to do? And how do you course correct them? Yeah, I've had jobs I've actually turned away where it was SharePoint looking for a problem to solve and they had a need for a relational database management system and they wanted to use SharePoint to address it. It's like, no, no, no. It looks and kind of feels like a database, but it's not. And though a list looks like a table, it's not, so. I think where it's cool though, is the citizen dev space. Like if you're building a power app, you're not really a developer and you're doing this on your own. You need a little bit of table storage. Don't kill me, Sean. But yeah, okay. SharePoint lists will probably do the job. That is a great point. That's exactly where it is. Like Sean, that topic, and I think what we're like, why I'd like to see that blog post-written is because when you talk about that, the citizen developer world and being able to go and build those automations, how are you looking at how SharePoint can be used and where that data exists? And sometimes it is. It looks like a database. So to put some elegance to Sean's grumble, because I completely agree with Sean's grumble, like a citizen developer creating a solution as a first cut of how to solve a business problem, sure, a SharePoint list totally works. But if this is becoming a enterprise-ready mission-critical application, it's time to take it out of the SharePoint list and put it into a database because the SharePoint list is going to break one day. Someone is going to go in there and delete a column and your entire solution will stop working. So check it out, Jay. These are the access to .0 databases of 10, 20 years ago that became production systems. Well, so two points. One, love, Jay, your gentle slam on Sean's inelegant responses. Two is exactly that. You have to be careful about this. It's just about why having good governance around citizen development is so important is because you go and build it as much as we want to talk about graduating it up to a more scalable solution. We all know that you go and build that rudimentary thing. It's going to find its way into the enterprise. And so doing as much as you can to establish the standards at the beginning with how we go and build these smaller automations because they don't always, we're not so robust in our practices to then re-architect or rebuild that solution to move it up. And let me point back to the history of SharePoint where most of why SharePoint grew like weeds is because WSS was free and it was people outside of IT installing it on a box, sitting under their desk, outside of the purview of IT and building solutions and then suddenly the CEO said, I like that report. He's like, make that happen and forced SharePoint found its way in in a poorly architected SharePoint solution. Not that that ever happens anymore, everything. Yeah. It's purposefully and elegantly architected. The cloud fixed everything. Yes. Yeah. We have crap that scales to unbelievable heights now. There's a great podcast title is like, crap that scales. I got a huge cloud. Microsoft cloud and metropolitan sewer district. Yeah. I got to make one last point about this whole citizen dev database thing that I think is a good direction and it's the dataverse for teams which being tied to teams is a whole different conversation but that is scalable. That is something that the end user as a citizen dev can just build and then when the real devs need to get involved and scale it to the enterprise they can upgrade it to full CDS or dataverse whatever we're calling it these days. That's the one. If those citizen devs know about dataverse. Yeah. That's part of the problem. Yeah. Someone should put a link to that dataverse stuff in that spreadsheet and then we can share it via the blog post in the YouTube link. Just saying. I'm just saying. I'm not pointing to anybody. And this is where You don't put like a giant arrow in post prod over Macs. Yeah. But this could also be another lengthy discussion where it's not about what IT controls but it's what IT does in the way of guidance for citizen developers. Because a detached systems analyst is not going to understand the business process better than the person who's in the business process. So I like the example that Jay used where the users finding a way to figure out their business problem. So how can IT? I don't know. Not support, not take over but give them that guidance or that guidance facilitation. Yeah. Yeah. Facilitation to move it into something like dataverse for teams. So nearly every presentation I give in the community, I have content that talks about the role of IT with Microsoft 365 and IT is not a tool installer anymore. We are a business enabler. So that's exactly norm. It speaks to exactly what you're talking about which is, if you think that dataverse is how the citizen tools should be built, you've got to make sure people know what it is. You've got to make sure they know how to use it. You've got to make sure they know why even though it's a little bit more complicated than an access database, you really should focus there and not the access database. Like if there are things you want them to do, you have to educate them on it and then you have to keep educating them on it. Like it can't just be here's SharePoint, it's under my desk and I'll talk to you in a year when I update it again. Like it, you can't do that. Well said. I'm probably the odd guy out here, you know, being the Azure person. Well, you're odd, definitely.