Columns not visible on Form Layout

ravin
Giga Contributor

We've around 220+ columns created on a custom table(not extended from any) and having multiple views. 
When I try to arrange the columns, I see that some columns are not visible on Form Layout slush bucket to arragnge. 

Can someone help on this please. Thank you in advacne. 

find_real_file.png

find_real_file.png

7 REPLIES 7

ravin
Giga Contributor

Thank you all for your responses.

 

I got to see an issue here. We've created 220+ columns. Recently there was a cloning activity, after which we reapplied our update sets and surprised to see just 203 columns. 

 

We damn sure, we've captured all 220+ columns into an update set. 

 

Contacting ServcieNow on the same. Meanwhile if any of you get to know about maximum # of columns allowed on a table, kindly let me know.

Hi,

As given in the MySQL docs, there is a hard limit of 4096 columns per table.

Please refer the given link for more information.

Thanks.

Did you check the sys_update_xml related list on the update set, as well as sys_update_preview_xml? If it's all in the same update set, filter the related list on both the sys_remote_update_set record as well as the sys_update_set. Filter for name starts with sys_dictionary and target name starts with your table name.

If there's not the right number in the remote update set, they weren't captured. It could be possible they got skipped if you loaded the update set to a different instance, and skipped remote updates, then only saved the update set from the second instance. Other than that I don't know what to tell you.

If there is the right number in remote but not local, some got skipped, possibly from preview errors/warnings where you selected 'skip remote update'. Try reloading the update set and accepting remote update sets on any preview errors/warnings for sys_dictionary updates.

If there's the right number in both. The records are there somewhere unless they were later deleted. Check the target name field and check if you see any weird ones with bad data.