Symptom
An HTTP 400 error occurs when consuming data of Datasphere Analytic Model or View using OData API.
Error message can be:
{"status":400,"message":"There was an issue handling the request. Please try again later or contact customer support - See correlation id XXXXXXX"}
or
{"code":"UNKNOWN_ERROR","details":{"stack":"See correlation id XXXXXXX","message":"There was an issue handling the request. Please try again later or contact customer support"}}
Error occurs only when the odata URL has selected many measures and attriburtes/dimensions, after removing some of the attriburtes/dimensions, error does not occur even though those attriburtes/dimensions are valid in Analytic Model or View. Error is not specific to certain attriburte/dimension.
Environment
SAP Datasphere
Reproducing the Issue
- Connect to the Datasphere Analytic Model or View using OData API.
- Select multiple Measures/Attributes in the Odata API URL with $select OData query parameter.
- Observe the HTTP 400 error message.
{"status":400,"message":"There was an issue handling the request. Please try again later or contact customer support - See correlation id XXXXXXX"} - Modify the URL by excluding some of the attributes/dimensions from the $select query parameter and execute the URL again.
- Observe that the URL works now without the error.
Cause
The selection returning more records than the allowed limit in HANA Cloud Database. More details is documented in SAP Note 2770570.
Resolution
To resolve this issue, please either reduce the number of attributes/dimensions or measures selected or apply more restrictive filters such as using query parameter $filter to narrow down the dataset.
See Also
Keywords
http400 error, UNKNOWN_ERROR, dsp, dwc, idmc, analytical requests, query parameter, odata URL error, Odata service, consumption API , KBA , DS-BB-ODATA , To address issues related to Odata consumption API , Problem
SAP Knowledge Base Article - Public