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 more news on this??
This deserves another bump...
I am also facing this issue, as I try to call a stored procedure from a trigger, anytime my powerapp updates the table where the trigger is stored.
It is ridiculous IMO that Microsoft has marked this "feature" as PLANNED and +2,5 years later there is no update about it.
Been working with PowerApps for a few months and very excited about it, but this is disappointing.
Can someone PLEASE just give us some information about this bug?
Support for SQL triggers is essential.
Microsoft please provide an update on the resolution of this issue
To echo many of the above comments, we are excited about PowerApps but are cautious/skeptical since triggers is such a basic feature of SQL Server. This bug was discovered in 2016 and we are now in 2020. Is this status quo for bug resolution with PowerApps? Any updates???
Is there any update on this issue?
Gotta bump this! Having to use a SQL Stored procedure to get around this is really not a good solution. MS, please consider fixing this issue for us.
Happy 3rd anniversary, planning item.
03-13-2017 06:19 AMStatus changed to: PLANNED
Be ashamed of yourselves...
Hi @Audrie-MSFT ,
This idea goes back to 2016. Is there any chance for an implementation ?
Most of the times, Powerapps is used as 3rd party app to manage easily an sql database or a vehicle to distribute data inside O365 users in a friendly way. For some companies the SQL is directly managed by ERP software, which we cannot change the structure, like deleting triggers. So in order to take advantage of powerapps we do need this feature working. Otherwise we're limited to tables without triggers.
Please do take into consideration.
I agree with the other folks here. Being able to build Power Apps with databases that have triggers is a critical part of our use case. Are there any updates on this?