Converted to SQL and having all sorts of problems

(0) Share

Report

Posted on by Nicci

194

Hi Hivemind! I need some help please!

So I have an app that originally was built using Sharepoint List and now I've converted to premium connector using SQL on prem via data gateway. Everything was working great until I started adding some extra columns needed, specifically a timestamp because I learned my power automate flows dont work for triggering on update/insert without a timestamp column.

I've had nothing but problems since adding a timestamp column. As soon as I did my patch functions all broke and I can no longer save anything into any of the tables (it was working before). So this morning I deleted the timestamp column just to see and now i'm getting an error that says "Error when trying to retrieve data from the network: Microsoft SQL: Invalid column name "LastModifiedTS". inner exception: Microsoft SQL: Invalid column name "LastModifiedTS".

This is the column I deleted. I refreshed the data in power apps, I removed it and added it back in, I tried refreshing the connection reference in the solution, and cleared my cache. I can't move forward; this is a nightmare just working on this app because i'm now on my second work day trying to get the app to work again after getting this column, that microsoft requires for flow, to now work.

Please help if you can!!

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Sort by

Verified answer

timl 37,262 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

Hi @Nicci

With on-premise SQL Server, it can often take some time for schema changes to be recognised by Power Apps. What can sometimes help is to restart the on-prem data gateway service.

If you've refreshed the data source in Power Apps, I'd wait a few hours to see if the error goes away.

Was this reply helpful? Yes No
Nicci 194 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi Timl! Yup thats exactly what happened. It was a wait time issue, however my other patch issue that was a generic 400 bad request error ended up being some triggers we have setup for created/modified timestamps. Its REALLY frustrating power apps does not insert/update/work with SQL that has triggers setup. That is a big failure because this app is to be integrated with a traditional web app and those triggers need to stay so now we're at a place we'll need to end up dropping the data in a table and running a job to move it on the database side which defeats the purpose of going to SQL since we can run the same batch with sharepoint list extract and not pay for premium....yikes Microsoft, yikes!

Was this reply helpful? Yes No
timl 37,262 Super User 2026 Season 1 on at

Like
a
(1)

Report
Copy link

Link copied!

@Nicci - thanks for the update. Yes, it's ashame that MS still hasn't added support for tables with triggers. If it's any consolation, I guess at least you've saved the cost of some premium licenses!

Was this reply helpful? Yes No
Nicci 194 on at

Like
a
(0)

Report
Copy link

Link copied!

hah naw more like we had to remove those triggers and handle it app side (not best practice though) because we gotta get this data off of SP.

Was this reply helpful? Yes No