Symptom
You have a custom field configured for Global Assignment and an error is being thrown while saving the transaction even when the field isn't available.
Environment
SAP SuccessFactors Employee Central
Reproducing the Issue
- Under Manage Business Configuration, configure a custom field in globalAssignmentDetails
- You can take, for example, custom-string116, which should appear on end global assignment
- Make the custom-string116 mandatory
- Go to an employee profile and add a global assignment
- custom-string116 will not be available there
- Upon saving, error is displayed, saying that the field is required and cannot be blank.
Cause
This is a product defect. System is checking the global assignment fields that are not available on the current page.
Resolution
This issue is planned to be fixed on second half-year release of 2024 (2411).
As a workaround, ensure that the field with the issue is not set as mandatory. You can make the field mandatory with business rules only on the required screen.
See Also
Keywords
ECT-235652, INC8262145, 2411, global assignment, field is required and cannot be blank, end global assignment, add global assignment, required field , KBA , LOD-SF-EC-GA , Global Assignment , Problem