We have some inherited fields from our Customer Class that also appear in out sub-classes. These are showing as Relevant Records and are available in the Eligibility Builder dropdowns, and are causing users to select the incorrect field for Engagement Policies.
Is there a way to “hide” these inherited fields? We have tried “inactivating” them in their own classes, but they still appear in the list.
@JeremyN17158224 To hide inherited fields that are marked as relevant records, you can select ‘Mark as inactive’ for each irrelevant property individually in the Relevant Records section. This action should help in managing the visibility of these inherited fields in the Engagement Policies. If the inherited fields still appear after marking them as inactive, it may be necessary to ensure that the properties are properly cached and loaded. In some cases, logging off and logging back in can help to refresh the cache and reflect the changes made.
@thulg we have tried that and then tried to log out and log back in, but the properties still persist in the dropdowns. Is there a way to refresh the report definition perhaps to update those as expected? I was hoping that was the solution, but we are not seeing the expected properties be removed.