Symptom
- Custom MDF blocks on latest People Profile are showing as error "No applicable renderer found".
"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
Reproducing the Issue
- Make sure Latest People Profile is enabled
- Navigate to People Profile
- Check for one MDF block that it is displaying an error "No applicable renderer found"
Cause
This issue can be caused by either:
- Customized standard MDF Field name
- As an example, the standard field name of "Transaction Sequence Number" should be "transactionSequence".
- If you change the default name of a standard field to "mdfSystemTransactionSequence", the issue will happen.
- It is not only for "Transaction Sequence Number", but also for other system standard fields.
- The MDF Internal Fields (ex: mdfSystemLastModifiedBy and mdfSystemLastModifiedDate) of a child object was added
- The System Internal Field IDs are changed causing the issue ("No applicable renderer found') on the UI.
- This issue was already handled for parent objects but not on child objects.
Resolution
For the following issue:
- Customized standard MDF Field name
- Engineering team has made a fix in code to make it compatible for customized standard fields.
- The fix will be released in 1H 2025 (b2505).
- Workaround: Before the fix version is release, customer could change the customized standard field name back to the default one.
- The MDF Internal Fields (ex: mdfSystemLastModifiedBy and mdfSystemLastModifiedDate) of a child object was added.
- The code fix for this will be deployed on 2H 2025 (b2511).
See Also
Keywords
Custom MDF blocks, Error, People Profile, latest People Profile, No applicable renderer found, standard field name, Transacation Sequence Number, transactionSequence , KBA , LOD-SF-MDF-PPX , MDF on New People Profile , Problem
Product
SAP SuccessFactors HCM Suite all versions