We’re looking for the best way to prevent the Error: Another process has updated the 'SOOrder' record. Your changes will be lost when our integration writes back an external ID.
When a users saves the first SO line it creates a push notification and creates a record in our external app. The ID generated in that App is then written back to the External Ref number on the SO which will be used to stay in sync with the external App.
However if a user continues to add lines they have to refresh the SO.
The current thought is to create a customization that creates a table that will store the SO GUID or Order Type and Number and our external ID.
Then have the GI for the push notification relate to this new table.
Any other ideas on how to prevent this issue?
Answer
Prevent the Error: Another process has updated the 'SOOrder' record. Your changes will be lost. when writring back using the API
+6Best answer by markusray17
In your case I would probably recommend just tracking the link in a separate table. But there is PXAccumulatorAttribute(https://asiablog.acumatica.com/2019/02/concurrent-update.html) if you want to go that route.
In your case I would probably recommend just tracking the link in a separate table. But there is PXAccumulatorAttribute(https://asiablog.acumatica.com/2019/02/concurrent-update.html) if you want to go that route.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.