For a gallery I have a connection to SQL database to get my list. In the SQL table I have added a new column and entered some data. When I try to refresh the connection from within powerapps, nothing happens. When I reference the table by name I get the error that the identifier could not be found (or something like this).
So, I deleted the connection entirely and made a completely new one. Same error.
Does anyone know what the issue might be?
I know for sure the column exists and that the name is spelled correctly. Just that the column definition isn't updated in Powerapps.
How can I force this update to happen?
Solved! Go to Solution.
Yup, it has a primary key that's auto-incrementing. I could see the column now, maybe it just needed more time...
I think it's strange because I both updated AND removed the reference from here without it recognizing the column definitions.
Did you remember to include a primary key in your table?
---
Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Hi @agneum
I think this has been buggy for quite a while. Is it on-prem SQL that you're using? If so, restarting the gateway can sometimes help.
Glad that's working @agneum. Out of interest, what kind of delay was there between you making the change in SQL, and seeing it in PowerApps? Was it 10s of minutes, or hours?
@timl It was about 15 minutes maybe, and that's after me updating everything in the left pane and re-adding the connection.
This is a structural issue when working with the onprem sql connector in PowerApps. Sometimes there's a delay with the gateway when adding new columns. The weird thing is that the new column does appear in the columnslist when adding a datatable but when you select it the datatable throws an error that the column doesn't exist. Seems like the new structure of the table is sent to PowerApps but the data doesn't match the new structure. After a while the issue resolves itself.