Enable use of triggers in Azure SQL Tables

[Harm]

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.

[DanBoehm]

I'm guessing that this is because of the error here,

https://blogs.msdn.microsoft.com/sqlprogrammability/2008/07/11/update-with-output-clause-triggers-an...

I ran into this with an on-premise SQL environment using the gateway.

[gmathias]

Same issue here. I have an on-premises gateway and SQL server, so I was able to run SQL Profiler and see the UPDATE statement that PowerApps generates -- it does have an OUTPUT clause without INTO clause.

[Anonymous]

Essential piece of functionality with a tool like PowerApps to be able to use triggers on the target data source. Surprised this is being treated like a feature rather than a Bug.

Any clues on timeline for this. It's a bit of a showstopper for us as we really don't want to be introducing messy workarounds to this.

[GS]

Any clues on a timeline yet? Crucial for our adoption rate for powerapps versus native stuff.

[FredForest]

Same here, this is a showstopper for us at the moment

[Shegs]

If this is output clause related then i am having a similar issue with calculated columns.

updating a table returns the error about output inserted.[calculated column]

commenting to be kept aware of when/how this is resolved.

[rsoeagnie]

Any UPDATE on this?

We have triggers for audit-log purposes so this is a show-stopper

[Anonymous]

Any timeline for this?

[DataJunky]

We were excited when initially looking at PowerApps, then ran into the trigger issue on a simple app.  That stopped us cold.  Hopefully it gets resolved.