Application Portfolio Management - Scope Issues
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-25-2017 11:16 AM
We're implementing Application Portfolio Management and running into a couple of issues - most likely related.
App Portfolio Mgmt appears to be a hybrid between a fully scoped application and a module. I see that the Application field is set to "Application Portfolio Management" but it doesn't appear in Studio.
When I try to remove (or heck, I'll take 'set to inactive') a choice in a field on APM, I'm seeing two different error messages:
"This record is in the Global Application, but Application Portfolio Management is the current application"
"Invalid 'Choice Set' record even though the selected outside Table "Business Application" is allowed.
I've tried setting the choice record to Inactive = True while in the APM scope and in the Global scope.
I've tried going through the table form and through the sys_choice table directly.
There's no way I've found to make the update.
It seems that ServiceNow is getting confused as to which scope it's in. Has anyone else run across this? Is there a fix / workaround?
Thanks!
- Labels:
-
Best Practices
-
Scoped App Development

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-25-2017 03:27 PM
Hello Sue,
It looks like a Bug. As a workaround, you can try to update the record via background script using setWorkflow(false). Can you please give it a try and let me know if that works.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-28-2017 06:21 AM
Hi Pradeep,
I ran this code in the background:
updateRecord();
function updateRecord() {
var gr = new GlideRecord('cmdb_ci_business_app');
gr.addQuery('value', 'cots');
gr.query();
while(gr.next()){
gr.inactive = true;
gr.setWorkflow = false;
gr.update();
}
}
It ran, but came back with this message and did not make the change.
cmdb_metadata : Rule d551e0a0c31122003e76741e81d3ae35: Missing field container on table cmdb_ci_endpoint_storf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-13-2017 10:05 AM
ServiceNow indicates that this is a bug that is fixed in Kingston.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-20-2019 01:49 PM
I am at Kingston, patch 12, and seeing similar issue. I am creating a scoped app that uses the Business Application CI class (cmdb_ci_business_app). I am trying to change the choice values for application_type attribute. I can go outside the Studio and set the existing 2 choices to inactive, but unable to add a new choice. When I go to sys_choice.list and click New and try to add a new choice for application_type i get the message shown. Anyone know how to add the new choices.
I solved my problem, i had the application scope set to my scoped App, when I changed the scope to Global I was able to create the new choice entries