You do not own the vendor prefix for this scope

Gary Fawcett1
Tera Guru

Hi,

 

We are unable to publish a Scoped Application to our company Application Repository from Studio.

 

We get this error message: "You do not own the vendor prefix for this scope"

 

The application did start its life on a Personal Dev Instance, so hence the Vendor Prefix won't the same as your company.

 

Is it possible to change the vendor prefix or scope on an existing application, I couldn't find anything online.

Thanks...Gary

4 REPLIES 4

sago45
Tera Contributor

Hi,

We had the same issue before where the applications were under different prefixes and I remember we had to go ServiceNow Support to get this fixed. 

Runjay Patel
Giga Sage

Hi @Gary Fawcett1 

Check this below thread and if still not able to solve then you have to get support from ServiceNow HI team.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0712291

https://noderegister.service-now.com/kb?id=kb_article_view&sysparm_article=KB0749922

 

-------------------------------------------------------------------------

If you found my response helpful, please consider selecting "Accept as Solution" and marking it as "Helpful." This not only supports me but also benefits the community.


Regards
Runjay Patel - ServiceNow Solution Architect
YouTube: https://www.youtube.com/@RunjayP
LinkedIn: https://www.linkedin.com/in/runjay

-------------------------------------------------------------------------

Ravi Gaurav
Giga Sage
Giga Sage

Hi @Gary Fawcett1 

 

This error occurs when there is a mismatch in the Application Repository between the Application Scope and source_app_id. This combination is supposed to be unique. This can happen when the Application is published to an Updated Set and the source_app_id is modified before the Application is reloaded on another instance.

--------------------------------------------------------------------------------------------------------------------------


If you found my response helpful, I would greatly appreciate it if you could mark it as "Accepted Solution" and "Helpful."
Your support not only benefits the community but also encourages me to continue assisting. Thank you so much!

Thanks and Regards
Ravi Gaurav | ServiceNow MVP 2025,2024 | ServiceNow Practice Lead | Solution Architect
CGI
M.Tech in Data Science & AI

 YouTube: https://www.youtube.com/@learnservicenowwithravi
 LinkedIn: https://www.linkedin.com/in/ravi-gaurav-a67542aa/

Gary Fawcett1
Tera Guru

Thanks for all the answers, in the end this worked for me.

 

I created a new scope and then ran the script on this post HERE.

This seem to work for me, I need to do some more tested as I think the cross scope permission may need to be setup again.

Thanks...Gary Fawcett