Unanswered

Power Apps SQL Server Connector Resource Not Found Error

(2) Share

Report

Posted on by RobDin

I have a well-established Canvas Power App that employs many SQL Server connections to an Azure SQL Server database. The app has worked well for over a year but in the last couple days we've seen instances where patch statements fail with the error '(TableName) Resource Not Found'. On different screens within my app I use the same patch statement with the exact same syntax. On one screen it works fine, on the other I consistently get the error. I've found I can remedy the error by removing the connection and recreating it. This fix gives me an uneasy feeling because this Microsoft product is now at risk of spontaneously failing without any notice.

Has anyone else had this issue? Is there a solution that you've used that can guarantee that this won't happen again? I've read about a retired feature to turn off enhanced SQL Server connections, could this be my problem? If so, what's the fix?

Categories:

Building Power Apps

I have the same question (2)

All responses (3)

Answers (1)

gmurnock 57 on at

Like (0)

Report

I too am seeing issues with the SQL connector with the same error, '(TableName) Resource Not Found'. Reading data is fine it is just an issue writing. Re-defining the data connection it will work for a couple of submissions, Patch function and Form submit, then give error again.

Was this reply helpful? Yes No
Verified answer

RobDin 69 on at

Like (0)

Report

@gmurnock

As I mentioned above, I was able to temporarily remedy this issue by removing the connection and then re-adding it. Unfortunately, this also means republishing the app and waiting for all end users to update.

After an email discussion with Microsoft's support team, it was also determined that I was using an old syntax of the Patch function that did not contain the Default() function on a new record insert to my database table. Being a PowerApps developer since 2020 you learn one way to do things you use so often. It seems odd to have to re-check function syntax for changes, but apparently using Default() became a requirement with a recent platform update. In conjunction with this change, I turned on the 'New Analysis Engine' at the same time; prior to the automatic activation.

I'm hesitant to say the problem is 100% solved (until some time has passed), but the issue has not come back since I made that change.

Was this reply helpful? Yes No
Suggested answer

Tim D' Spy 2 on at

Like (0)

Report

This kind of issue can be fixed by giving permission to the Stored Procedures, Tables & View that have been used in Power Apps. Adding also that if there are triggers, it should also be given permission.

- Giving the account the right execution privileges in SQL (Edit, Add, or remove for tables and to execute for stored procedure).

Was this reply helpful? Yes No