Form not rendering: form view configuration error

The form view references a field that has been deleted from the table dictionary but still exists in the form layout configuration. (high likelihood)

A UI formatter script contains syntax errors or runtime exceptions that prevent the form from rendering properly. (high likelihood)

A mandatory form section has corrupt XML configuration or missing required attributes in the sys_ui_section table. (medium likelihood)

The form view has conflicting or circular dependencies between UI policies, client scripts, or business rules that affect form rendering. (medium likelihood)

Access control rules are preventing the form from loading required field definitions or UI elements for the current user's role. (low likelihood)

Step 1: Check the browser console for specific JavaScript errors and note any field names or script references mentioned in the error details.

Step 2: Navigate to the affected table's form configuration by going to the table, right-clicking the form header, and selecting Configure > Form Layout to identify problematic fields.

Step 3: Cross-reference each field in the form layout against the table's dictionary by navigating to System Definition > Tables & Columns and searching for missing fields.

Step 4: Remove any fields from the form layout that no longer exist in the table dictionary or restore deleted fields if they are still needed.

Step 5: Review UI formatters on the form by checking System UI > Formatters and test each formatter script for syntax errors in the script editor.

Step 6: Examine form sections in the sys_ui_section table for the affected form view and validate that all section XML configurations are properly formatted.

Step 7: Test the form rendering by impersonating different user roles to rule out access control issues affecting form visibility.

Step 8: Clear the form cache by navigating to System Properties > UI Properties and toggling the glide.ui.form_cache property or restarting the instance if necessary.