If something in Ice.Triggers is stopping a transaction, can I get around it?
Also, what the heck is Ice.Triggers?
If something in Ice.Triggers is stopping a transaction, can I get around it?
Also, what the heck is Ice.Triggers?
Ice.Triggers has code that runs based on trigger events on database tables (create a record, write a record, delete a record, etc.)
I’ve not delved into what triggers are set up out of box.
Thanks @GabeFranco !
So, these are server side then?
Correct, these would be attached to a table and a method (when creating a new record in OrderHed, execute code xxxxxx)
One of those is running into an issue, it could be doing something like trying to create a record in a related table that already exists. You might see some expanded information about it in the Application Server Log.