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.
Any update on this please, really need PowerApps to work with triggers...
This makes the powerapps not work with tables in an SQL replication to/from Azure SQL database since it relies on triggers.
03-13-2017 06:19 AM
Status changed to: PLANNED
Hey @Audrie-MSFT or anyone who's listening at Microsoft,
This has been planned for almost 2 years now. Either give us an update or change the status back to under review or something.
Having triggers work would really smooth out any complex DAL actions that overcomplicate PowerApps control events. With no true code reusability across multiple screen for complex CRUD operations, this lack makes my apps a complete mess in some places.
+1 and bumping for this idea
I vote for adding trigger capabilities too. I was surprised that I couldn't put a trigger on the sql table updated by my powerapp. I can do a workaround, but it makes my PowerBI/PowerApp integration look pretty clunky.
Any Updates yet ?
Any news on this? For us this is a showstopper, because the database is already in place (Including triggers) with some legacy application running on top of it!
Hello @Audrie-MSFT ,
Is anybody listening?
This has the status planned since at least March 2017? That's almost 2,5 years!
The requested change is really important for us, while we're using a database with triggers on several tables, but now we can't use this tables because of this bug (I see this as a bug, not a feature)
Can you please update us on the status??
I have the same issue and it would be great to fix it in Powerapps
Come on Microsoft!!