I setup a gateway and connected to it a couple days ago successfully in PowerApps, but this app does not seem to have been saved
Since then I have created a new app but am seeing the following error when trying to list the items from a table in the database:
"The specified records was not found. Server response [dbo][tableName] failed: something went wrong"
PowerApps can see the Connection, and can see all the tables in the connection, but it just can't seem to find any records in any of the tables.
I have tried a number of other tables in the database
I have tried recreating the App
I have tried recreating the Gateway and connection
I am able to see records if I setup a PowerApp Entity to the same gateway configuration
The same connection created for PowerApps above, works perfectly fine in Power Automate in a small test I created
I have seen PowerApps may not like a key made of multiple columns, but I believe this table's key is single int column
Running out of things to try, if anyone has any ideas
After registering the issue (and lots of log sending!) with Microsoft they have contacted me to confirm that the SQL Server connector was the issue and "deployment is now completed for all regions and SQL connectivity issue is resolved."
I tested and can confirm that this bug appears to be fixed in the new authoring version 3.20085.19
@Anonymous
You absolute blinder/hero/gem/star/legend!
I've been battling with this since Monday and that's EXACTLY what it was.
Oh my days. I need a drink.
Thank you!!!!!!
@LeonM wrote:When you try to disable the feature, you will get an pop-up that you're not able to disable it before you've removed the connected SQL tables.
Good luck!
Yeah, and as I found out last night, it is not only the direct SQL Servber connector in an app, also if you a flow pushing information to the app that has to be removed.
Yeah, and as I found out last night, it is not only the direct SQL Server connector in an app, also if you a flow pushing information to the app that has to be removed.
It is not related to an older version of SQL Server, we are using SQL Server 2016, on a gateway. Probably this latter element the culprit, MS wants to push more setup in azure.
Thanks for the suggestion though.
It was suggested above that this may be related to gateways connecting to SQL server 2012.
Unless someone can confirm it is happening with newer versions the "fix" could be to upgrade the SQL servers to 2014 or later?
When you try to disable the feature, you will get an pop-up that you're not able to disable it before you've removed the connected SQL tables.
Good luck!
In order for it to toggle it off, we have to remove every SQL Server connector in every app?!?
I have a few broken apps right now with that error message.
Anyone knows if Microsoft intend to fix this asap?
Regards,