Symptom
- The UI does not respect the group order when a field is set as conditional in custom MDF objects.
- when you add fields used as conditionals in a group in MDF UI, fields are displaying outside this group in the People Profile.
- Conditional fields' displaying order will not always follow the field's order set in Manage Configuration UI or Object Level.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Environment
SAP SuccessFactors HCM Suite
Reproducing the Issue
- In Manage Configuration UI, you add a conditioned field (for example test_condition has a condition to Period) in a group:
- However, when you go to the People Profile and tries to add a record, you notice that the conditioned field does not appear inside the group:
Resolution
This is expected behavior. For conditional fields, based on conditions, backend will evaluate and pass the set of fields to the front end UI. The UI renders upon receiving the fields. It is not certain in which those conditional fields can be sent from backend.
See Also
Keywords
SF, metadata framework, condition field, group, MDF, UI, MDF UI, people profile , MDF portlet, Conditional, Condition Association, INC4607805, field display order, order , KBA , LOD-SF-MDF-UI , UI Config, Layout & Rules , LOD-SF-MDF-PP3 , MDF on People Profile , How To
SAP Knowledge Base Article - Public