Table Label showing label instead of table name when update set is loaded in higher environment

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 08:33 AM
I created a custom table with few fields and then moved the updateset to higher environment. When done, table's label field shows label instead of the table name.
I checked the updateset and found that field label for the table was missing in the updateset and was not there in the customer updates of lower environment.
I tried modifying the label in higher environment but after saving it is still showing label and not the actual table.
Please guide how to get it fixed without recreating the table and recapturing it
- Labels:
-
Best Practices
-
Team Development

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 08:49 AM
Hi,
Try to find it in Lower environment, it should be there.
navigate to sys_update_xml.list and put filter like type = "Field Label" and target name = "name of your table you had given"
once you find it, move that update into an update set and deploy it.
Mark my ANSWER as CORRECT / HELPFUL if it served your purpose.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-26-2018 08:52 AM
I know it could have been fixed like this but somehow it is not there in the lower environment. may be I might have deleted 😞
That's why looking for other options how to fix it
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2019 04:06 AM
this did not work.
i tried changing the value of the label field on my table and it does not change.
the value remains "label"
do you know how to fix?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2020 11:29 AM
We created a ticket for this and ours is a little different. The lower environment has the problem but the upper environments do not (test and prod).
Their answer was to clone from Prod to Dev and it *should* fix it. We haven't cloned it yet, so I'm not sure if this will fix it but I'll update this thread when I find out.