You do not own the vendor prefix for this scope

[Anirban Roy]

Hi,

We are working on a known integration - Servicenow to Terraform integration.

We have imported the 3rd party application named 'Terraform' via source control as it is not available in servicenow store 

We understand that the app can be moved via update set, however Is it possible to deploy the app to further instances using publish and install option? 

While trying to publish the app, we are getting the below error because the app is built by 3rd part and thus company scope prefix wont match with the external app provider's scope.

**********************************************************************************

To summarize, I am trying to follow the below method to import the 3rd party scoped app, do some development and then move the application across instances along with my custom changes without xml import/ update set movement -

 

Looking for the best practices in this scenario. All suggestions are welcome.

Regards,

Anirban

[Pradeep Sharma]

Hi Anirban,

The scope prefix of the 3rd party store app will not be 'snc'. Each company will have a vendor key assigned from the ServiceNow side. For ex: Acme company (**test company just for reference**) will have vendor key assigned from ServiceNow something like x_acme (**just as a reference**)

- Pradeep Sharma

[Anirban Roy]

Hi @Pradeep Sharma ,

Thanks again for your response.

If I take your example, lets say ACME Company (x_acme) wants to install a 3rd party store app from Servicenow store. The app is not being developed by ACME Company but they are gonna purchase it from the 3rd party developer via SNOW store. so I would assume the scope wont be 'x_acme'. 

I want to understand the below:

1. The scope of this 3rd part app available in SNOW Store.

2. In case the scope is something x_<3rd party developer prefix>, then logically we should be getting the same error message while publishing.

We know there wont be any error but this is a question out of curiosity.

Regards,

Anirban

[Pradeep Sharma]

1. The scope will be retained i.e the scope Will be x_acme

2. In this scenario, we don't expect customers to publish an app via App Repo. Any minor changes can be captured via update set and promoted to the target instance if required (**assuming the changes are very specific to a customer and will not be included by the author of the app in future version).

- Pradeep Sharma

[Anirban Roy]

Awesome! Got my answer. 🙂

[Ravish Shetty]

Pradeep, I am getting the same error for a company-developed internal application. we developed it in DEV1 environment and moved to DEV2 and when we try to publish it from DEV2, we see this error. We no longer could use DEV1 environment because it being repurposed for some other projects.