I'm trying to save a form in SQL, but the message is showing that there is no column x in the table, but it does exist.
When saved without the specific column, the application registers and "null" appears in the specified column field.
Solved! Go to Solution.
This is an inner exception being thrown when the app is trying to run some stored procedure. You can see it's a server response so it's not likely an error with the app itself or a given expression, although always possible.
The most likely breakpoint is the stored procedure in question. You can look to see if there are syntax errors, maybe there are other deleted fields still being referenced in there. You'll also want to look for special characters in both the SPROC and your data, anything that could possibly interrupt this.
You can try some "toggle" type steps, as well...
If this remains persistent even with this troubleshooting, you can navigate to the Power Platform Admin Center and set up a support incident. This may not ultimately be a PowerApps issue but we can make certain.
Let us know!
We followed the steps, remade the connections and in our database we don't have Stored procedures, triggers, etc. And the error persists.
I appreciate your feedback and we will set up a support incident on that.
Check out the on demand sessions that are available now!
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Features releasing from October 2020 through March 2021
Check out the Power Platform Community Highlights