Form sections moved through update set do not reflect on the target instanceIssue Form sections updated by navigating to sys_ui_form --> select table --> add the sections to the form and capturing them in an updated set is not the ideal way to move it from one instance to another. This will not save the changes correctly in the update set. ResolutionForms, form sections, and variables on the form should always be updated via Configure --> Form LayoutForm sections are dependent on the form layout.Form layout and form sections should always move together to the targetted instance.When updating the Form Layout, the update set entry will show the entry for type Form Layout. The modification for the section and fields corresponding to the specific layout can be found in the update set payload field. So there is no need to capture it separately.Related LinksThe tables that are involved when a form section OR element OR layout is moved via update set: sys_ui_form – The entry point to the form. Each form view will have its own record here. (when a view is modified) sys_ui_section – The holding record for a form section. This is the actual section itself for a form but does not itself hold any field data. (when a section is modified) sys_ui_form_section – The many to many tables linking the forms to the sections. (when a form section modified) sys_ui_element – This is each of the elements on a section. It contains the position value so that they can be ordered in the section using that position. (adding or removing variables from a form) Other KB articles & Community links can be referred 1. KB0677504 - Domain Separation Delegated Administration and Form Layout creates shared form sections. This is specifically for domain-separated instances but can be applied to non-domain separated instances as well. 2. sections not showing after update set 3. Form Layout 4. KB0534762 - Form Sections configuration - Broken relationships between [sys_ui_section] and [sys_ui_form_section] records cause forms to not load