Reply To: RM00101 Custom Trigger Conflict

  • Kerry Hataley

    August 21, 2023 at 10:58 am

    Hi David,

    I am thinking that the issue steams from the fact that triggers are NOT executed once per row, but only once per DML operation. So you need to explicit out the triggers. This means that you ALWAYS should have individual triggers per event type. Meaning a trigger of the insert, update and delete. Each need to have their own definition. This hold true when there are other triggers attached to the table. I have seen this issue with Paramount and their triggers.

    Also remember to exclude the Dex_xxx from updates, since this will fill your audit table when doing maintenance routines.

Welcome to our new site!

Here you will find a wealth of information created for people  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!