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.
Is it possible to map manager in sys_user table although no_auto_map=true ? - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Is it possible to map manager in sys_user table although no_auto_map=true ?
KB0783213

Is it possible to map manager in sys_user table although no_auto_map=true ?


873 Views Last updated : Apr 20, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

An attribute 'no_auto_map' exists out of the box that is meant to prevent automatic mapping of the field 'manager' in the sys_user table when transforming data to import users into the platform

Is it possible to  disabling this attribute 'no_auto_map' shown in the dictionary entry of the field sys_user.manager ?

Resolution

Yes, this is possible to disable or remove attribute 'no_auto_map=true'

It was set up that way out of the box because, additional coding is required to fetch the manager value from LDAP and then attempt a lookup against an existing user in Servicenow

Out of the box, it is not possible to set the manger value from AD to the sys_user.manager because this is a reference field, so the underlying real value is a sys_id.

If the field was automatically mapped, then it would fail and throw a mapping exception.

It is possible to map but a little bit of additional coding is reequired to do the lookup from the name to return a Servicenow sys_id

The pre-requisite for the lookup to succeed is that the user manager name should already exist in Servicenow.


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.