cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
DaniSeara
Regular Visitor

Fail to connect to SQL customer database

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? 
TIA!

 

4 REPLIES 4
JRaasumaa
Memorable Member
Memorable Member

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)

 

https://powerapps.microsoft.com/en-us/tutorials/share-app/

 

What isn't supported?

  • You can share to a security group but not a distribution group.
  • You can share apps with users in your organization but not users in another tenant.
  • You can share an app from powerapps.com but not from PowerApps Studio. (Click or tap a share icon in PowerApps Studio to open powerapps.com).
  • You can re-share an app if you have Contributor (not User) permission to that app.
v-micsh-msft
Community Support
Community Support

Hi @DaniSeara,

 

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:

Share app resources

Regards,

Michael

Community Support Team _ Michael Shao
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

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.
TIA!

Helpful resources

Announcements
UG GA Amplification 768x460.png

Launching new user group features

Learn how to create your own user groups today!

Community Connections 768x460.jpg

Community & How To Videos

Check out the new Power Platform Community Connections gallery!

M365 768x460.jpg

Microsoft 365 Collaboration Conference | December 7–9, 2021

Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.

Top Solution Authors
Top Kudoed Authors
Users online (2,703)