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.
Import Entitlement can throws error: The custom column field '<field_name>' is mandatory but was not present. - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Import Entitlement can throws error: The custom column field '<field_name>' is mandatory but was not present.
KB0829102

Import Entitlement can throws error: The custom column field '<field_name>' is mandatory but was not present.


1094 Views Last updated : Jan 29, 2025 public Copy Permalink
KB Summary by Now Assist

Description

Changing some of the fields to mandatory on Software Entitlement form can cause issues while importing the entitlement even though the mandatory fields are present in the import document.

Steps to Reproduce

> Any instance which is in Orlando version
> Change some of the fields that are not mandatory OOTB to mandatory(fields like start_date,end_date,publisher_part_number,unit cost)
> Import an entitlement with above mandatory fields present in the excel sheet.

Error is thrown:
Multiple reasons for error: Publisher Part Number not found; The custom column field 'end date' is mandatory but was not present; The custom column field 'publisher part number' is mandatory but was not present; The custom column field 'start date' is mandatory but was not present; The custom column field 'unit cost' is mandatory but was not present


Workaround

The issue can be fixed by adding the mandatory fields to line 67 of the script include SAMPEntitlementUtil

https://<instance-name>.service-now.com/nav_to.do?uri=sys_script_include.do?sys_id=31630b8587420300562e4127f5cb0b01

OOTB:

MANDATORY_NON_CUSTOM_FIELDS: ['model', 'model_category', 'quantity', 'license_metric', 'purchased_rights', 'software_model', 'product_type'],

Add the other fields like below:

MANDATORY_NON_CUSTOM_FIELDS: ['model', 'model_category', 'quantity', 'license_metric', 'purchased_rights', 'software_model', 'product_type','start_date','end_date','unit_cost','publisher_part_number'],

Note: SAMPEntitlementUtil is a protected script so customers would not be able to modify this, if required customer support would be able to assist the customer further if they choose to use the workaround.


Related Problem: PRB1411112

Potentially Seen In

There is no data to report.

Fixed In

Orlando Patch 10
Paris Patch 5
Quebec

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.