A field Label is not getting displayed but its present in the the database

[suprakash]

In incident form i have a field whose column name is u_is_enhancement and column label is is_enhancement.

The column Label is not getting displayed in the form and i think for that reason i cannot find the field in the incident form ,

i have checked in form layout also its not there

But in the back ground script i checked its displaying the label

If i update the filed label its getting updated but not visible.

var gr = new GlideRecord('sys_dictionary');

gr.addQuery('element','u_is_enhancement');

gr.query();

gr.next();

gs.print(gr.column_label);

Output : *** Script: is_enhancement

Its in the the database but its not visible.

I am attaching the image

[suprakash]

No its not working. is there any way out other than deleting the column and creating a new one????

[Harish KM]

I would suggest to raise a HI ticket.   Dealing with dictionaries are pretty risky

[ShubhangiW]

That was helpful.

I had the same issue - When I added a new field after the existing 125 fields, the column label showed empty while the column name showed fine in the Advanced view. This 126th field never showed in the normal view in ServiceNow studio. I was able to find the field in sys_documentation and added a column label and the field still continued to be invisible to GlideRecord.getElements() API. I also checked sys_dictionary and the field had no column label although the field showed. The field did not show in Table Schema Map of my staging table. In sys_storage_table, I only saw the staging table but no columns. 

I saw a forum question where they said the limit had been reached and they had to delete a (unused or less used) column to add a new one. I did that and that worked. I wish this limit did not exist on the number of columns we can add in a table or that it was more than 125.

[nthumma]

this happens in two scenarios

1) One a delete a field and create the field again with same name.

2) if you actually hit SQL limit of number columns(storage) allowed on the table.

[Archi]

I had the same problem.

The number of fields in the table is limited due to the limitation of the maximum length of the SQL query row to the database. Exceeding this boundary value entails hiding the labels of newly created fields (in tables where there are a large number of fields). In this case, the table needs to create another table for additional fields.

I add the required fields not to the original table, but to the table for additional fields.

Using output these fields on the form of the original table.