SAP Knowledge Base Article - Public

3294721 - Hyphens (-) in custom Recruiting Field IDs can break Suite Integration - Recruiting Management


  • Recruiting Data is not flowed to Manage Pending Hires or Onboarding if there is a hyphen (-) in the mapped Recruiting Field ID.
  • Hyphens (-) in Recruiting Field IDs are all replaced with an underscore (_) in Recruit-to-Hire Data Mapping tool.


  • SAP SuccessFactors Recruiting Management
  • SAP SuccessFactors Onboarding
  • SAP SuccessFactors HXM Suite


Hyphens (-) break OData naming convention. 

The system by default converts all hyphens (-) in OData property names to an underscore (_) and this can cause Field ID mismatching.


Please do not use hyphens (-) when naming a custom Field ID, use underscores instead.
**This applies only to custom fields. You do not need to modify standard Field IDs.

To resolve the issue:

  1. Please rename the Field ID in the Recruiting template.
  2. After updating the template, please refresh the metadata manually via Admin Center > OData API Metadata Refresh and Export.


  • Please evaluate the impact before rolling out the change; renaming property name is a backward incompatible change.
  • After renaming the Field ID, it will become a blank new field. If data exists in the old field and you wish to refer the data, you can create a new field rather than renaming the Field ID in the existing field definition.


Hyphen, Dash, underscore, OData API, integration, field mapping, error, template, job requisition, application, candidate, Recruit-to-Hire Data Mapping, MPH, manage pending hires, RCM, ONB, EC, onboarding, recruiting, suite integration, candidate to employee integration , KBA , LOD-SF-OBX-RCM , Initiate onboarding from RCM , LOD-SF-RCM-MPH , Manage Pending Hire , Problem


SAP SuccessFactors HXM Suite all versions ; SAP SuccessFactors Onboarding all versions ; SAP SuccessFactors Recruiting all versions