Scope error for sys_choice records on pm_project table

[Louis Savalli]

Has anyone run into an issue where ServiceNow thinks you are creating sys_choice records in another scope even though you are in global?

To recreate this, go to the pm_project table definition and open up a string/choice list field whose underlying table is Task (this bug doesn't happen with fields on planned_task or on pm_project).  Scroll down to the choice list related list and add a new one.  After you add it, go back and look at your new sys_choice record, and you should see something similar to my screenshot below.  And if you look at the sys_update_xml record that was created, it will also have the Goal Framework scope.  I've been able to recreate this on two separate instances.  Any ideas what this is or how to fix it?

[Ankur Bawiskar]

@Louis Savalli 

because you were in your custom scope and then added the choices to the OOB field which is in global scope

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Runjay Patel]

Hi @Louis Savalli ,

Impact field if from task table and you are creating choice for your scoped app table then first do the dictionary override and create the choices.

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.

Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

[Louis Savalli]

Thanks but I'm creating a choice list for that field for the pm_project table, which is in the global scope.