3614944 - One To Many association vs One To One association [Custom MDF]

• Clicking on the pencil icon only one request appears and submit the request, everything works as expected.
• Using the "Insert New Record" option, both the previous record and the new entry are displayed simultaneously with empty fields. Then, upon clicking the arrow button to navigate, the previous record suddenly disappears.

• SAP SuccessFactors HCM suite
• Meta Data Framework (MDF)

1. Go to People profile 
2. On a custom MDF Portlet Portlet_1, click on Clock Icon.
3. Click Insert New Record.
4. See child record entry duplicated 
5. Once you collapse the first entry, it disappears and no more shows up.

There is a rule created for this MDF object that attempts to have it as a 1:1 association while the object itself is configured One To Many 

Remove or adjust the rules based on the business need. If the requirement is to set the default value, consider adding the rules on the Child object itself rather than adding to the parent object.

How to fix this without affecting existing data:

• If removing the rules is not a viable solution, export all data and check if there are multiple child records for any given object. If all the parent records have only 1 child record, then switch to 1:1 configuration.
• If there is not too much data, delete and recreate the association so that all existing data gets deleted and there is na data issue due to existing record.

mdf portlet, glitch, 1h 2025 release, insert new record, duplicate entry, effectiveStartDate, Default_Grievance_Form_Fields, Default Grievance Handling, rules adjustment, child object, parent object, 1:1 configuration, INC12889965, one to many, one to one association , KBA , LOD-SF-MDF-OBJ , Object Definition & Field Related Issues , Problem