cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
PowerAppUsr
Frequent Visitor

SQL Connector not working in Edit mode

Our PowerApp uses the SQL server connector to  connect to an on-premise SQL database and has been operational for over 7 months now. 

Since last week we observe that the app does not fetch data while in Edit mode and returns the following error message. 

The specified record was not found. Server Response [SQL Table Name] failed. Something went wrong. 

On using developer tools we can see the following message with a 404 error for the SQL calls. No HTTP resource was found that matches the request URI .

The last time the app was successfully edited was in the week of August 24th. 

The last successful edit was on PowerApp release 3.20082.19

The current powerapp release observed is 3.20084.9 

 

However the app works fine when run in Play mode and fetches data without any issues. 

We were able to replicate the issue with a new app and across different SQL databases on this environment. 

 

Interestingly the connections seem to be fine both in Play and Edit mode on a different environment which has a powerapp release version of 3.20083.24

 

Is there any other reported issue with the SQL connectors not working in edit mode. 

1 ACCEPTED SOLUTION

Accepted Solutions
AnotherNobody
New Member

I'm having the same problem. 

 

Turning off “Enable enhanced Microsoft SQL Server connector" in Advance Settings got it working for me.

 

If you need that feature, I also got it working by changing the Servername in the Connection from ServerName\InstanceName to ServerName:PortNumber.  That caused speed issues for me though.

View solution in original post

4 REPLIES 4
AnotherNobody
New Member

I'm having the same problem. 

 

Turning off “Enable enhanced Microsoft SQL Server connector" in Advance Settings got it working for me.

 

If you need that feature, I also got it working by changing the Servername in the Connection from ServerName\InstanceName to ServerName:PortNumber.  That caused speed issues for me though.

v-xida-msft
Community Support
Community Support

Hi @PowerAppUsr ,

Regarding the issue that you mentioned, I think this issue may be related to the SQL Table connection in your canvas app.

 

Firstly, please check if you have removed the SQL Table from your database, or made some changes to it. Please consider remove the SQL Table connection from your canvas app, then re-create a new connection to your SQL Table from your canvas app, then check if the issue is solved.

 

If the issue still exists, I think this issue may be related to Power Apps Version. Please consider edit your canvas app using following previous version of Power Apps:

https://create.powerapps.com/v3.20083.24.161674676/studio/

then check if the issue is fixed.

 

Regards,

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

Thanks for all the responses. 

 

as recommended by @AnotherNobody the issue was fixed by disabling the feature 'Enable enhanced Microsoft SQL Server connector'. 

On our test app with one screen and one table, it was a quick resolution to delete the sql data source , disable the feature and the add the sql data source again to resume editing. 

 

However this wasn't as easy on the existing production application with multiple screens and connections. Despite deleting all sql data sources, it kept indicating that all sql data sources need to be removed. The post by @balaji_mohan in the following thread https://powerusers.microsoft.com/t5/Building-Power-Apps/PowerApps-Connections-will-not-delete-Allow-... helped resolve the problem.

 

The steps we took to resolve.

1) delete all data sources including flows that use SQL server.

2) Save the app locally

3) open the app again from Local

4) Disable the feature 'Enable enhanced Microsoft SQL Server connector' in Advanced settings. 

5) Add the required SQL data sources. 

 

This helped us allow editing of the application again. 

 

Anonymous
Not applicable

This hurt, bad. We have over 2 dozen applications we had to emergency release. (each with plenty of db sources!)

This fix did the trick.  Why on earth did the app change without a release? Scary.

Helpful resources

Announcements
Power Platform Conf 2022 768x460.jpg

Join us for Microsoft Power Platform Conference

The first Microsoft-sponsored Power Platform Conference is coming in September. 100+ speakers, 150+ sessions, and what's new and next for Power Platform.

Power Platform Call June 2022 768x460.png

Power Platform Community Call

Join us for the next call on June 15, 2022 at 8am PDT.

PA Virtual Workshop Carousel 768x460.png

Register for a Free Workshop

This training provides practical hands-on experience in creating Power Apps solutions in a full-day of instructor-led App creation workshop.

PA.JPG

New Release Planning Portal (Preview)

Check out our new release planning portal, an interactive way to plan and prepare for upcoming features in Power Platform.

Top Solution Authors
Top Kudoed Authors
Users online (3,192)