3622384 - 400 Bad Request error message appears while using OData API: "Failed to fetch the data preview."

When querying different entities 400 Bad Request error is thrown by the system.

Please see the following example:

"Failed to fetch data preview.

We can provide the following information to assist either you or an SAP engineer to solve the issue:

Correlation ID:

HTTP Status: 500 error

Error Code: getDataSetFailed

Technical Message: Failed to fetch the data. Error in getDataSet. Failed to get dataset data for /FormCustomSection. Cause 1: HTTP/1.1 400 Bad Request{"error" : { "code" : "COE_GENERAL_BAD_REQUEST", "message" : { "lang" : "en-US", "value" : "[COE0018]FormDataId, formContentId and secIndex can not be null or empty!" } } } Code:99999;"

SAP SuccessFactors HCM Core 2505

1. Query for example FormCustomSection without setting value for formDataId, formContentId or sectionIndex.
2. See the error message.

The request is malformed, as the syntax of the query is invalid.

Correct the syntax of the request according to the description in guide.

To get more information on the invalid syntax of the request, go to the Developer Trace in the Log Viewer and search for the log entry identified by the log entry ID. You can find the log entry ID in the error response that is returned by the service.

Reference can be found here for the example that is used in this KBA: FormCustomSection | SAP Help Portal

HTTP Status Code: 400 (Bad Request) | SAP Help Portal

SuccessFactors, SF, PMGM, OData API, 400 error, bad request, fetch, data, getDataSet, FormCustomSection, syntax, query, null, empty, Failed to fetch data preview , KBA , LOD-SF-PM-API , Webservices, OData APIs , How To

SAP SuccessFactors HCM Core 2505 ; SAP SuccessFactors Performance & Goals all versions