 Frasier says anyone got any idea why you would use Microsoft Dataverse for teams over Microsoft lists or SharePoint for solutions in your environment? Also, do you know the difference between Dataverse for teams and full Dataverse? I love this question because I'm just really skilling up and I'm going back to my Microsoft Access roots here and my data background. There's probably three different answers to this question. First of all, the Microsoft lists are also SharePoint lists and those were never meant to be a database. They're a great list solution, but you wouldn't want to have tens of thousands of records in that list. Plus, you can't get the relational database where you can refer and create really dynamic data management solutions with that. So they're great for basic things that you would put like an Excel spreadsheet, for example, but you wouldn't want to have tens of thousands of records in that because then it becomes unmanageable. I love that guidance. It's like SharePoint is not a database unless you're using it as a database. Yeah, basic is my world, basic. So yeah, that works for me because less database. Yeah. And then the Dataverse for teams. So you have to understand the origin of Dataverse. It used to be the common data layer that's behind the dynamics infrastructure. And when you created dynamics, there's some basic tables that are like accounts, contacts, activities that come with the management of accounts and contracts and the CRM basics. And that's what comes free with the Dataverse for teams. You get those tables for free. The full Dataverse, you can create whatever solutions you want to. So that takes me to like my old SQL server days. I want to create a full blown data management customized solution to manage my data or like my access databases I use to create. You can create whatever you want. You can create those relational databases. You can create queries on those. You can create views of your data using the data that you've created. The core tables are the ones that came from Dynamics 365 for, again, contacts, activities, your companies, the different CRM based ones. The Dataverse ones you can customize. That's the short answer that I can come up with for that. But yeah, SharePoint is not a database solution. It's a list. Think of it like a Excel spreadsheet on steroids. And the difference between Dataverse for teams and full Dataverse? Does anyone know that half of the question? Yeah. The Dataverse for teams only includes those basic tables. You can't customize them. Okay. That's the free version that comes with it. I still love learning. I come along just so I can learn. I always love the terms of free. It's included for free. It's included in what you're already paying. You don't get it for free. It's included in a console. This is one of those from a governance standpoint. My thinking of this too is that are you building something for you or are you building something that is scalable for your organization? That's always the danger. The reason why you need to have, for example, with any Power Platform solution, you need to have a governance review, some kind of oversight of that. So many solutions that somebody goes and if my five-person team that we build something to help automate part of the way that we work, great. But for a manager to come in and be like, that's fantastic. Everybody should be using that. Well, that doesn't mean that that solution will scale. And so that's one of those things that are you building things with the purpose, the intent of it being used more broadly. There's a reason why you might utilize Dataverse for Teams rather than a list solution. Not that a list solution can't scale again. It's just like, what is the scope? What are you trying to accomplish and then architect the solution appropriately? And from what you said, question. Sorry. They highlight things like advanced data types, multiple transaction currencies, and mobile offline as things that are not available in Dataverse for Teams that are available in full Dataverse. Yeah. And then the big caution to kind of tag up what you said, Christian, is that Microsoft lists, you can create them now. Once they read random, they've always been SharePoint lists for over 20 years. Welcome to my world. It was nothing new. And they said, oh, Microsoft lists. The difference is now you can create personal lists that are stored in your, basically, your, your My SharePoint, which is your OneDrive. That's part of that storage. You have to be really careful when you create a new list where you create it. Because if it's something that's business critical, that if you win the lottery and run away, you've created it in your space, it breaks and it's gone for everyone else. You want to be real careful when you create your list that you're putting it in a place that's sustainable and scalable, like you're saying, because I see that a lot of people are like, oh, I created a new list. And I look up and I'm like, this is My SharePoint. I'm like, oh, no, you're building a, you know, time off, you know, request solution based on your stuff. And then those people leave the company, it gets broken.