Field Label Empty in Dictionary – Cannot Add Field to Form

[Nilam Narote]

Hi Community,

We're facing an issue with a field not appearing on the Policy Exception form in our instance.

Issue Details:

• On the Policy Exception form, when Source Type is set to Policy, the corresponding Policy field does not appear.

• Attempting to manually add the Policy field to the form is not possible because:

  • The field does exist in the table.

  • However, in the Field Dictionary, the Column Label is empty.

  • The XML export of the field does show a label value, but it's not reflected in the dictionary entry within the platform.

Thank you!

[Community Alums]

hi @Nilam Narote ,

• The Policy field exists on the table, but its Column Label is blank in the dictionary.
• Because of that, the form layout tool doesn’t show it as an available field to add.
• Even though the XML shows a label, the platform UI doesn’t reflect it — possibly due to a mismatch or corruption in the dictionary entry.

1. Manually Update the Column Label

• Go to System Definition > Dictionary.
• Search for the field (e.g., policy) on the Policy Exception table.
• Open the dictionary entry.
• If the Column Label is blank, add a label like “Policy” and save.

This should make the field appear in the form layout editor.

---

2. Clear Cache (Optional but Helpful)

After updating the dictionary, run the following in the Application Navigator to refresh metadata:

3. Reopen the Form Layout

• Go to the form layout for the Policy Exception table.
• You should now see the Policy field in the list of available fields to add.

---

4. Check UI Policies or Client Scripts

If the field still doesn’t show up when Source Type = Policy, check:

• UI Policies: Make sure there’s no policy hiding the field unintentionally.
• Client Scripts: Look for scripts that might be hiding the field based on conditions.

[Nilam Narote]

Hello Tejas,
I’ve already tried this solution, but it didn’t work.
Thank you!

[VedS]

Hello @Nilam Narote ,
Try to clear the Cache, in most of the cases clearing the cache resolves such issues.

Please mark this as "correct" and "helpful" if you feel this answer helped you in anyway.

Thanks and Regards,

Ved

[Nilam Narote]

This solution did not work in my case.