- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2019 11:38 AM
Hi all,
I've made an scoped app on the sandbox instance, when the first version was done i published my scoped app. After publishing i've installed the app on the dev instance via System Applications > My Company Applications. When installed, i want to develop on the dev instance on the scoped app. Unfortunately i can't find my scoped app in studio, because there is no entry made in the sys_app table. Does anybody have any tips how to fix it? And what possibly went wrong..
Thanks!
Solved! Go to Solution.
- Labels:
-
Scoped App Development
-
Studio

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2019 11:58 PM
Hi Tjardo,
The reason it is not available in Studio on test instance is because the app was shared via Apprepo i.e Publish to My Application Repository. Recommended in order to publish an app to internal instances. That said, if your requirement is to have an author version of the app (** In order to develop the app **) then you should export the app update set XML and import it in the target instance. In this case, the app will be visible in Studio.
P.S: In case you prefer to go with an update set approach, make sure you delete the application which you have already installed in the target instance before importing the update set XML.
- Pradeep Sharma

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-21-2019 11:58 PM
Hi Tjardo,
The reason it is not available in Studio on test instance is because the app was shared via Apprepo i.e Publish to My Application Repository. Recommended in order to publish an app to internal instances. That said, if your requirement is to have an author version of the app (** In order to develop the app **) then you should export the app update set XML and import it in the target instance. In this case, the app will be visible in Studio.
P.S: In case you prefer to go with an update set approach, make sure you delete the application which you have already installed in the target instance before importing the update set XML.
- Pradeep Sharma
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2019 12:25 AM
Thanks Pradeep! So if i understand you well, if you want to develop on your app in studio on another instance you always have to migrate via xml update set? So i have deinstall and remove my scoped app on the dev and import again with xml? The thing is i already have a new update set with newer updates on the dev instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2019 11:17 AM
Yes, you are right.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2019 12:22 AM
Hi Tjardo,
Not sure on your actual issue. Though, adding this one:
A while ago, we noticed that the sys_app records where different between our dev-test-prd environments (dev being the "correct" one). We added Clone Data Preservers so that these sys_app records will not be lost on our dev environment when cloning.
Kind regards,
Mark
---
LinkedIn
Community article list
Kind regards,
Mark Roethof
Independent ServiceNow Consultant
10x ServiceNow MVP
---
~444 Articles, Blogs, Videos, Podcasts, Share projects - Experiences from the field