Label showing Empty and throwing "Column name empty" on Update

[MandalaS]

Hi Everyone,

I am facing an issue where a custom Currency field Planning credit (USD) (u_planning_credit) on the Project (pm_project) table suddenly disappeared from the form layout.

When checking the Dictionary Entry (sys_dictionary), the Column label is completely blank. If I try to type the label back in and hit Update, the platform throws a validation error saying "Column name empty" and resets.

What I have verified and tried so far:

1. Sys Documentation exists: The sys_documentation record for pm_project and u_planning_credit exists and has the correct label populated. Please refer the attached acreesnhot.

Thanks!

[Abhishek Pal]

Hi @MandalaS ,

Based on the screenshots, I would not delete and recreate the field yet.

The combination of:

- pm_project.u_planning_credit existing in sys_dictionary
- Column label appearing blank
- A valid sys_documentation record already containing the label
- Updating the dictionary producing "Column name empty"
- The field disappearing from the form

suggests a dictionary/field metadata inconsistency rather than a normal Form Layout issue.

Recommended troubleshooting:

1. Verify the Dictionary record

Open:

sys_dictionary.list

Filter:

Table = pm_project
Column name = u_planning_credit

There should be exactly one field dictionary record.

Verify:

Table: pm_project
Column name: u_planning_credit
Type: Currency

If multiple dictionary records exist for the same table/element, investigate that first.

2. Verify the physical/logical field is still recognized

Run this read-only test in Scripts - Background:

var gr = new GlideRecord('pm_project');

gs.info(
'u_planning_credit is valid: ' +
gr.isValidField('u_planning_credit')
);

Expected:

u_planning_credit is valid: true

If this returns false even though the sys_dictionary record exists, you likely have inconsistent/orphaned dictionary metadata.

Do not delete/recreate the field in production in that situation because existing field data could be lost.

3. Verify the field from the Table definition

Navigate to:

System Definition > Tables
-> Project [pm_project]
-> Columns

Search for:

u_planning_credit

If the Dictionary record exists but the field is not recognized in the table's Columns metadata, this further indicates a schema/dictionary consistency problem.

4. Validate sys_documentation

Navigate to:

System Definition > Language File

Filter:

Table = pm_project
Element = u_planning_credit

Verify that the record for the user's current language contains:

Label:
Planning credit (USD)

Also verify that you do not have duplicate records for the same:

Table
+
Element
+
Language

The user-facing field label is stored in sys_documentation.

Therefore, if the actual field is valid and only the label is incorrect, update the existing sys_documentation record instead of trying to recreate the field.

5. Test the field again

After correcting the Language File record:

- Start a new session / sign in again.
- Open the Project form.
- Configure the form layout.
- Search for Planning credit (USD).

If it appears under Available fields, add it back to the required form view.

6. If the field is valid but Dictionary Update still throws "Column name empty"

Do not try to fix this by:

- Changing the Column name
- Deleting sys_dictionary directly
- Recreating u_planning_credit
- Manually inserting dictionary metadata
- Changing the field type

The Column name of an existing field is not intended to be changed.

Since sys_documentation is already correct, there should normally be no need to update sys_dictionary just to restore the label.

7. If isValidField() returns false

At that point I would open a Now Support case.

Provide:

Table:
pm_project

Field:
u_planning_credit

Dictionary sys_id:
<sys_dictionary sys_id>

Symptoms:

- Dictionary entry exists
- sys_documentation exists
- Field no longer appears on the form
- Column label is blank
- Updating produces "Column name empty"
- isValidField('u_planning_credit') returns false

Ask Support to verify whether the dictionary metadata and physical database column are still synchronized.

If this started after an update set rollback, clone, upgrade, field deletion, application repair, or migration, include that information because it can help identify how the metadata became inconsistent.

I would not recreate this field until the physical-column status is confirmed, particularly if existing Project records already contain Planning Credit values.

Also, the yellow Read Only message visible in the screenshot is related to the newer read-only field configuration and is not by itself an explanation for the "Column name empty" validation error.

In summary:

sys_documentation correct
+
sys_dictionary present
+
Column label blank
+
"Column name empty"

-> Verify field/schema integrity first
-> Update the Language File only if the field is valid
-> Do not delete/recreate the field
-> Escalate to Now Support if the dictionary exists but the platform no longer recognizes the field

Hope this helps!

If this response helped, please mark it as Helpful.
If it resolves your issue, please Accept it as Solution.

Kind Regards,
Abhishek Pal