Added Column to SQL table but not showing in flow.

(5) Share

Report

Posted on by bkrlee1

Hi All,

Apologies as this is probably something very easy but I can't for the life of me find it.

I've created a flow which connects to an azure sql database successfully, It creates records and updates them. I've added another column to the SQL table but the column is not showing in flow. It's just a varchar(50) column. Is there a button to update the schema of the table so it shows as a parameter in the sql update action on flow please? Don't fancy recreating the whole sql part of flow everything I add a new column lol.

Many thanks.

Categories:

Using connectors

I have the same question (0)

All responses (46)

Answers (0)

v-yamao-msft on at

Like (0)

Report

Hi @bkrlee1,

When testing this issue with SQL Server on-premises, the newly added columns could be synced to the flow after refreshing the browser.

Could you try to refresh the browser or wait for a moment to sync the table changes?

I guess it might be a sync issue.

Please let me know if you are still having the issue.

Best regards,

Mabel

Was this reply helpful? Yes No
Lisa2 4 on at

Like (1)

Report

Hi @v-yamao-msft @bkrlee1

I'm dealing with a similar issue as well, however with deleted columns from a SQL table.

I've deleted columns from a table in an on-premises SQL Server database, and the updated columns are not disappearing in the flow. This is while I'm using the SQL Server "Insert Rows V2" connector.

Is this a known issue? How long should a sync take to occur?

Regards,
Lisa

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

I've been having this same issue for a few months. Recreating the connection to our on-prem gateway certainly does fix things, but that's becoming more of a hassle as we build out more Flows. Is there any update on this issue @v-yamao-msft @v-bacao-msft?

Was this reply helpful? Yes No
Reigningfear 139 on at

Like (2)

Report

Hello,

I have encountered this very issue as well with an traditional SQL database. I added columns after creating my connection and they do not show up. After recreating my connection, the new columns showed up. Prior to that, I refreshed my browser and toggled between different SQL connections to no avail.

Posting this in the hopes it'll get some attention as this issue does not seem to be resolved thus far.

Was this reply helpful? Yes No
Community Power Pla... on at

Like (3)

Report

I'm having this problem too, surprised nearly 2 years later, this bug hasn't been fixed.

Was this reply helpful? Yes No
Peter_Groen 17 on at

Like (5)

Report

When I switch connections to a new connection (on prem data via data gateway), I can see the updated table with added columns. But, when I switch back to the connection I need, the added columns disappear. So this looks like a caching issue.

This is annoying and counter productive. It is totally normal during dev to change a SQL table. We cannot wait forever for the changes to come back in Power Automate. Fix it please!

Was this reply helpful? Yes No
Community Power Pla... on at

Like (3)

Report

Still not fixed...

Was this reply helpful? Yes No
visakh16 10 on at

Like (3)

Report

This issue is still happening. Tried changing few columns as well as datatypes for couple of them but still the flow is having earlier schema info and failing due to incompatibility. Have tried refreshing browser, opening in new incognito window etc. but still issue persists. Have to wait to while as of now to see the changes getting reflected in the flow which is pretty annoying 😞

Was this reply helpful? Yes No
Community Power Pla... on at

Like (1)

Report

I was able to get the connector to refresh my table's metadata by dropping the table, refreshing power automate (table disappeared) and then refreshing the connector and reselecting the connector. However, it took a while (30 minutes or so) before the table showed up in PA again.

I have not tried it but I assume that copying the table into a new table and dropping the old should also work and allow you copy your data back once PA is working again.

Was this reply helpful? Yes No
tomking-ueco on at

Like (2)

Report

I am reporting that this same issue is affecting me. I have a "PostItem_V2" API operation for Inserting into SQL on Power Automate.

When the flow was originally made, one of the fields was of data type "nchar(10)" and the string being written was of length 14. I have since changed the data type in the SQL table to "nchar(50)" so logically, the flow should now successfully insert a record into SQL from Power Automate.

Even with the action being re-created, the connection being refreshed, and the data type change on the SQL table, the flow action still insists that it requires the string to be a maximum length of '10', but the data type is 100% allowing length of '50'.

Dropping the table is not an acceptable solution. Copying the table over to a new one is not an acceptable solution. How can I get the Power Automate flow to recognize that the data type is different now, and therefore, the error should not be thrown?

Was this reply helpful? Yes No