Corrupted App for export and sharing after recreation of connection

[LievenBoving]

Hello 

I have an app created in my organisation and I can not share it well. 

The app uses a local SQL instance via our gateway. But i wanted to convert my connection to use SQL authentication instead of Windows authentication. This was not possible to i created a second connection with same name. 

After that i had to adapt some flows and app connections but it worked again. But since then i can not export my app anymore and i can share it well with co-workers. (so it is blocking) 

They can not except because the connection is grayed out (disabled) and just mention "SQL Server"

Some printscreens to see what is wrong

Please tell me what you need to help me on this.

Regards Lieven

[v-monli-msft]

Hi @LievenBoving ,

There is no need to share SQL Server Connection, it is automically shared after you shared the App, check:

Share App resources

"

Some types of connections, such as SQL Server, are shared automatically, but others require users to create their own connections to the data source or sources in the app.

On powerapps.com, you can determine whether a connection will be shared automatically, and you can update sharing permissions. In the left navigation bar, click or tap Manage, click or tap Connections, and then click or tap a connection. If the Share tab appears, the connection will be shared automatically.

"

Would you please try to create a new app with SQL server connection and see if you could share the app correctly?

See if you have reached the limitation when exporting the app according to:

https://powerapps.microsoft.com/en-us/blog/powerapps-packaging/

"

If an app depends on a connection (such as a SQL connection w/ credentials) we do not currently support exporting the connection or credentials as a part of the package.

If you have an app that relies on a shared connection (like SQL), your only current option is to manually re-create that connection with the appropriate credentials in your target environment and select that connection when you import the package.

"

Regards,

Mona

[LievenBoving · Accepted solution]

Hello

I got some support from MS. The fix was to delete all flows and re-add them in the app. 

Kind Regards Lieven