Additional list security settings: Turn off Edit in grid view in list settings > Advanced. Also set a custom permission level on the site and apply it to a permission group for the list that allows ordinary users to add/edit/delete as required, plus prevents them from creating their own views too. Turn off RSS for the list so people cannot subscribe to the list to get at list data without SharePoint forms.
I mostly use 'Users can only see and edit their own records' in Advanced settings too. And give a SP group (with a few people) full rights on the list.
We have an automated process for requesting SharePoint sites via a flow approval, which also creates the site (well, I created it so I'm biased!). Thanks for the great information!
Also, I've found it's easier to just use JSON formatting for SharePoint forms modifications (unless you use that cool technique to keep ppl from editing the list in SharePoint).
Great video! 👍🏽 Clear and insightful discussion on using SharePoint as a Power Apps data source. Definitely will help many to weigh the pros and cons. Thanks for breaking it down! 🔍💡 #PowerApps #SharePoint #DataSources
Great content and format of presentation. Agree with all points made on SharePoint. It would be really helpful if you could create videos on how to configure/setup Dataverse (you mentioned it’s a bit more involved) , differences from SharePoint (eg guid instead of ID), and column types to avoid in databerse (would you still avoid lookups in databerse for example) Thank you and looking forward to future content
Thank you for your positive feedback! I appreciate your suggestions on Dataverse content, and I'll definitely create videos on configuring Dataverse, highlighting differences from SharePoint, and discussing column types to avoid. Stay tuned for upcoming content, and feel free to share more suggestions. Your support means a lot! Join my free community for more content: www.skool.com/power-apps-community
16:03 oh yes. i can confim that 100%. by the way do not change the type of the column more than two times. i was playing around to see whats going to happen if one does ist, and it basically breaks the complete view of the list. however the data can still be created but not accessed by anyone over the list itself. there is a labe that just says "something went wron, try again later" or something similar.
Hi, I think I was able to do a workaround on one of the "CONS" which is "User wondering on your sharepoint data and modify directly". So what I did is to utilize power automate get,delete,add,edit items and made the powerautomate run only users using my account. From that flow all data are passed to power apps and used parsejson to put them on a collection. But the sad thing is i cant use Forms :D, so I made my own from scratch, then pass back the data using powerautomate again to sharepoint. I hope you get where Im going :P
Sure! SharePoint is primarily designed as a document management and storage system, not as a relational database. While it offers some features similar to relational databases, like lists and columns, it lacks key relational database characteristics. For instance, it doesn't support complex relationships like many-to-many or one-to-many without workarounds, and it doesn't offer the same level of query optimization or data integrity features that relational databases provide. SharePoint is more about collaboration and content management, whereas relational databases are designed for complex data relationships and high-volume data transactions.
🍬 Get my free video course, access to my free community
www.skool.com/power-apps-community ⬅
Additional list security settings: Turn off Edit in grid view in list settings > Advanced. Also set a custom permission level on the site and apply it to a permission group for the list that allows ordinary users to add/edit/delete as required, plus prevents them from creating their own views too. Turn off RSS for the list so people cannot subscribe to the list to get at list data without SharePoint forms.
I mostly use 'Users can only see and edit their own records' in Advanced settings too. And give a SP group (with a few people) full rights on the list.
We have an automated process for requesting SharePoint sites via a flow approval, which also creates the site (well, I created it so I'm biased!). Thanks for the great information!
Also, I've found it's easier to just use JSON formatting for SharePoint forms modifications (unless you use that cool technique to keep ppl from editing the list in SharePoint).
You mean integrating Powerapps to create a new form so users have to use the app. We do that. And we use JSON formatting as well.
@@DonCurrier great!
Great video! 👍🏽 Clear and insightful discussion on using SharePoint as a Power Apps data source. Definitely will help many to weigh the pros and cons. Thanks for breaking it down! 🔍💡 #PowerApps #SharePoint #DataSources
Thank you!
Nice discussion, but i think im still gonna use SharePoint as datasource for now. hahahaha (the licensing for the premium stuff is too hard T-T)
Dang, I should of been here for this topic! I could talk for days!😀
Awe... would have loved to have you in on it, man!
Great content and format of presentation. Agree with all points made on SharePoint.
It would be really helpful if you could create videos on how to configure/setup Dataverse (you mentioned it’s a bit more involved) , differences from SharePoint (eg guid instead of ID), and column types to avoid in databerse (would you still avoid lookups in databerse for example)
Thank you and looking forward to future content
Thank you for your positive feedback! I appreciate your suggestions on Dataverse content, and I'll definitely create videos on configuring Dataverse, highlighting differences from SharePoint, and discussing column types to avoid. Stay tuned for upcoming content, and feel free to share more suggestions. Your support means a lot!
Join my free community for more content: www.skool.com/power-apps-community
This is a good video. Very informative and helpful :D
Thank you, Jisa!
16:03 oh yes. i can confim that 100%. by the way do not change the type of the column more than two times. i was playing around to see whats going to happen if one does ist, and it basically breaks the complete view of the list. however the data can still be created but not accessed by anyone over the list itself. there is a labe that just says "something went wron, try again later" or something similar.
Follow the rules😊
thats a great discussion!
Thank you!
Hi, I think I was able to do a workaround on one of the "CONS" which is "User wondering on your sharepoint data and modify directly". So what I did is to utilize power automate get,delete,add,edit items and made the powerautomate run only users using my account. From that flow all data are passed to power apps and used parsejson to put them on a collection. But the sad thing is i cant use Forms :D, so I made my own from scratch, then pass back the data using powerautomate again to sharepoint. I hope you get where Im going :P
Nice workaround 👍
The answer for me is: All the time, my company does not use dataverse and we cannot setup a sql gateway quite yet 😂
We could help with that if its needed 😊
For a simple form, I just use powerapps to design the form.
Much helpful
Glad you liked it!🚀
I know SharePoint is not a Relational Database but I have no convincing argument to support it.
Can you please help.
Sure! SharePoint is primarily designed as a document management and storage system, not as a relational database. While it offers some features similar to relational databases, like lists and columns, it lacks key relational database characteristics. For instance, it doesn't support complex relationships like many-to-many or one-to-many without workarounds, and it doesn't offer the same level of query optimization or data integrity features that relational databases provide. SharePoint is more about collaboration and content management, whereas relational databases are designed for complex data relationships and high-volume data transactions.
Wait don't use people picker column type? So what do you use in place of people picker column in both the list and the power app?
You may want to avoid the People Picker column due to deletion issues. You can create a custom list that will contain the required users 😊
I will have to research how to do this. So use the office connectors and store as string in text column?@@PowerAppsTutorial
You can create a sharepoint list and add the users manually