Document Lifecycle Event (upp.user_account. Loaded) script exception: The document has been changed by another user, and your changes cannot be saved. You must discard these changes and reload the document.

[Former Member]

Hello all,

Does anyone know why are we getting this log when uploading collaborators to a Master Agreement?

The error message in the title of this post is the one we get in NWA. In CLM 'Import Data', we get a similar log:

"The Document has been changed by another user and your changes cannot be saved. You must discard these changes and reload the document [STANDARD_ATTRIBUTE_ID]"

Thanks in advance.

Cheers,

Laura

[former_member207877]

Hello Laura,

Inactivate all the Master Agreement related Scripts and then import the workbook.

If the issue doesn't occur then keep on activation one by one and check where the concurrency happening.

Mostly the above issue is due to concurrent modification.

Regards,

Raj.

[Former Member]

Hello Raj,

We already know that this issue is due to concurrent modification but unfortunately we cannot follow your proposal.

We need to know why this exception is happening on the Document Lifecycle event "upp.user_account.Loaded" and what it means.

Regards,

Laura

[former_member190023]

Hello Laura,

The issue itself (concurrent modification) usually happens because of incorrectly coded scripts. Generally, triggering a .save() action on any BO has to be done with great care and with a good understanding of script sequentiality.

From the information provided it's not possible to identify 'why' the exception is triggered, only that it is triggered by the User Account Loaded script.

The error message doesn't clearly identify which object it applies to, and not even the object type.

For example, you could update an MA which has a script that searches for an User Account. Then the User Loaded script could trigger the exact same error for a related RFX (if incorrectly coded)... and the error message would be the same.

For investigations you will need to:

- get more information out of the logs, including stack traces and identify the full chain of events that leads to this error

- search for any .save() statements in User Account Loaded script and check if the requirement to have that save statement is valid... also try to identify use-cases in which the save statement could be in conflict with script sequentiality.

Hope this is helpful.

Bogdan Toma