Apparently this is was raised a couple of times a year ago. Using the Patch funktion to update a table that has a trigger on the SQL server. Unfortunatley we can not change or delete the trigger on the table. Is there by now any update on the issue or a possible workaround? We would like to use powerapps but obviously without the possibility to update a table it does not really make sense.
Thx,
Uli
Solved! Go to Solution.
Hi,
Currently this issue is still under developing.
A possible workaround is to take use of SQL Server stored procedure with Microsoft Flow.
Quoted:
"
The followings are some of the known limitations of using SQL connector
Stored Procedures cannot be invoked from PowerApps. A workaround is to create a Flow and invoke the Flow from PowerApps.
Insert and update to a table does not work if you have a SQL server side Trigger defined on the table. To workaround this issue, you can do either of the following:
Use a Stored Procedure
Remove the Trigger of your SQL table
"
Refer to this article.
Regards,
Michael
Hi,
Currently this issue is still under developing.
A possible workaround is to take use of SQL Server stored procedure with Microsoft Flow.
Quoted:
"
The followings are some of the known limitations of using SQL connector
Stored Procedures cannot be invoked from PowerApps. A workaround is to create a Flow and invoke the Flow from PowerApps.
Insert and update to a table does not work if you have a SQL server side Trigger defined on the table. To workaround this issue, you can do either of the following:
Use a Stored Procedure
Remove the Trigger of your SQL table
"
Refer to this article.
Regards,
Michael
Hi, this is what we have done as a workaround - stored procedures and flow. It does the job - though it is a little long winded to get to a result which should be done via the control. Looking forward to see this included in the edit/html control.
Any target date to solve this issue? I don't think this is difficult for Microsoft right .
Hello Mickael @v-micsh-msft !
Your post is from May 2018. Do you have any update on that subject from the dev team, please ?
Because your workaround seems fine until... Until I try to get my SQL connector on flow to work with my OnPremise SQL Server through On-Prem data gateway.
This is quite inconvenient, because my customer had to buy more licences to be able to run this getaway and it won't even work by default... as a workaround for things not even developped yet, though they were "under development"!
Thanks a lot for your help, I appreciate it.
Is there any plan to update this? It's now almost two years later and not being able to write to tables with triggers is a big deal. Yes, there are workarounds, but it's clunky.
User | Count |
---|---|
228 | |
103 | |
97 | |
57 | |
31 |
User | Count |
---|---|
283 | |
113 | |
107 | |
63 | |
63 |