Hello everybody ;
What are the limitations of using sharepoint list as a database instead of Dataverse?
Hi @gikido ,
Operationally, the main limitation in SharePoint is the non-Delegable nature of the Search or in functions (it will not perform a server-side query looking for instances of a string anywhere inside another string - it will however perform StartsWith or equals). Depending on your needs, this can generally be easily worked around with pre-filtering (and doing the search client-side). Large lists (over 100k or so) also start to slow down a bit, so it is not something you would probably use for large enterprise apps.
Of course, the cost is a consideration as SharePoint can be used Out of the Box, whereas Dataverse requires a premium licence for all users. The SharePoint interface itself can be a very valuable user query tool which you can also build Integrated Power Apps on to replace the standard menu.
I am a SharePoint user and have not found anything in the last six years across multiple customers I could not do on it, however the apps were in the main "custom" apps to perform a specific purpose.
This video from Shane Young is also probably useful viewing.
Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.
MVP (Business Applications) Visit my blog Practical Power Apps
Well, this question does not have any straightforward answer, it really depends on what you are trying to achieve with your application.
The most important difference is the speed and scalability when it comes to your org data size.
Working with Dataverse table is same as working with traditional database tables creating relationships between tables etc., while working with SharePoint lists you can create an application that uses few hundreds to thousands of records.
WarrenBelz
637
Most Valuable Professional
stampcoin
570
Super User 2025 Season 2
Power Apps 1919
473