- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2017 06:26 AM
Hello, everyone
I've created a scoped application. One of the tables from this application has been modified to be tracked in an update set.
I've pushed this application to my non-production instance. Now, some of the records, that are created in this table, are marked as created in Global application.
How can that be - a table still belongs to a scoped application according to it's name (contains scoped applicaton prefix of x_12345_tableName), but records in it are created in Global application? Is there a way to fix that?
Thank you.
Solved! Go to Solution.
- Labels:
-
Scoped App Development
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2017 07:18 AM
Is that from the Customer table in the Notes application? If that's the case, then I too am curious how those records are able to be created from the Global scope. It looks like it is doing the proper thing in not allowing you to modify them unless you are in the same scope they were created, but how they are being created, I don't know. I haven't use the "Track in Update Set" feature in a scoped app yet so I have no background information to draw upon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-24-2017 07:32 AM
Yes, the settings on the screenshot are for the Customers table in the Notes application.
I guess my steps would be to re-create the table in the application, set up all dependiencies one more time, migrate all existing records in it and create a feature request to ServiceNow to fix the issue (I assume it's the issue, could be wrong on that one).
Thanks, Chuck, for your expertise. I'll take it from here.
