I'm working on a PowerApp solution which uses Azure SQL database backend. After the GA, I saved the solution locally and then saved it to production (default) environment of the customer. I recreated the Azure SQL Server connection for production (default) environment. I shared both the PowerApp and the connection to the users.
No matter how many times I retry this, the users are not able to click the Allow button in the dialog when they are trying to access the app from browser client.
Have any of you experienced this and found a way around it?
There is actually additional strange behaviour here: There should be only one connection instead of two. But on the other hand, I have another app with only one connection (shared with the users) and that doesn't work either.
Please help 🙂
I have been testing migrating apps from development to production as well. There are a few issues.
I found that I need to use Windows Studio to save/load apps from one environment to the next (all new environments/CDS databases). Using the Web Studio preview does not work it just hangs.
Once I have managed to save my app to the cloud (from Windows Studio, SQL azure connection), I cannot edit the app in Web Studio preview, though it will play. The error is:
So at the moment that makes the Web Studio preview almost 'unusable' in real workflows. It only takes 10 minutes to test the scenarios for dev to production, so it is very easy to see the problems. I avoided attempting legacy-to-new on purpose, just new-to-new.
Hi opax,
Please make sure that you have explicitly shared the SQL connection from PowerApps.com (go to connections details view and click on the share tab) and then check the issue.
Regards,
Mona
Thanks for the replies. I'm still unable to make this work. The allowing of the connection simple does not seem to work to other users it is shared with. I'm trying get help from the product group.