Commiting update set error: Version loading was stopped by DefaultUpdateLoader

[peter_repan]

Hi all,

I was moving update set from Dev to Test with changed assignment rules on incident and sc_task table.

Assignment rules for Incident table has been applied correctly, but rules for sc_task table not.

I got a following error in commit log : "Version loading was stopped by DefaultUpdateLoader" for all assignment rules records for sc_task table.

Any ideas what could be wrong?

(by the way, instances have exactly the same version)

[Pradeep Sharma]

Hi Peter,

As far as I know that is a false positive error. Please refer the below thread for more info.

https://community.servicenow.com/thread/165127

[peter_repan · Accepted solution]

Issue was probably caused by Data Policy on Assignment rules for sc_task table. One of the fields was mandatory, but empty, so commit of update set produced error.

The message in error log was not very helpful : /

[HarshKaushik]

Hi Pradeep,

I have a query related to the same issue for Custom(Scoped) Application demo data. While creating application files from "sys_user" table for demo data of a scoped application, system is aborting the action and throwing an info message - "ServiceNow prevents publishing records for the table "sys_user" because they can potentially cause a security risk when installed on other instances".

Looking at the code, there is a servicenow class which is not exposed - SNC.MetadataLinkUtil.isTableMetadataLinkExempt(current.getTableName())

Could you please help me in identifying - why system does not allow to create application files(for demo data in scoped application) from "sys_user" table while it is working fine for "sys_user_group" table.

- Harsh Kaushik

[Imran Makandar]

Harsh - platform does not allow capturing sys_user record as demo data because user account holds password which is sensitive information and sys_user_group just holds group information without any sensitive information.