Version loading was stopped by DictionaryUpdateLoader
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-06-2014 09:47 AM
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
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2014 09:00 AM
Ah... thank you for that! I appreciate it! And that solves this for me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-09-2016 04:12 AM
The link to the answer does not work. Can anyone please provide the details of the answer here? Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2016 11:31 AM
Unfortunately, the link now takes you to Evanios - Dedicated to evolving the way business services are managed and I can't find the specific article. I'm guessing since it's been about a year the site's been updated. Please copy its contents here or point us to where this information exists today. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2016 09:37 AM
This is the PRB that details the issue, with workaround (or at least a way to verify if the error is a false positive): PRB602168
If this answers your question, please mark this as the correct answer. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2014 09:06 AM
Good that you were able to resolve the issue.
Not related to this issue.
But generally as a good practice when pulling update set from other instance, the "User (Credential)" used in pulling the update set should have "admin" role.
Thanks,