Form layout displays label as section name when configuring formsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } When configuring forms, all fields and form sections may appear missing from the form layout. This article explains how forms are structured across platform tables and provides steps to identify and resolve missing form section records for both single and multiple form section configurations. This article is intended for system administrators. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Releases Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Table of Contents Identifying the issueHow Forms Work Case #1: Single Form SectionCase #2: Multiple Form Sections How to Troubleshoot Case #1: Single Form SectionCase #2: Multiple Form Sections Identifying the issue When configuring forms, all fields and form sections may appear missing from the form layout. How Forms Work A form consists of the collaboration of multiple tables: sys_ui_view – Holds the record for the View where the form livessys_ui_form – Holds the container for when a form has Multiple Form Sectionssys_ui_form_section – A container for the section and its elementssys_ui_section – The form section as displayed on tabs in the formsys_ui_element - Contains the relationship to the fields on the form When you configure the form layout, all of these tables are updated in the backend to reflect the changes made. There are two different use cases for how forms are built. The following diagrams show how these tables work together, followed by an explanation. Case 1: Single Form Section For a form with a single form section, the relationship between the view and the section is established directly without needing to reference the form or form section records. The section itself is tied to multiple elements. The view — in many cases the base system Default view — is tied directly to the section. A section for this use case tends not to contain a caption and is not accompanied by any tabs or additional division of sections. The single section tends to inherit the name of the table. Note: Sections should not be confused with related lists, which appear below Related Links on forms. Case 2: Multiple Form Sections For a form with multiple form sections, two additional tables join the schema: sys_ui_form and sys_ui_form_section. The sys_ui_form record acts as an invisible container for all the form sections and their corresponding elements. The sys_ui_form_section sections are contained inside the form record and act as containers for all the individual sections This schema makes it possible to modify sections across the platform without repeating the same steps on each individual view. It also provides a way to domain-separate the form sections if the instance is domain-separated. The form and form sections are containers that are not explicitly visible on the form. Note that even though the form sections highlight the tabs, they represent a container of the section inside and are not the section itself. How to Troubleshoot To troubleshoot, identify which record is missing from the schema, then restore it by importing it from another instance where the issue is not present. Case 1: Single Form Section 1. Identify the view in use on the affected form. 2. Navigate to System UI > Views. 3. Find and open the record for the view identified in step 1. 4. Select the Sections tab in the related records and search for the affected section using the table name. - If the section is not found, the record needs to be restored. If a working instance is available, export the XML file for that section and import it into the affected environment. - To confirm the correct form section, verify the sys_id by opening the form in a browser, opening the browser developer tools, and searching the elements panel for an element whose ID starts with section_tab. The sys_id for the corresponding section follows the section_tab text — for example, section_tab.<sys_id> The following figure shows an example. 5. Import the XML file from your other instance. - If no working instance is available, contact Customer Support for further troubleshooting. 5. Run cache.do in the affected instance to clear the cache and apply the changes 6. Run cache.do in the affected instance to clear the cache and apply the changes. Case 2: Multiple Form Sections 1. Identify the view in use on the affected form. 2. Navigate to System UI > Views. 3. Find and open the record for the view identified in step 1. 4. Select the Forms tab in the related records and search for the affected form using the table name. - If one is not found, the record needs to be restored. If a working instance is available, export the XML file for that form and import it into the affected environment. 5. If the form record exists, open it and review every related form section record to confirm each one is present. - If any record is missing, import it from an instance where the issue is not present. Ensure the sys_id values for the missing section match those in the working instance. Repeat this check for any missing form, form section, section, or element record. 6. Run cache.do in the affected instance to clear the cache and apply the changes. The following video provides a live example of how to fix multiple form sections (with audio). After completing these steps, the form layout returns to normal and can be configured in the standard ways.