- Setting up field criteria on the fields of child object based on parent object effective start date.
- In a custom MDF object having parent child composite association, the child object does not take parent’s effective date into account for the availability/unavailability of the values in GO field.
- SuccessFactors Cloud HCM: MDF
- SuccessFactors Cloud HCM: MDF associations
Reproducing the Issue
While creating data for an MDF object, the values displayed in the composite child object's GO field are not restricted based on the date selected on the parent's effective start date
This is because of the field criteria not defined to check the date based on the parent's effective start date.
Effective start date for a composite object follows from the parent. If you have a field of type GO defined on the child object that needs to respect the effective dating as selected on the parent object then, the field criteria on the child object's GO needs to have the below set up shown in the screenshot.
Setting up the below criteria on the child object's will then limit the values in the drop down based on the effective start date of the parent that matches the effective start date of the referenced objects data.
- MDF: Metadata Framework
- Composite associations
- Field criteria