3753316 - Does PPX View / Edit support the null value if field is not marked as required in Manage Data and Workflows?

• In a custom MDF object, some non‑required picklist fields (values: Yes/No) revert to the previous value when the value is cleared to NULL and saved when Inserting New Record - both in a Workflow and in Manage Data.

• SAP SuccessFactors HCM Suite
• Metadata Framework (MDF)

1. In a custom MDF object, a field type is Picklist (values: Yes/No) and is not marked as required.
2. There is a first record created, with a selection picked - either Yes or No.
3. Insert a new record and set that picklist field to “No selection” (NULL).
4. Save.
5. On the workflow approval page or in Manage Data, observe that the field value reverts to the previous effective value instead of remaining NULL.

As per UX design, PPX view / edit supports NULL values for non‑required picklist fields.

However, Workflows Approval Page and Manage Data do not support NULL for such picklist fields.

Consequently, when cleared to NULL and routed to workflow/Manage Data, the value is kept as the previous effective value.

• If customers want to use the "No Selection" option across PPX (workflow approval and Manage Data), change the affected fields to use the data type “Generic Object (GO)”, which supports no selection on all pages.
• If switching to a GO data type is not feasible, avoid clearing such picklist fields to NULL when changes will be routed to workflow; use an explicit value (for example, Yes/No) or boolean data type to ensure consistency.

• KBA 2208066 - How to create a Custom MDF Portlet in the Employee/People Profile
• Help Portal - MDF Configurations for Latest People Profile
• SAP Community - MDF Objects in Latest People Profile

mdf, workflow approval page, manage data, picklist, yes/no, null, no selection, revert to previous value, onSave rule, custom mdf object, people profile, ppx, generic object picklist, go picklist, expected behavior , KBA , LOD-SF-MDF-PPX , MDF on New People Profile , How To