Unanswered

Trigger on SQL Server

(1) Share

Report

Posted on by CS-07032256-0

Honestly, it seems insane to me that PowerApps cant update or insert on a table in sql server if it has a trigger. I'm not even sure how this is a restriction because shouldn't the two be independent? When can we expect a fix for this? I am going to try and create a stored proc as a workaround, but can someone explain why this is and when it will stop being an issue? The powerapp is only one of many ways to get data into the DB so the trigger is critical for data integrity.

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

lbendlin 8,474 Super User 2025 Season 2 on at

Like (0)

Report

From what I understand the concern is that the inserts could trigger (pardon the pun) a chain reaction that PowerApps cannot stop.

Also note that you cannot insert rows into an on-prem SQL database anyway. You can only run stored procedures.

Was this reply helpful? Yes No
Michael E. Gernaey 53,335 Super User 2025 Season 2 on at

Like (0)

Report

Hi @CS-07032256-0

You said,

Honestly, it seems insane to me that PowerApps cant update or insert on a table in sql server if it has a trigger

Sorry its 313 Am and I am on high doses or muscle relaxers... but I am not following what the trigger has to do with doing an update?

And personally, I would, for security always prefer to use the sproc myself but what I would say is

Also, I would say, if you are not happy with how something works, you are better to go add it to the Requested Ideas, so people can up vote it, or go find it there probably is already hehe, and upvote it :-)

Was this reply helpful? Yes No