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.
Records in [sys_ui_section] and [sys_ui_form_section] system tables are deleted when a form section is used for more than one form view - Known Error
  • >
  • Knowledge Base
  • >
  • Known Error (Knowledge Base)
  • >
  • Records in [sys_ui_section] and [sys_ui_form_section] system tables are deleted when a form section is used for more than one form view
KB0634434

Records in [sys_ui_section] and [sys_ui_form_section] system tables are deleted when a form section is used for more than one form view


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

Description

Form layout misconfiguration can lead to sys_ui_form_section and sys_ui_section records disappearing.

The following misconfiguration is seen in several use cases, possibly due to the Form Designer:

View A will have a form defined for Incident that has several sys_ui_form_sections pointing to sys_ui_sections with the view defined as View A.

View B will have a form defined for Incident that has several sys_ui_form sections pointing to the same sys_ui_sections in View A, or just some of them.

The relationship does not cause any issue with the form rendering. The main problem is that the relationship can exist in the instance without the administrator knowing, and when a form layout change is made (for example, adding/removing a field, reordering), the sections disappear and leave the form in an unusable state.

Steps to Reproduce

 

  1. Go to sys_ui_view.do and create two new UI Views: View A and View B.

  2. Create incident forms for both views based on the Default view.

  3. Go to sys_ui_section_list.do and delete the record for Related Records from View B.

  4. Copy the sys_ID of the record for Related Records from View A.

  5. Go to sys_ui_form_section_list.do and use the sys_ID to set the relationship for Related Records in View B.

    The two forms should now share sys_ui_section records for Related Records but have their own copy of everything else.

  6. Make a change to the form layout of both views.

    One or both updates will cause the form sections to disappear.

 

Workaround

Delete the invalid form sections for the affected table and view, and then manually re-create them using the Configure Form Layout feature.

For more information, see KB0534762, "Form Sections configuration - Broken relationships between [sys_ui_section] and [sys_ui_form_section] records cause forms to not load."

 


Related Problem: PRB671474

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.