You’re offline. This is a read only version of the page.
Announcements
6
Hi everyone,
I hope that the way I have structured this isn't too long winded. Please let me know if I need to edit this post to remain compliant with forum guidelines and recommendations.
BACKGROUND
I have a canvas app in development that aims to manage data and generate very basic administrative reports about employees within our Department. This app needs to be shared with a 5 member administrative team that will be using the app to
DATABASE
KEY QUESTION
I would like to know how best to set up the SQL Server connector in PowerApps to enable 5 people to read/write records to the database simultaneously?
I originally believed that when sharing the app, I would need to create new a new SQL Server connector for each individual and create a corresponding login and set up permissions in SQL Server when sharing the app in order for each individual to have his/her own access to the app as well as the database.
I've been doing some reading and it sounds like SQL Server connections are always implicitly shared.
Hopefully you have made it this far down and can share some insights.
If there are any other technical details or clarification I need to provide regarding the app's setup, please don't hesitate to let me know.
Thank you in advance for any information!
Yes, SQL is an implicitly shared connection so it is a good practice to use a service account for the credentials of the connection. This should have no effect on other connections in the app since the credentials are embedded in the connection itself.
This design is what MS calls "optimistic concurrency". Which means its assumed that no two people will be editing the same record at the same moment in time. Editing separate records concurrently is not a problem. Multiple users using the same connection account is common in SQL whether you are in Power Apps or some other programming language.
Share
Report
All responses (
Answers (
