Well tbh I actually LOL at @23:43, calling it 'low-code' development platform is really some "gimmick" Microsoft has put on about Power Platform... Correct me if I were wrong, they should have logic-app alike designer suite. Microsoft probably add ChatGPT on it after 1-2 years, and I believe I can have this workable function by just describing it to AI to help me building the DB update function without writing single codes... Regardless, many thanks for the effort for making this tutorial video.
Your implementation left me thinking of the Contribute column which may run out of space - especially if a large number of users have to be granted access. Would it not be far more durable to just add another record every time a new user has to be given access? Then the framework to be used is to go for a !IsBlank pattern when you query the SQL table and compare the logged in user email with the filtered rows of the SQL table. If the filtered table has a row count of 1 for the combination of queried item and user name, it means that the logged in user has access - in which case the item is added to the collection. To me, using the above pattern seems to be a far more durable solution especially as its scalable and will not run into problems where a large number of users are required to be provided access to a single item . Taking the point further, it would also cater better to situations where an existing access has to be withdrawn. In such cases, all one needs to do is to find the correct record and delete it - rather than run to string manipulation complications to first identify within the Contribute column and then delete a specific substring relevant to the users' email whose access needs to be withdrawn.
Hi Daniel. Please note that this method is not secure. Since you are using Implicit SQL connection. Any app user can use developer tools to capture auth token and query URL, then change the filter condition to impersonate someone else user ID. Should not be used on sensitive data unless you are using explicit connection with Row Level Security.
Thanks a lot for tutorial. I have a question, I work in an organization where there are several departments, is it possible to create an app only be visible for a certain department/group? and in that app I set permissions for the specific department for example and app for the finance department and there are admin users and non-admin users, but other departments can't access the app.
hi im trying to do something very similar as a teacher releasing grades and feedback to students online. thanks for showing this! Can a user (Shane) view another user (Ashlee) info from SQL table? or maybe SQL stops them from getting into that file? will this work using Excel instead of SQL? thanks for any help
Well tbh I actually LOL at @23:43, calling it 'low-code' development platform is really some "gimmick" Microsoft has put on about Power Platform... Correct me if I were wrong, they should have logic-app alike designer suite.
Microsoft probably add ChatGPT on it after 1-2 years, and I believe I can have this workable function by just describing it to AI to help me building the DB update function without writing single codes...
Regardless, many thanks for the effort for making this tutorial video.
Your implementation left me thinking of the Contribute column which may run out of space - especially if a large number of users have to be granted access. Would it not be far more durable to just add another record every time a new user has to be given access? Then the framework to be used is to go for a !IsBlank pattern when you query the SQL table and compare the logged in user email with the filtered rows of the SQL table. If the filtered table has a row count of 1 for the combination of queried item and user name, it means that the logged in user has access - in which case the item is added to the collection.
To me, using the above pattern seems to be a far more durable solution especially as its scalable and will not run into problems where a large number of users are required to be provided access to a single item .
Taking the point further, it would also cater better to situations where an existing access has to be withdrawn. In such cases, all one needs to do is to find the correct record and delete it - rather than run to string manipulation complications to first identify within the Contribute column and then delete a specific substring relevant to the users' email whose access needs to be withdrawn.
Hi Daniel.
Please note that this method is not secure.
Since you are using Implicit SQL connection. Any app user can use developer tools to capture auth token and query URL, then change the filter condition to impersonate someone else user ID.
Should not be used on sensitive data unless you are using explicit connection with Row Level Security.
Very helpful, exactly what I was looking for.
but if we do this, if they somehow have access to the site, they can view the full list right? is there a way to prevent that?
I like your implementation. Question: is it possible to do something similar but based on groups?
Thanks for sharing this, can the same thing be accomplished using a SP list as the data source vs sql?
Great presentation. Was looking something similar...
Thanks a lot for tutorial. I have a question, I work in an organization where there are several departments, is it possible to create an app only be visible for a certain department/group? and in that app I set permissions for the specific department for example and app for the finance department and there are admin users and non-admin users, but other departments can't access the app.
for my organization we use MS 365 and active directory.
hi im trying to do something very similar as a teacher releasing grades and feedback to students online. thanks for showing this! Can a user (Shane) view another user (Ashlee) info from SQL table? or maybe SQL stops them from getting into that file? will this work using Excel instead of SQL? thanks for any help