...
{
"statusItem": [
{
"taskIdentifier": {
"correlationId": {
"value": "89OVZ7XM47N4WUVYJ"
}
},
"status": "FAILED",
"severityCode": {
"value": "1"
},
"reason": [
{
"description": "Could not find any request with correlation id 8RTFPDOM5CQCNOVB1q"
}
]
}
],
"header": {
"sentBy": {
"value": "http://www.eagleinvsys.com/"
},
"creationTimestamp": "2018-03-22T15:22:39.864-04:00"
}
}
AdhocReport GET endpoint in MC2
This is synchronous endpoint which redirects requests to the existing AdhocReport POST endpoint transforming GET parameters into JSON HTTP body and allows using HTTP GET parameters like in the examples below.
Let's take the next uri as an example:
HTTP parameters:
entityselectiontype=EntityID&entityselectionvalue=41038M
will be transformed into:
"entityId": "41038M",
all the other parameters will be taken as is and transformed into JSON HTTP body:
{
"reportName": "41038M TEST",
"entityId": "41038M",
"beginDate": "20150101",
"endDate": "20151231",
"fields": "1 Yr Net Return vs BM,10 Yr Annual Net Return vs BM",
"outputFormat":"JSON"
}
and redirected to AdhocReport POST endpoint:
http://host:port/eagle/report/v1/adhocReport
If "fields" parameter is empty/not present in uri: http://host:port/eagle/v2/adhocreport?reportName=41038M TEST&entityselectiontype=EntityID&entityselectionvalue=41038M&beginDate=20150101&endDate=20151231&outputFormat=JSON
then it will be empty in JSON body:
{
"reportName": "41038M TEST",
"entityId": "41038M",
"beginDate": "20150101",
"endDate": "20151231",
"fields": "",
"outputFormat":"JSON"
}