Ondemand request filed vs schedule request file

kai fang
kai fang Newcomer
in DSS

I am building two Rest API rest to download necessary data, for the filed i choose in schedule task, i create a report with file HST_CLOSE and HSTCOLODATE, and i am trying to get the same data in an on demand request using the ElektronTimeseriesExtractionRequest, however i could not find similar filed as this two, so i could not use the rest api to collect data if my schedule rest api is down one day, is there a one by one filed table when we are comparing the on demand request and the schedule request, or actually the data source for them are totally different, so we have different field name, or should i use another on demand api request rather than the elektron time series.

Tagged:

Best Answer

  • warat.boonyanit
    warat.boonyanit LSEG
    Answer ✓

    Hi @kai fang

    Both Schedule and On-demand use the exact same fields for each template type.

    Which template are you using for the Schedule task?
    I assume it is "Tick History Raw" as that is the only template that has HST_CLOSE and HSTCLSDATE fields, am I correct?

    If you want exactly the same field, then you must use the TickHistoryRawExtractionRequest for your On-demand request.

    Unlike other templates, TickHistoryRawExtractionRequest uses Elektron Real-Time fields (because it is Elektron Real-Time Raw data).

    When you made On-demand TickHistoryRawExtractionRequest, you must specify fields in the "Condition" under "Fids". And the "Fids" must be the field id, not the field name.

    HST_CLOSE and HSTCLSDATE field ids are 21 and 79.

    Here is an example JSON.

    {
      "ExtractionRequest": {
        "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryRawExtractionRequest",
        "IdentifierList": {
          "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
          "InstrumentIdentifiers": [
            {
              "Identifier": "IBM.N",
              "IdentifierType": "Ric"
            }
          ],
          "ValidationOptions": {
            "AllowHistoricalInstruments": true,
          }
        },
        "Condition": {
          "MessageTimeStampIn": "GmtUtc",
          "ReportDateRangeType": "Range",
          "TimeRangeMode": "Inclusive",
          "QueryStartDate": "2018-10-29T00:00:00.000Z",
          "QueryEndDate": "2018-10-30T00:00:00.000Z",
          "DomainCode": "MarketPrice",
          "Fids": "21,79"
        }
      }
    }

Answers

  • Christiaan Meihsl
    Christiaan Meihsl LSEG

    @kai fang, could you please export the template you refer to in your schedule (it will deliver an XML file), change the file extension to .txt, and post it here ? That will be of help to solve your issue.

Categories