At this moment it seems not possible to have triggers on tables in PowerApps.
Because of this, relatively basic apps with some logic in table triggers can not be created.
As posted by pretty much everyone else in this comment section, how is this not a feature that is already implemented? I understand there are plenty of moving parts under the hood but to leave this as "Planned" for years is simply unacceptable. If this is going to be implemented please update us. If it isn't let us know so we can find a long term workaround to this problem. Simply telling us to "Not use triggers" isn't a solution. These triggers are required for auditing so deleting them is not really an option.
I would like to echo this. Seems like a pretty essential function.
OMG facepalm! Years later after finally "PLANNED" it's still not in place? This is a showstopper for many apps, esp where the DB used for other (ie real - ERP, CRM, HR etc) purposes. I appreciate you want us to use Power Automate to fire a Stored Proc (woohoo!) but it's messy, not always feasible and likely more grind than a trigger.
Please sort this out, it shouldn't be difficult considering you develop both Power Apps and SQL Server! I expect the key issue is controlling the timeouts in case triggers grind, and keeping Power App moving - but that isn't insurmountable, just return an error on timeout!
This is a bug, not a feature; please call it what it actually is.
The inability to fire a trigger when writing to SQL table used in a PowerApp relegates the product to Tinker Toy status.
My discovery started with great promise and excitement and has since bottomed out.
PowerApps has so much promise...it’s a shame that it’s being held back.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.