- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 10:50 AM - edited 08-09-2024 10:52 AM
So I was trying to correct a mistake, we had added a field to cmdb_ci and it should have been added to cmdb_ci_server. However by the time it was realized it had already gone to production.
In an attempt to correct this I removed it from cmdb_ci in our dev environment and add it back when needed, use our data sources and transform maps to put the data back for all the appropriate servers and add it back to the forms it was needed on. I thought it was mostly working in Dev (at first), but when we brought the update set to our QA environment it produced an error "Version loading was stopped by DictionaryUpdateLoader for sys_dictionary_cmdb_ci_server_u_dr_tier". Which did allow it to commit however we noticed that when you try to use the filter in our QA environment the choices aren't listed:
They do show properly in the lower environment. And we were able to run the Data Sources/Transforms to repopulate the data (mostly, one option seems to have skipped over in the Dev environment, but populated properly in the QA environment), however when trying to sort the information where those choices should be is just --None--. Any suggestions of where to look to see what I've done wrong?
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 11:08 AM
When you first created the field and the choices, those choices are connected to that element (field), so perhaps during the development to delete and re-create, the choices weren't reassociated properly.
In any case, I'm glad that helped guide you properly. If my reply above helped guide you towards the answer, please consider marking it as "Accept Solution". Thanks! 😀
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 10:55 AM
Hello,
You'd have to evaluate the dictionary entry for this field and check and see if there are choices associated with it. I'm assuming it's a string with choices or a choice field, so on the dictionary, in the related list at the bottom, the choices would be there and those would also need to be brought up to the other environment(s).
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 11:05 AM
Actually I think I see it now, the choices were there... but the choice table is still pointing to cmdb_ci somehow. Not sure why that didn't carry up, but at least I see it now. Thank you!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 11:08 AM
When you first created the field and the choices, those choices are connected to that element (field), so perhaps during the development to delete and re-create, the choices weren't reassociated properly.
In any case, I'm glad that helped guide you properly. If my reply above helped guide you towards the answer, please consider marking it as "Accept Solution". Thanks! 😀
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-09-2024 01:51 PM
Included that same file in an update set, this time the choice table shows correctly and the filter works again.