RM00101 Custom Trigger Conflict
-
RM00101 Custom Trigger Conflict
I have been asked to track certain changes to the Customer Master and address tables (RM00101 & RM00102). I have created an “Audit” Tracking table and a proof-of-concept trigger for RM00101.
The After Update SQL Trigger doesn’t update data to the RM00101 table, but writes the Del and Ins records to the new custom Audit table.
Here is the weird behavior however; when enabled the trigger I see a “Violation of PRIMARY KEY constraint ‘PKRM00101′.
Cannot insert duplicate key in object ‘dbo.RM00101’. The duplicate key value is xxxxxx.”. GPPT tracing shows GP (zDP_RM00101SI) thinking an insert being attempted to RM00101. Why?The symptom in GP 2018 R2 is a GP pop-up “This record has been created since your attempt to create it. Changes won’t be saved.”
The discussion ‘RM00101 Custom Trigger Conflict’ is closed to new replies.