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.
I had to replace all the triggers for procedures to manipulate log tables 😕
This is really ridiculous. It's been over 4 years since first report of this. Not communicating with your users is a recipe for disaster. Triggers are common in many applications and you're telling us MSFT can't figure this out after 4 years? That doesn't feel like a robust solution to me. You do know you have Azure Data Sync that uses triggers so .. your own product will not work with your own product. Is anybody even paying attention to this channel?
Dear PowerApps Team,
When will this issue be addressed?
We're using powerapps which connects to the MS SQL database of our systems from a different vendor. .
But unfortunatly some tables use triggers in the newer release of our other system (to which powerapps connects) which renders the powerapps (in which we've invested a lot of time) useless.
Why is this taking so long to solve?
I echo the need to fix this bug. PowerApps is not cheap to use or develop in. We've invested monetary and time resources into learning and developing PowerApps solutions only to encounter this unexpected barrier. We are faced with either abandoning PowerApps as a development tool or with modifying our database tables by disabling triggers and creating labour intensive workarounds. Both products are by Microsoft and both are expensive - this kind of a barrier is unacceptable, to put it mildly.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.