The image/example below came from a demo instance, any resemblance to a live customer data is purely coincidental.
A customer has inquired why there are several Custom Foundation Object appearing in their Dynamic Role > Dynamic Role Assignment section even if its not configured in the corporate data model.
SuccessFactors Employee Central Foundation Object.
Reproducing the Issue
1. Create a custom foundation MDF object, in this example I will be creating a custom MDF named "Sub Department".
2. Create a custom string in the job information section with Type of Reference Object = Foundation Object
3. Once the field is saved go to Admin Center> Manage Organization, Pay and Job Structures > Create New > Dynamic Role
This is an expected behavior, all the fields defined in the job information section with Type of Reference Object = Foundation Object will automatically appear in the dynamic role assignment section of the dynamic role object.
Notes: The visibility of the custom-string field that references the custom foundation object (Sub department in this example) affects whether the Sub Department will be selectable in the Dynamic Role. In this example Sub department is not selectable because the visibility configuration of the custom-string is = view, if you want to make the Sub Department be selectable in the dynamic role, then you need to change the configuration to visibility=edit.
It is not possible to hide unused referenced custom foundation object in the dynamic role (In my example if the customer chooses not to use Sub department in the dynamic role object then they can just leave it as blank but it is not possible to hide the sub department in the dynamic role object).
Dynamic Role, Custom Foundation Object, MDF, Dynamic Role Assignment. , KBA , LOD-SF-EC-FOO , Foundation Objects (Organisation, Pay and Job Structures) , Problem