cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
westerdaled
Resolver I
Resolver I

Unable to export a Power App due to a SQL Server connection sharing issue.

hi

 

I am testing out exporting a power App to our 3 evironments: Prod (default), Staging and Development & test.  The Power App is not in a solution ( this may come back to haunt me🙄). 

 

Anyway I have just exported the Power App from Live to Staging.  All looks good.

 

Next I want export the the Power App from Development & Test, into Staging.

However, when I go to open the Power App in development , I see this obscure message given I am the Power App owner!

 

SQLConnection perrmission error blured.png

I can click "Don't Allow" to get rid of this dialog and continue developing the Power App 

 

Unfortunately, I can't export the Power App due to this issue. 

 

Export Package error blured.png

 

I would like to understand how I can resolve this issue.  Note is is not a premium license issue as I have just extended the trial.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
westerdaled
Resolver I
Resolver I

We unzipped the Power App export file and looked for the connector Id meantioned in the above error message. 

As this was nowhere to be found ( in the various .json files) . we concluded the enviroment was the issue . 

Recreated the enviroment and imported the Power App , check this is now able to be re-exported 👍.

 

Is there a way of interrogating an enviroment and say remove a  dodgy connector?  Can we report on both the connectors used in the Power App and the target enviroment we wan to  import the Power App into?

 

View solution in original post

1 REPLY 1
westerdaled
Resolver I
Resolver I

We unzipped the Power App export file and looked for the connector Id meantioned in the above error message. 

As this was nowhere to be found ( in the various .json files) . we concluded the enviroment was the issue . 

Recreated the enviroment and imported the Power App , check this is now able to be re-exported 👍.

 

Is there a way of interrogating an enviroment and say remove a  dodgy connector?  Can we report on both the connectors used in the Power App and the target enviroment we wan to  import the Power App into?

 

View solution in original post

Helpful resources

Announcements
PA User Group

Welcome to the User Group Public Preview

Check out new user group experience and if you are a leader please create your group

Power Apps Community Call

Monthly Power Apps Community Call

Did you miss the call?? Check out the Power Apps Community Call here!

secondImage

Experience what’s next for Power Apps

See the latest Power Apps innovations, updates, and demos from the Microsoft Business Applications Launch Event.

Power Platform ISV STudio

Power Platform ISV Studio

ISV Studio is the go-to Power Platform destination for ISV’s to monitor & manage applications post-AppSource publish.

Users online (106,517)