Domain - Calgary: Unable to create a sys_domain field on a new, custom table

[sbailey1]

(I found and reported this problem in September and have been demonstrating it to students in Domain Separation training classes, but had not posted it publicly. A former client emailed me yesterday about it, though, so I thought I'd share this with all in the MSP user group.

(attached doc has screenshots included)

UNABLE TO CREATE A SYS_DOMAIN FIELD ON A NEW, CUSTOM TABLE

Introduced in Calgary (glide-calgary-02-15-2013__cca4-04-19-2013_04-19-2013_2025.zip) was a restriction on the dictionary type field that limits the ability to add new sys_domain fields on custom tables to just ServiceNow employees with 'maint' roles. (PRB589498) The problem associated with this issue has been closed, so we can assume a fix is included in a later Calgary release or an initial Dublin release.

In the dictionary, looking at internal_type, we can see that the field only shows types where visible = true or the user has 'maint' (available only to ServiceNow employees).

If we look at the field class for 'domain_id,' we see that the visible flag is set to false.

And to change that would require 'maint' access.

So, our best workaround at the moment is to change the reference qualifier on the Dictionary Type field from:
'javascript:gs.hasRole('maint')?'':'visible=true';
to
'javascript:gs.hasRole('admin')?'':'visible=true';

After doing so, we can now see the Domain ID type and create a new sys_domain field on a custom table.

REMEMBER, though, to look through skipped updates in later releases so you can undo this workaround when a permanent fix is provided. In general, we should NOT be changing the Dictionary table in any way.

(attached doc has screenshots included)