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.
Unable to save form layout when using 'Create new field' section. - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Unable to save form layout when using 'Create new field' section.
KB0817426

Unable to save form layout when using 'Create new field' section.


560 Views Last updated : Apr 8, 2025 public Copy Permalink
KB Summary by Now Assist

Issue

This article discusses possible troubleshooting scenario when user encounters the following:

  • New field is not saving to form
  • They are using Configure Form Layout and adding new field using the 'Create new field' section
  • When they hit 'save' nothing happens, and their new field is not saved.
  • The new field cannot be found even when searching the table's columns.

Cause

This can happen when the user is trying to add a field whose name already exists on a parent table of that form/table.  For example, if they added a custom field to [incident] and are now trying to add the same field name to [task] it will not work.  Although this can appear to be failing silently from the front end, you should be able to see an error present in the node logs when trying to save:

WARNING *** WARNING *** 'u_field_name' is already defined on 'other_table'

This happens because 2 fields cannot have the same name within the same table hierarchy. 

Resolution

Try adding the field with another name, or remove the existing field first from the conflicting table in the hierarchy.  This is expected behavior.


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.