2753506 - Application error when trying to access or save candidate profiles - Recruiting Management

Application error when trying to access or save candidate profiles.

• fingerprint=3451999b7e4f0857c7929f0b824d2d3d62ef746c
• fingerprint=aa40e2a1605ca1e66e43f166e8aebe430e29c7af
• fingerprint=478e02e42a68ed0cc1cd7c9e1afb91aa3c57a9cf
• fingerprint=6ed23a1d14f6185544771159100381bfb68d8ea9

SAP SuccessFactors Recruiting Management

1. Access the candidate profile (could be either through the job requisition or not);
2. Get the error message
   

1. The type (text, number, picklist, etc...) of a Candidate Profile field has been changed. 
   The change of field types, such as from "text" to "number" or from "text" to "picklist", will result in a data type mismatch for candidate profiles that had data saved before the field type change.
   
   
2. A standard Candidate Profile field has been defined with a wrong field.
   For example, this error will occur if the field id "gender" is not defined as "derived" type in the Candidate Profile template.
   
   
3. There is a field type mismatch between the Job Application template and the Candidate Profile template for the same field id.
   For example, if a field is defined as "text" in the Job Application template but as "number" in the Candidate Profile template, when the candidate updates the job application, the text value will be synchronized to the Candidate Profile, causing a data type mismatch.
   
   
4. There is a field type mismatch between the Candidate Profile template and Provisioning -> Configure Reportable Custom Fields

(For SAP Support: see internal memo)

• Cause 1:
  Standard Fields
  
  For standard fields, it is required to undo the performed field type change to maintain the field type according to the implementation guide.
  If it is necessary to have this field with the new type, a brand new field id must be created.

• Cause 2:
  Custom Fields
  
  You may have 2 options:
• Undo the field type change.
• If you have choosen to change the field type, it is required to update candidate profiles that had the data saved before the field type change. You can bulk update candidate profiles using Integration Center (Refer to KBA 3077019).
  
  

• Cause 3:
  Configure Reportable Custom Fields
  
  If custom field is added to Reportable Custom Fields at provisioning, ensure that it has the same field type as the Candidate Profiles.
  
  
• Cause 4:
  Mismatch of filed-type between the Candidate Profile and Reportable Custom Fields section in provisioning
  
  Please access your provisioning and access the reportable custom fields section and access the tab for Candidate Profile. Make sure to confirm that all the fields configured remains with the same field type. If by any chance, there is an alteration please adjust to the correct section of the field type.

Note:

After correcting the field type, please perform a metadata refresh via OData API Metadata Refresh and Export.

Raising a Support ticket

In case you are unable to identify the cause, open a Support ticket with the following information.

1. Click 'Show Error' on the error pop-up, copy and paste the error details in the issue description.
2. Company ID
3. Support Access
4. A sample candidate
5. Steps to reproduce the error

Candidate Profile Field Definition: Field ID and Field Type

RCM, recruiting, Candidate, unable, error, profile, format, convert, java.lang.Long, CustomStringField, cannot, cast, class, CustomNumberField, 6ed23a1d14f6185544771159100381bfb68d8ea9, 3451999b7e4f0857c7929f0b824d2d3d62ef746c, aa40e2a1605ca1e66e43f166e8aebe430e29c7af, 478e02e42a68ed0cc1cd7c9e1afb91aa3c57a9cf , KBA , LOD-SF-RCM-CAN , General Candidate Issues (not Offers, not Profiles) , Problem