Issue with Domain Specific Choice Lists

[Chris Sanford1]

I am trying to configure domain specific incident categories on the 'category' field. I have pre-existing global domain choices, and then added a new one in a specific domain. None of my choices are inactive. For an incident in the specific domain, I expected to see all the global ones, as well as the domain specific choice. However this does not seem to be the case. I only see the new choice in that specific domain, and the global ones appear on all of the other domains except that one.

According to ServiceNow's documentation on this subject at https://docs.servicenow.com/bundle/kingston-platform-administration/page/administer/company-and-doma..., I found the following paragraph:

From what I can tell this appears to be a false statement. I confirmed in my out of box developer instance the same behavior. Am I missing something here?

[Chris Sanford1]

Hate to keep beating a dead horse, but interestingly enough if you look at an update set after configuring a choice list it's pretty unique behavior. The related record of the customer update is actually a 'sys_choice_set' record, but the payload also contains all the child 'sys_choice' records. A similar thing happens with form sections. The customer update is a 'sys_ui_section' related record but the payload contains all the child 'sys_ui_element' records.

Also, it's the 'sys_choice_set' records which extend the 'sys_metadata' (application files) table. 'sys_choice' does not extend sys_metadata. I think I remember hearing somewhere that the official definition of configuration is an update to the sys_metadata table.

Anyways, very interesting conversation on the inner-workings of ServiceNow configurations at the database level.

[lalit007]

I agree... If a table extends application file (sys_metadata) then it is considered configuration else it will be Data. Update_synch attribute is responsible for capturing the records in the update sets, nothing more.

[Louis Savalli]

As best I can tell, here in 2022, that it's still a false statement.  I'm seeing current documentation say that you should be able to see global choice list items in lower domains, and other somewhat recent community posts seemingly agreeing, but my testing is not showing that.  I'm adding global choices, and they're not showing up in the choice list, and the Configure Choices from the right-click menu isn't showing it either.

[Prateek Gupta3]

Hi Louis,

Are you able to find the solution to this. Even, I am getting the same issue.

Thanks,

Prateek

[Louis Savalli]

No, we never did.  We ended up creating a custom field for domain-specific categories, and I think we used a reference qualifier to limit the choices per domain - not remembering exactly but definitely pivoted to a custom field.