Update Set Column in Customer Updates on the Update Set doesnt show up

[Erwin Tsan Fena]

When I go to my current Update Set Record, I check the customizations that I have done and change the Update Set to Default if needed. If I need to change the customization, I would go inside the record and revert it back to the global Default Update set.
However, I would like to make changes only to the "Customer Update" Related List in the Update Set. Although I can select the Update Set in the Personalize Columns section, it does not show up on the list. Strangely, it does appear on the list when I open the Customer Update on a different window. I am not sure why this is happening. Can you suggest any possible reasons?

[Amit Gujarathi]

Hi @Erwin Tsan Fena ,

I hope you are doing good.
You can try the below measures to fix your issue.

1. Check the access level and permissions for the user who is facing the issue. Ensure that the user has the necessary permissions to access and modify the "Customer Update" Related List and the Update Set.

2. Verify that the "Customer Update" Related List is included in the form layout of the Update Set record. If it is not included, add it to the form layout.

3. Check the personalize columns section and ensure that the "Customer Update" column is not hidden or removed. If it is hidden, unhide it from the personalize columns section.

4. Try clearing the user's browser cache and cookies and logging in again to see if the issue persists.

5. If the issue still persists, you can try refreshing the instance cache by navigating to System Diagnostics > Cache list, and then clicking the "Flush All" button. This will clear the instance cache and may resolve any caching issues causing the problem.

6. If none of the above steps work, you can raise a support ticket with ServiceNow to investigate the issue further. Be sure to include details of the problem, steps to reproduce it, and any error messages or logs that may be relevant.

Please mark the answer helpful if it helped in anyway.

Regards,

Amit Gujarathi

[Ankur Bawiskar]

@Erwin Tsan Fena 

Did you try to clear instance cache using cache.do and then logout and login again?

Did you try in some other browser?