- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2019 07:02 AM
Hi everyone,
I'm running into an interesting situation here.
I noticed in our system that the Standard Change Template Version field in change_request is inactive and I want it active. So, I went into System Definition > Tables, searched for change_request. In the dictionary entries, I searched for std_change_template_version field and changed Active from "false" to "true".
Simple, right? Well not so much.
When I go into a business rule to have the Filter Condition to use the Standard Change Template Version field, it doesn't exist.
Any idea on what's going on?
Solved! Go to Solution.
- Labels:
-
Change Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2019 02:17 PM
I received the following solution from ServiceNow support:
Standard Change Template version[std_change_producer_version] field is in sys_dictionary with active=true, but also staged=true which should not be the case. This may be fixed by setting staged=false for this entry. 'staged' is a flag set when field is in the process of being created - for some reason it was not switched off in your instances. Staged=true will override Active=true. Fields marked as staged will not be used in the platform.
- Add Staged column to the list view in sys_dictionary.
- Change the value from true to false from list view.
Staged = false
Hope this helps someone else with the same issue.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2019 07:51 AM
Hi,
Do you mean like this:
Works and appears for me.
That field on change_request is actually a reference to another table called: std_change_producer_version
Perhaps you can look that over, but OOB, it should be there.
This is from my Personal Developer Instance which is on Madrid.
Please mark reply as Helpful/Correct, if applicable. 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
03-20-2019 08:03 AM
Hi Allen,
Yes, that is what I mean. It works in my personal instance as well but not in my company's instance.
Here are the screenshots from my company's instance. You can see from the first screenshot that the field is active.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-20-2019 08:31 AM
I would compare between your PDI and this instance and see where there may be a difference. As stated above, this field is actually a reference to another table, so you may want to look there as well.
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
03-20-2019 02:17 PM
I received the following solution from ServiceNow support:
Standard Change Template version[std_change_producer_version] field is in sys_dictionary with active=true, but also staged=true which should not be the case. This may be fixed by setting staged=false for this entry. 'staged' is a flag set when field is in the process of being created - for some reason it was not switched off in your instances. Staged=true will override Active=true. Fields marked as staged will not be used in the platform.
- Add Staged column to the list view in sys_dictionary.
- Change the value from true to false from list view.
Staged = false
Hope this helps someone else with the same issue.