snc ui-component deploy throwing ERROR in Component tag name exception

Paritosh Fulsu1
Tera Contributor

Hi, 

We are trying to develop a custom component and followed the documentation to get the custom component development started. As of now the components is very simple and just displays a welcome message no additional component used on top of what the template provides. 

We could build the code successfully and test it locally

But when we try to execute snc ui-component deploy --profile dev6275, we are getting the below exception

ERROR in Component tag name "m365-snow" must start with the vendor prefix "x-777875-"

We are using a Personal developer instance for this test.

Any pointers on how to fix this issue.

1 ACCEPTED SOLUTION

Brad Tilton
ServiceNow Employee
ServiceNow Employee

I believe the name of your component needs to match the company code in the instance you're deploying it to. For example, if you connect to an PDI instance, scaffold and build the component, then try to deploy to a different PDI you're going to get that error.

In your index.js in the createCustomElement it will need to start with x-777875. In the screenshot you can see that my PDI's prefix is x-85636 so any component I need to deploy to it starts with that prefix:

find_real_file.png

View solution in original post

2 REPLIES 2

Sandeep Rajput
Tera Patron
Tera Patron

According to ServiceNow Component documentation scope name for a component should adhere to the following guidelines.

find_real_file.png

You can also add the scopeName parameter in the now-ui.json file.

find_real_file.png

Follow these steps and check if your component scope name is in accordance with these guidelines. 

Brad Tilton
ServiceNow Employee
ServiceNow Employee

I believe the name of your component needs to match the company code in the instance you're deploying it to. For example, if you connect to an PDI instance, scaffold and build the component, then try to deploy to a different PDI you're going to get that error.

In your index.js in the createCustomElement it will need to start with x-777875. In the screenshot you can see that my PDI's prefix is x-85636 so any component I need to deploy to it starts with that prefix:

find_real_file.png