Story [rm_story] table and the Team [eap_team] field Dictionary entry has an error out of the box

juliebailey · ‎05-27-2026

I want to limit the Team [eap_team] field on the Story [rm_story] table so that when a Story record is created from Strategic Planning Workspace the Team field is only populated with Enterprise Agile Teams from the team level (e.g., not the higher level teams for the Portfolio (Epic) or Agile Release Train (Feature)). I noticed that the Dictionary entry for the Team [eap_team] field from the Story [rm_story] table has an error message that is preventing me from change the Reference Qualifier or adding Dictionary Overrides. The error message says "Invalid 'Dictionary Entry' record even though the selected outside Table 'Story' is allowed." I tested this in a PDI and the error appears out of the box without making any changes. Is this an error that ServiceNow is aware is happening in Zurich and Strategic Planning? I searched for known errors and could not find anything related to this error message. I would like to know if there is a way to clear this error and make changes to the Reference Qualifier for the Team [eap_team] field? Or if the error is intended to happen, is there another way to limit the Team [eap_team] field so that only Enterprise Agile Teams are displayed?

sristiG · 4 weeks ago

Hi,

One of my collegue has the same issue. As a workaround what they did was to create a dictionary entry record on the eap_team through background script and override the reference qualifier and it worked.

View solution in original post

juliebailey · 4 weeks ago

Thank you for your response, @sristiG. We tried your suggestion and it worked perfectly for us. Here is the background script that we used:

var TABLE_NAME = 'rm_story'; //table that the reference qualifier is applied to
var FIELD_NAME = 'eap_team'; //field that the reference qualifier is applied to
var TASK_TABLE = 'task'; //base table of the table from the variable for TABLE_NAME
var QUAL_TRUE = 'true'; //flag to set the reference qualifier to override the system setting

var qualifier = "javascript&colon;'sys_class_nameINSTANCEOFsn_apw_advanced_agile_team'"; //entry that will be inserted into the reference_qual field of this dictionary override

// Look for existing override
var gr = new GlideRecord('sys_dictionary_override');
gr.addQuery('name', TABLE_NAME);
gr.addQuery('element', FIELD_NAME);
gr.query();

if (gr.next()) {
// Update existing override
gr.setWorkflow(false);
gr.autoSysFields(false);

gr.reference_qual = qualifier;
gr.base_table = TASK_TABLE;
gr.update();

gs.print('Updated existing override for ' + FIELD_NAME);
} else {
// Create new override
var newRec = new GlideRecord('sys_dictionary_override');
newRec.initialize();

newRec.name = TABLE_NAME;
newRec.element = FIELD_NAME;
newRec.reference_qual = qualifier;
newRec.base_table = TASK_TABLE;
newRec.reference_qual_override = QUAL_TRUE;

newRec.insert();

gs.print('Created new override for ' + FIELD_NAME);
}

View solution in original post

brianlan25 · a month ago

I would open a case with ServiceNow Support.

Tanushree Maiti · a month ago

Hi @juliebailey

Refer KB: KB0824064 Invalid Choice record even though selected outside table 'xxx' is allowed

Resolution

1. Go to the cogwheel icon on the right corner of the instance

2. Select the developer tab and toggle the options to show the Application picker and update set picker

3. Once the application picker is visible, select the application where your choice record needs to be created

4. Make the change to the choice record and observe error is not thrown anymore.

Please Accept the solution if it assisted you with your question & Mark this response as Helpful.
Regards
Tanushree Maiti
ServiceNow Technical Architect
LinkedIn: https://www.linkedin.com/in/tanushreemaiti

juliebailey · a month ago

Thank you, @brianlan25 and @Tanushree Maiti. We have a HI Ticket in with ServiceNow. I will let you know what happens with that case.

Sunil B N · a month ago

Hi,
Please create an support ticket for the error issue. Meanwhile if you like to limit the Team [eap_team] field so that only Enterprise Agile Teams are displayed, then you can create a ACL for only that field.