3698601 - [SF Mobile APP]The Content Displayed on The MDF Summary Card Differs Between the SF Web and Mobile App

Symptom

Background: In the latest people profile, for the root MDF object with no visible fields but has one-to-many composite associations.

The content displayed on the MDF summary card is inconsistent between the SF web and mobile app. The Web display follows the configure UI, but the App does not.

On certain MDF cards, the mobile app displays the last modified date and other system fields which differs from the web version.
Custom MDF Card Displays Inconsistency Between Web and SF Mobile App
Certain System Metadata Fields (e.g., "Created By") appear in SF Mobile App but not in SF Web within a Custom MDF portlet in Latest People Profile.

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

Go to Profile > Set User Permission > Manage Permission Groups
Setting-->Mobile-->Activate via Camera-->login APP-->Full Profile
The content displayed for custom MDF is different between the App and the Web

Resolution

The inconsistency is caused by a fundamental architectural difference between SF Mobile App and SF Web.

SF Web:

For the MDF Card, SF Web uses Configurable UI (Manager UI Configuration) to determine which fields to display on summary cards. Fields only appear if explicitly added to the Configurable UI.

SF Mobile App:

SF Mobile App does not support Configurable UI for summary cards. Instead, it reads directly from the domain API, which returns all read-only fields — including system metadata fields like "Created By", "Last Modified By", etc. This is working as designed on both platforms.

Fields that are subjected to this inconsistency that observed between SF Web and SF Mobile App for a custom MDF in latest people profile

Created By

Created Date

Last Modified By

Last Modified Date

MDF System Proxy User (modified on behalf of / assignment ID)

For SF Mobile App: respects the Visibility configuration of the field in configure object definition, e.g if it is "Not Visible", then from Mobile App this field will be hidden and vice versa.

For SF Web: Respects the field configuration of Manguage Configuration UI. e.g if field set with visible from Manage Configuration UI, this field will be visible in SF Web.

Resolution to the fields that are subjected to this inconsistency

Desired Behavior	Action
Show the field on Web too (match SF Mobile App)	Add the field to the Configurable UI in Manager Configuration UI
Hide the field on Mobile App too (match SF Web)	Set field visibility to Not Visible in the Configure Object Definition > Find the Field > Details

Fields That Must Always Be Hidden (Both Web & SF Mobile App):

Field	Notes
Effective Start Date	Must only appear in the header of the detail view page and should NOT appear in the detail panel or summary card.
Transaction Sequence ID	Used for multiple changes per day (Effective Dating is MCPD for the Object) on effectivity-dated objects.
DPP Subject User (RBP Subject User Field)	Must be hidden from all UIs.

Keywords

PPX, Latest People Profile, SF Mobile, SF APP, Summary Card, Configuration, Mismatch, Metadata, ConfigUI, Parent-Child object, Custom MDF, Label, Object Definitions , KBA , LOD-SF-PLT-MOB , Mobile Issues , LOD-SF-MDF , Metadata Framework , LOD-SF-MDF-PPX , MDF on New People Profile , Problem

Product

SAP SuccessFactors HCM Core all versions