I have been working on a project that requires me to use some fields that are not available to me on my current table- but they do exist on another table!
Both the new table I am working on and the table where the fields exist extend the “task” table so it makes sense to promote the fields from the extended table, up to task and have them available on both tables!
The script needed:
To achieve this I will need to run the following in a background script
GlideDBUtil.promoteColumn('table_to_move_from', 'table_to_move_to', 'field_to_move', true);
This will not be saved in an update set, ensure to make this change before you apply update sets.
You will need security admin privileges to run the above in a background script.
DON’T be alarmed if the field disappears while the script is running- ServiceNow appends the column name with a “Z” while the data is moved- it will come back!
I got all this information and more from SN Guru, be sure to check them out!