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.
Additional columns created in Import set table when specifying wrong header row - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Additional columns created in Import set table when specifying wrong header row
KB0821309

Additional columns created in Import set table when specifying wrong header row


3586 Views Last updated : Apr 8, 2024 public Copy Permalink
KB Summary by Now Assist

Issue

When the Import set table is created by admins for the very first time as per requirement the columns are defined and then transform maps are prepared along with a standard data load sheet.

Please note the columns created in import set table will match the columns specified in the row that was chosen as header. When a non admin is trying to use the import set table going forward and specifies a wrong header row by mistake system tends to create additional columns in the Import Set table and it does not prompt the user or stop them in doing the data load.

Main concern is the system allows a non-admin user to create columns in import set table indirectly when wrong header is chosen?

Cause

- This is working as per the design

Resolution

We need to set this import set property "glide.import_set_row.dynamically_add_fields" to "false inorder to stop dynamic fields creation.

 

You also have below options:

 

1) Clean up your Excel spreadsheet so that it only includes columns for fields that already exist in your Import Set table

 

2) Manually ensure that all columns in your Excel file have corresponding fields configured in your Import Set table

 

Note: Once the the Import Set Table has columns created and when the property "glide.import_set_row.dynamically_add_fields" set to "false" then it will not allow even any admin user to create the new column dynamically during the date load.


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.