Symptom
When generating export report in Integration Center, the user is getting the error "The data type of the given value String cannot be cast to the target type Edm.Decimal. Code: BadRequestException Status: Bad Request Status Code: 400"
Environment
SAP SuccessFactors Recruiting Management
Reproducing the Issue
- Go to Integration Center
- Start creating a Scheduled Simple File Output Integration
- Select the affected entity as the initial entity
- Click Next
- Then the error appears
Cause
This is caused by misconfiguration. Some possible causes include:
- One or more custom fields are configured as reportable in Provisioning but defined with different data type.
- “Status” field is configured in the candidate profile template (CPT).
Resolution
For Cause 1:
- In Provisioning > Managing Recruiting > Configure Reportable Custom Fields, open the entity (job requisition, application or candidate) where you are getting the error in Integration Center.
- Click the Save button to see possible error in the field type mapping.
- Correct the field data type mapping of field ID with warning.
- After saving the adjustment, click the 'Synchronize Existing Data' button on the page.
- Once it has completed, go to the instance Admin Center > OData API Metadata Refresh and Export and click on Refresh metadata.
For Cause 2:
Remove the "status" field from the Candidate Profile Template (CPT). According to the implementation guide, there is a disclaimer: "Don't configure this in the Candidate Profile Template. It doesn't populate with any data".
- Remove any references to the status field from the CPT and save the updated template.
- Afterwards, perform an OData metadata refresh from Admin Center > OData API Metadata Refresh and Export, and then validate the behavior again in Integration Center.
See Also
Keywords
job requistion, job application, jobreq, jobapp, candidate, candidatelight, Text, Textarea, Richtext, Boolean, Hyperlink, Object, Number, Percent, Picklist, IC, status , KBA , LOD-SF-RCM-INT , Integration Center & Intelligent Services , Problem
SAP Knowledge Base Article - Public