Two application scopes on the same form!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2015 09:06 PM
Since the last patch (Fuji Patch 8), whenever I deploy an application via update set (created via 'Publish') from the upgraded instance to a new one, I am finding my forms have fields and sections from both the application scope and global on the same form!
This is incredibly frustrating... I can't find a way to stop this from happening!
You can see below that the top half of the form is in my scope (light grey), and the bottom half in global (dark grey)!
If I deploy this update set on an instance that already has the application I see the same behavior.
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2015 09:24 PM
P.S. It is adding the form and sections from Default View onto the end, rather than keeping it where it belongs (Default View!)
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2015 01:41 PM
Hi Paul,
You should be able to have fields from multiple scopes on the same form. For instance, if your scoped application adds a field to the Incident form, you should be able to have all of the regular Incident fields (in the global scope) in addition to your new field, show up in your custom view.
That said- it shouldn't happen when you aren't expecting it. If you are creating a new view in your scope, and the only section in that view is your section, and the only fields in that section are your fields, there shouldn't be other additional fields added.
Would you mind providing detailed steps to reproduce the issue? From beginning with a new app, through how you are creating the form view, to the links you are publishing, and the ServiceNow version of the instance that the app is developed on to the ServiceNow instance version that the app is deployed to.
With that information, we can open up a good Problem ticket, track down the root cause, and provide a fix.
Alternatively, if you open up an Incident with the Support team, they can help gather that information, and write up the Problem ticket.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-21-2015 06:23 PM
It is happening when I don't expect it.
I've found a workaround which is to ensure that the application has a default view configured.
Otherwise the system generates one in the global scope then attaches it to the end of your existing scoped view!
ServiceNow Nerd
ServiceNow Developer MVP 2020-2022
ServiceNow Community MVP 2019-2022