cannot have any enabled trigger if the statement contains an output clause without INTO clause

[DaniSeara]

Hi.
I'm trying to update a record to a SQL Database and it is imperative that the destination table needs to execute an update trigger.
Howeever, I receive the error message  in the subject.

I was trying to avoid the able, creating a view on top of it, but Power Apps do not recognize View as data sources. Any idea? Must be this reported as a bug? Could the PowerApps team add an INTO clause?.

Anyway, we need to solve this during the next two weeks so. Could it be feasible?

Any idea will be so much appreciated

TIA

[Meneghino · Accepted solution]

Hi @DaniSeara

PowerApps does not yet support connecting to SQL Azure/ SQL Server views and does not yet support patching to tables with triggers.

There are other bugs in the SQL Azure/ SQL Server connector that you will find.

The product group is apparently working on this, but communication on progress, if any, is very patchy.

I am disappointed. 

[DaniSeara]

Thanks, @Meneghino. At least, you clarify me the current situation.

Thanks again!

[Nboss]

Any update on this situation??

[Meneghino]

UPDATE: Views are now supported but you still cannot modify data of a table with triggers

[zolle04]

any updates from the product team?

an estimate would be nice...

[jcd-csmm]

Training with AdventureWorks2016 under SQL Server 2016 for Developers.
A table with trigger (person.person) produce a DLM OUTPUT clause event if there is no OUTPUT clause in the trigger.


An anticipated date (even beta) would be nice. Cannot go in prod with this.

Thanks

[vverb]

Bump (I'm starting to feel like a necromancer; currently reviving every relevant post I find on this topic and it's becoming a small army)

Is there ANY update or ETA or workaround that does NOT require calling a stored procedure with Flow? 

Sincerely,

A desperate lord of the undead

[nyU]

Helloooooooo????

It's been almost 3 (three!) years.