3670404 - Fields from Custom MDF Objects Cannot Be Mapped to Custom Tokens - Onboarding

Fields belonging to custom MDF object definitions are not available for selection when configuring custom tokens for Onboarding email notifications. Attempting to map a field from a nested custom MDF object results in the field not appearing in the token mapping interface.

SAP SuccessFactors Onboarding

1. In Admin Center, navigate to Document Generation > Manage Template Mapping.
2. Create or edit a custom token and attempt to map a field from a custom MDF object definition, for example a field from a custom task object such as "Request Equipment."
3. In the field selection interface, observe that fields belonging to the custom MDF object are not listed and cannot be selected for the token mapping.

System limitation. The token mapping interface supports only standard SuccessFactors entity fields. Custom MDF object fields, including fields from nested or child object structures, are not exposed in the mapping interface.

This is a current system limitation. Only standard SuccessFactors entity fields are supported in the custom token mapping interface. Fields from custom MDF object definitions, including fields from custom task objects and nested or child object structures such as those accessed via sfFields.sfField paths, cannot be selected.

This limitation has been raised as a product enhancement request. To vote and follow progress on the planned improvement, visit the Influence portal: Fields from custom MDF objects cannot be mapped to custom tokens - Improvement Request.

If the affected token is also used in a custom task email template where tokens are not resolving, see KBA 3433866 - Custom tokens are not working for 'custom task' emails - Onboarding - SAP for Me.

SAP SuccessFactors Onboarding, OBX, ONB, custom token, MDF object, custom task, email token, token mapping, nested object, Generic Object, email services, sfField, custom MDF , KBA , LOD-SF-OBX-EML , Notifications , Problem