Starting in 15.6.1, there was an API naming convention change. If you need to change the API ID (for example, so you can sync the attributes in Roadmaps), the below issues happen:
Expected Results: Attribute still appears in the blueprint
Actual Results: Attribute no longer appears and a blank space is left where the attribute used to exist
Additionally, if the attribute was saved by users in views in the New UX, they now see error: “The selected view uses attributes that are unavailable” in the views
Release : Clarity 15.6.1 and higher versions if upgrading from a prior release with old API ID Naming convention
Component : CA PPM SAAS STUDIO
In most scenarios, changing the API Attribute ID isn't required if upgrading from a prior release, though in some scenarios like syncing roadmaps to projects, this is required which does cause the issues and a few additional steps. Regarding saved views, the attributes where the API Attribute ID was changed will be treated like a deleted attribute and it will be removed from the saved view since the system use the API Attribute ID to match against the saved view. If there is no match, it will remove that field from the saved view since it assumes that field got deleted in Studio
Another option would be to remove everything out of the section in the blueprint with the empty space, delete the section, then recreate the section and add the fields back into the section.