How to fix it

  1. First, verify the field exists in the dictionary. Navigate to System Definition > Dictionary, search for your table name, then locate the field. Confirm the Active checkbox is checked.
  2. Check ACL restrictions by going to System Security > Access Control (ACL). Filter by your table name and look for any ACLs with Operation = read that reference your field name.
  3. Open any field-level read ACLs you found. Check the Requires role field and Script condition. If your user lacks the required roles or fails the script condition, the field will be hidden.
  4. To temporarily test ACL impact, impersonate a user with admin role or modify the ACL to add your current roles to the Requires role list.
  5. If ACLs aren't the issue, check the form layout. Navigate to your table's form, right-click and select Configure > Form Layout or open Form Designer from the gear icon.
  6. In Form Designer, look for your field in the Available Fields list on the right. If it's there, drag it to the desired section on the form. If it's not in Available Fields, it may be restricted by ACL or be on a different table.
  7. Check for UI Policies that might be hiding the field. Go to System UI > UI Policies and filter by Table = [your_table] and Active = true.
  8. Open each UI Policy and click the UI Policy Actions tab. Look for actions where Field name matches your field and Visible = false.
  9. If you find a UI Policy action hiding your field, check the UI Policy's Conditions tab to understand when it triggers. Either modify the conditions or change the action to Visible = true.
  10. Check if the field exists on the correct table. Go to System Definition > Tables, find your table, and verify its Extends table value. The field might exist on a parent table that doesn't inherit to your current table.
  11. As a final check, look for Client Scripts that might be hiding the field. Navigate to System Definition > Client Scripts and search for scripts containing setVisible(false) or setDisplay(false) with your field name.
💡

Quick verification: After making changes, always test with a different user role or in an incognito browser window to confirm the field appears as expected.