Hello,
I am looking for help and/or guidance on why I can't write use a table as a data source in PowerApps if that table has triggers, and I am looking for a workaround. Triggers are so common that I'm a bit flabbergasted that this problem exists. Here's my issue:
I have some tables that I am using as a source for powerapps. the app I built has no issue querying the tables to build galleries and edit forms, but I can't write to the tables because each has a trigger. I disable the trigger, and viola, the app now works with no issues other than that now my database business logic is shot to hell because the triggers aren't running. I know there is nothing wrong with my triggers, as when I update the tables using SQL Server Management Studio they execute fine. I saw on some forums that as of this spring PowerApps "did not support tables with triggers". Also, there were no workarounds available, other than "not using triggers" resulting in a pathetically underpowered and, quite frankly, useless solution. If the triggers are executing entirely server-side, why would PowerApps care what they do?
My triggers run after both insert and update, and some of them have no criteria while others are contiditional based on text in the inserted row.
I would love to know if other people have found a way to adjust their triggers so that they work. I see no way of using a "stored procedure" to accomplish the task.
I appreciate the advice and input.
Thank you .
