Symptom
Starting in 1H 2025, you won't be able to create or update a candidate with an invalid or duplicate email address in the preview instance where the Gigya migration is done (even if Gigya is turned off).
This validation is added to support Gigya enablement.
Environment
- SAP SuccessFactors Recruiting Management
- SAP Customer Data Cloud
Resolution
In 1H 2025, the Gigya migration will be completed for all Preview instances where the prerequisites are met. As part of this release, improved checks have been added to keep candidate email data accurate and consistent.
Moving forward, it will no longer be possible to create or update candidate records using invalid email formats (e.g., "user@domain", "example.com") or duplicate email addresses already associated with another candidate (e.g., reusing "jane.doe@example.com" for multiple accounts).
This applies even if the Gigya feature is not enabled, since the migration is done in all Preview instances.
The update makes sure that every candidate email address in the system is unique and correctly formatted, stopping possible conflicts or mismatches. Consequently, the system will now always reject wrong or duplicate emails.
This improvement supports Gigya integration, which needs unique and valid emails for smooth operation.
In production, until the migration is completed, this check will not be active.
See Also
Keywords
CDC, email, validation, preview, test, dummy, customer, data, cloud , KBA , LOD-SF-RCM-CAN-CDC , Customer Data Cloud Authentication , How To