Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Discovery of Cloud Datacenter failed with "Method returned an object of type sys_script_68e502fa0a0a0aa9001fdd4619ef53b5_12 which is not allowed in scope sn_cmp" - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Discovery of Cloud Datacenter failed with "Method returned an object of type sys_script_68e502fa0a0a0aa9001fdd4619ef53b5_12 which is not allowed in scope sn_cmp"
KB0688231

Discovery of Cloud Datacenter failed with "Method returned an object of type sys_script_68e502fa0a0a0aa9001fdd4619ef53b5_12 which is not allowed in scope sn_cmp"


355 Views Last updated : Apr 7, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

Symptoms


When going to Cloud Account > Datacenter > Discovery Now, immediately, client side is filled with the following errors:

"Method returned an object of type sys_script_68e502fa0a0a0aa9001fdd4619ef53b5_12 which is not allowed in scope sn_cmp"

Release


Jakarta and newer

Cause


The 'sys_script' record points to the 'getNextObjNumberPadded' Business Rule. In older versions, this business rule was not accessible from the 'All Application Scope'. Some of the Cloud tables have a numbering column which uses the business rule to to get the next number in the sequence. Newer versions of this business rule has 'Accessible from' field set to 'All application scopes'. If this business rule is not upgraded properly (ie, the business rule was customized), the Cloud applications in the 'Cloud Management Application' scope cannot access the business rule, resulting in the errors on the client side.

Resolution


  • Go to the affected business rule: getNextObjNumberPadded
  • Under the 'Versions' related list, right click the latest entry for the current instance and select 'Revert to this version'
  • This will update the business rule to the latest base version, making it compatible with Cloud Management Application

The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.