Version loading was stopped by DictionaryUpdateLoader

[esioson]

I've created an update set where fields were reused in the Incident Management form.

I have (2) Non-Prod environments:

NP Instance "B" currently has the most updated development and I've exported an update set from it to import into NP Instance "A".

After commiting the update set, I get the following error in the commit log:

"Version loading was stopped by DictionaryUpdateLoader".

Has anyone seen this before.   I think it might have to do with us reusing an existing OOB field and redefining its type, however, I'm not fully sure if this is what throws the error above.

Thanks in advance,

Ernadel

[johndurden]

The links in this thread don't lead to an answer anymore. What was the solution here?

[smcdonaldaz]

I'm currently having the issue and it is NOT a false positive.  My fields are not being added to the table on the target instance.  It may be a false positive in some cases but not mine.  I am adding fields to the Facility Hardware table which is OOB and that may have something to do with it.  I can add the columns in my DEV environment and everything extends fine but when trying to get the fields over to my TEST environment it's a no-go.

[kushal Tayade]

Hi,

Please find below link for more information:

https://hi.service-now.com/kb_view.do?sysparm_article=KB0690132

[Aaron57]

Are any of the fields calculated or function fields?  If so, I think it might be the same issue as https://hi.service-now.com/kb_view.do?sysparm_article=KB0690132.  

[M Turner]

We've seen this error today, deploying updates (new sys_dictionary entries onto cmdb_ci table). The error was definitely not a false positive - we could not get the sys_dictionary entries created.

Traced it down to having the same named dictionary entry on a number of lower down extended tables from cmdb_ci. We have no real clue how they got there, other than developer error and must have been loaded through on an earlier release without us knowing. Maybe a clue to help others - check the field does/doesn't exist in a table extended from the one you're trying to apply the update to