App with changed SQL database displays "The request operation is invalid"

[Yaronbs]

We have developed a PowerApss application which accesses an on-premise SQL Server database through several views.

Everything worked fine until the client dropped the database. Since they did not have a backup, they were required to re-build the database and specificaly the views.

We managed to correct all the errors in the app that existed due to missing objects or changed field names.

We are still faced with a red error in each of our main screens:

"The request operation is invalid.

Server response: The key didn't match any rows in the table.

clientRequestId: <GUID>."

This happens although data does show up in various controls and grids.

Publishing a new version or clearing the local PowerApps cache does not help.

It should be noted that we use collections to support offline scenarios.

We will be trying to get some additional data from the gateway or SQL Server, but any other ideas would be welcome.

[timl]

Hi @Yaronbs 

After re-building the database, did you refresh the connection in your app via the View > Datasources menu item? There should be a refresh option via the '3 dots' icon next to your SQL datasource.

If you haven't refreshed your connection, that might help.

[Yaronbs]

Thanks for the the tip.

I refreshed all the connections and there is no change in the app's behaviour (although it did not ask or allow me to save after these actions).

There is one view that a connection is pointing to that is no longer avaialbe (and not in use in the app); I'll see if deleting it helps.

[Yaronbs · Accepted solution]

Seems like adding the missing view in the database solved this particular problem so thanks!

[v-xida-msft]

Hi @Yaronbs ,

Could you please share a bit more about your issue?

Have you solved your problem?

After you remove the SQL Table from your SQL Server, the SQL Table connection you created before within your app would be invalid, even though, you re-create your SQL Table/SQL View in your SQL Database.

As an fixed solution, please consider remove the old SQL Table/SQL View connection from your app, then re-create a new connection to the new created SQL Table or SQL View from your app, then check if the issue is solved.

If you have solved your problem, please consider go ahead to click "Accept as Solution" to identify this thread has been solved.

Best regards,