We just finished a Power App for a customer (In fact a MSFT area). We use their own SQL Azure Server, with the credntials provided. However, when they publish the application in thier environment, or try to open it locally, they get "to Work Correctly, the pp needs to connct to these services and features, and display the SQL logo and the name of the original connection.
I asume the error raises because the connection (and a couple of Flows), were originally defined in our PowerApps environment.
How we can solve this?. How we can deliver a Power App to a customer environment?
PowerApps isn't designed to be delivered outside the Office online environment it's built in unfortunately.
See the last few lines of this article (maybe things are changing but I fear not)
What isn't supported?
That is not error, but a reminder. In order to have PowerApps works correctly, it would need the user to first initialize the connection used under App built within PowerApps, including other services.
Adding another article for your reference:
Thanks Michael. However, there are another issues. The user added the corresponding paramaters, but now all the SQL Table references are lost. Seems like even when actually it IS the same database, the Power app do not recognize the same tables. 😞
This is my own replay, just as an update. Finally, the customer could add another SQL connection. BUT, all the referred tables are changed to [schmea].[tablename]_1. And I had to change them one by one.
I think it could be enhanced and allow to define the connection string DIRECTLY in the Power Apps File (even better, allow the user to link to other external connection storage, like SharePoint Data Connections library, or even, Azure Storage).
This is something the team must consider.
Seomething similar occurs with FLows.
Just think about it.
Learn how to create your own user groups today!
Please join us on Wednesday, January 19th, at 8a PDT. Come and learn from our amazing speakers!
Check out the new Power Platform Community Connections gallery!