Issue creating a scoped application in PDI

[akinloyeoye]

Hi,

I am getting this error message:

Unable to create this application. Go back to the create app experience and enter a different scope name. Details: Failed to create templated object, details: This scope is already taken by another application.

I have entered different combinations of names, even using my name, but I am still getting the same error message. Any idea on how to resolve the issue?

[Dr Atul G- LNG · Accepted solution]

Hi @akinloyeoye 

https://www.servicenow.com/community/app-engine-articles/resolving-this-scope-is-already-taken-by-an...

[Bhuvan · Accepted solution]

@akinloyeoye 

Go to Applications table [sys_scope.LIST] from Application Navigator,

Search in the scope field to make sure the scope you are trying to create do not exist. Create an application with a unique name.

Note, maximum length of scope name is 18 characters and this could be causing the name conflict.

If this helped to answer your query, please accept the solution and close the thread.

Thanks,

Bhuvan

[Dr Atul G- LNG · Accepted solution]

Hi @akinloyeoye 

https://www.servicenow.com/community/app-engine-articles/resolving-this-scope-is-already-taken-by-an...

[akinloyeoye]

Thank you. This was helpful

[Bhuvan · Accepted solution]

@akinloyeoye 

Go to Applications table [sys_scope.LIST] from Application Navigator,

Search in the scope field to make sure the scope you are trying to create do not exist. Create an application with a unique name.

Note, maximum length of scope name is 18 characters and this could be causing the name conflict.

If this helped to answer your query, please accept the solution and close the thread.

Thanks,

Bhuvan

[Nikhil Bajaj9 · Accepted solution]

Hi @akinloyeoye ,

The error message "This scope is already taken by another application" indicates that the unique identifier (scope) chosen for the new application is already in use within the ServiceNow instance. Each application in ServiceNow requires a distinct scope to prevent conflicts and ensure proper isolation of its components. 

To resolve this issue, the following actions can be taken:

• Modify the Application Name or Scope Identifier:

When creating the application, ensure that the chosen name or manually specified scope identifier is unique within the instance. Adding a unique identifier, such as initials, a date, or a version number, to the application name can often generate a unique scope automatically.

• Verify Existing Application Scopes:

Navigate to the list of scoped applications within the ServiceNow instance (by typing sys_scope.list in the application navigator) to confirm if the desired scope already exists.

If my answer helepd you , please mark it solution accepted.

Regards,

Nikhil Bajaj