3800977 - Application Error in Legacy History UI for Custom MDF Portlet

• When the "Enable the latest Viewing, Editing and History UI" option is disabled in Configure Latest People Profile, opening the History of a custom MDF portlet (e.g., Shares/AESOP portlet) in the legacy History UI triggers an application error popup. The error is reproducible for all users.
  
  Error message observed: An application error occurred. Please try again later, or notify support
  
  
• Effective dating errors occur when re-uploading portlet data (e.g., Shares); after corrections, only a subset of records are processed successfully.
• The portlet and its history function correctly when the Latest People Profile History UI is enabled.

SAP SuccessFactors HCM Suite

1. In Configure Latest People Profile, disable “Enable the latest Viewing, Editing and History UI”.
2. Open the custom MDF portlet on People Profile and use History (legacy History UI) or attempt to update records.
3. Observe an application error; in imports with multiple effective-dated records, effective dating errors may also occur.

• The root cause is a configuration inconsistency in Configure Latest People Profile.
• Fields within Group-0 were assigned Value Type Resolvers that do not align with the Collection Resolver defined at the group level.
• When the legacy History UI attempts to render historical data, it processes field values through the incorrectly mapped resolver. 
• The Latest History UI does not exhibit this issue because it handles the resolver logic differently.

1. Review the configuration of the custom MDF portlet in Latest People Profile, focusing on the block/group that displays the child collection (Collection Resolver).
2. For every field inside the group, verify that the Value Type Resolver aligns with the same child collection configured by the group’s Collection Resolver.
3. Correct any fields mapped to a different child collection so all field Value Type Resolvers are consistent with the group-level Collection Resolver.
4. Save the configuration and clear caches as applicable.
5. Retest by opening the portlet’s History using the legacy History UI and confirm the application error no longer occurs.
6. Optional workaround: keep “Enable the latest Viewing, Editing and History UI” enabled until configuration is aligned and validated.

latest people profile, legacy history ui, mdf, custom portlet, people profile history, value type resolver, collection resolver, picklist, numberformatexception, application error, history error, effective dating, data upload, portlet configuration, ui rendering error , KBA , LOD-SF-MDF-PPX , MDF on New People Profile , Problem