Hi guys, how are you? Hoping to get some advice over here regarding the obnoxious error "RECORD_HAS_BEEN_CHANGED" that happens (at least to me right now) when i save a Sales Order using a M/R script type. Is there a way to avoid getting that error? Thank you!
s
Stuart Anderton
12/19/2023, 6:15 PM
Check what workflows or scripts run on save; if you have multiple After Submits which change the source record then they often crash over eachother.
b
Berenice Domínguez
12/19/2023, 6:16 PM
I thought that was a big piece on that error happening. :(
Berenice Domínguez
12/19/2023, 6:16 PM
Thank you!!!!!
s
Stuart Anderton
12/19/2023, 6:18 PM
The other one I hit is when you make sublist changes on a transaction which change the transaction status, eg close a line which results in the whole transaction being closed.
b
battk
12/19/2023, 8:52 PM
if you are consistently seeing RECORD_HAS_BEEN_CHANGED, the likely answer is that the performance of the record has been destroyed by after submit workflows/user events
battk
12/19/2023, 8:53 PM
is extra common when the user events use N/task to queue a task which then ends up running the same time as the original chain of user events/workflows since it takes so long to save the record