Forum Discussion
Hi Michael___C
You can store much more than 5000 items per SharePoint list if you set your indexes right. And SharePoint lists automatically provide you with forms, versioning and automatically propagated modified/created fields.
But you will certainly get issues with large datasets sometime in the future if you treat SharePoint lists like a database. They are meant for collaboration use and not to be used like a database.
If you just use the list to create views that filter by a "team" field and by a "date" field (and both are indexed) (and each resulting view has not more than 5000 Results), then lists should fit your usecase.
If you don't want your users to be able to edit items in the list, then go to "Gear"->"List Settings"->"Permissions for this list". Here you click "Stop Inheriting Permissions" and grant just "Read" Permissions to your members (instead of the default "Edit" Permissions)
But take a look at Dataverse Tables and a PowerApp.
Dataverse can handle large datasets and queries much better, you can easily update the data through Dataflows and visualize it using Power BI.
It also has automatically propagated modified/created fields, but no versioning. And you have to create your Forms and Views in PowerApps.
Best Regards,
Sven