- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 05:34 AM
I am unable to change the label of the field in the form in cmdb_ci_server form. I tried using saveral ways like Form design, Configure dictionary.
Appreciate any help.
Thank You in Advance.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 06:08 AM
Try deleting the old Label record and creating a new one. Or just create a new one on a child table (eg, cmdb_ci).
Labels are on the sys_documentation table.
I have fixed weird issues with labels by doing this before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 06:54 AM
Hi chuck,
Thanks for your response.
The table name is base configuration Item (cmdb).
I have checked the logs and errors. There are no errors.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 06:08 AM
Try deleting the old Label record and creating a new one. Or just create a new one on a child table (eg, cmdb_ci).
Labels are on the sys_documentation table.
I have fixed weird issues with labels by doing this before.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 06:43 AM
Hi Geoffrey
Thanks for response.
I have created new field with the required label and it is working now.
Only thing is In old label column we have around 50000 records so now I am thinking of exporting that data in my system and again upload it by using transform map in new field. Is it right direction to do it?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 06:52 AM
Hi Akshay,
If you change the label, it doesn't affect the data in the column.
Q: Did you create an entirely new field or just a new label for the old field? That seems like a bit of overkill. What I understood from Geoffrey is that he recommended creating a deleting and creating a new (label) record in sys_documentation.
For what it's worth, creating an entirely new field might have other implications like ACLs, scripting references, etc.
If you suspect your risk after creating a new field is negligible (low) then a simple script to copy the data from one field to the other is easy enough. You can do this in scripts background with something like this:
Standard disclaimer: The following code is untested, requires review and potential modifications.
(function () {
var rec = new GlideRecord('your_table');
rec.query();
while (rec.next()) {
rec.setWorkflow(false);
rec.autoSysFields(false);
rec.u_newfield = rec.u_oldfield;
rec.update();
}
})();
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-12-2016 07:11 AM