Tick history raw data extract is not sort in timestamp
Hi,
I have a python code to use REST API to extract tick history raw from DSS. The extraction works but the file output is not sort by timestamp but instead sort by FIDs. How can I fix that?
Below is the example using my program to extract 0005.HK on Nov 1 from 0930 - 1000 local exchange time, for FIDs 22, 25 and 6. Here's a snapshot of the extraction using my program. Its sorted by BID (22), following by ASK (25) and then by TRDPRC_1 (6)
I compare the same extraction using TRTH with the following template which is same as my program
Below is the extract from TRTH. You can see the data is sorted by timestamp.
Best Answer
-
The request contains only one FID.
Therefore, the result contains only values of the TRDPRC_1 field.
0
Answers
-
Please share the request message that you are using.
I used the following request.
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TickHistoryRawExtractionRequest",
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [{
"Identifier": "0005.HK",
"IdentifierType": "Ric"
}],"ValidationOptions": {"AllowHistoricalInstruments": true}
},
"Condition": {
"MessageTimeStampIn": "LocalExchangeTime",
"ReportDateRangeType": "Range",
"QueryStartDate": "2021-11-01T01:30:00.000Z",
"QueryEndDate": "2021-11-01T02:00:00.000Z",
"ExtractBy": "Ric",
"SortBy": "SingleByRic",
"DomainCode": "MarketPrice",
"Fids": "22,25,6",
"DisplaySourceRIC": true,
"FidListOperator": "OR"
}
}
}The output is:
0 -
This is the code
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TickHistoryRawExtractionRequest",
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": list_of_ric2,
"UseUserPreferencesForValidationOptions":"false"
},
"Condition": {
"DateRangeTimeZone": DateRangeTimeZone,
"TimeRangeMode": TimeRangeMode,
"MessageTimeStampIn": MessageTimeStampIn,
"ReportDateRangeType": "Range",
"QueryStartDate": start_datetime,
"QueryEndDate": end_datetime,
"ExtractBy": ExtractBy,
"SortBy": SortBy,
"DomainCode": DomainCode,
"DisplaySourceRIC":"false",
"Fids": ",".join(fids)
}
}
}And this is what I input into my program
0 -
The request message doesn't have the FidListOperator property. I checked and found that, on my account, the default value is "AND" so the output is:
Please check the request message with other tools, such as Postman or curl.
0 -
Thanks. I tried but still giving me the same output...
"Condition": {
"DateRangeTimeZone": DateRangeTimeZone,
"TimeRangeMode": TimeRangeMode,
"MessageTimeStampIn": MessageTimeStampIn,
"ReportDateRangeType": "Range",
"QueryStartDate": start_datetime,
"QueryEndDate": end_datetime,
"ExtractBy": ExtractBy,
"SortBy": SortBy,
"DomainCode": DomainCode,
"DisplaySourceRIC":"false",
"Fids": ",".join(fids),
"FidListOperator": "AND"
}0 -
With the "AND" operator, the output should be like this:
Please check the request message with other tools, such as Postman or curl.
0 -
Sorry for the delay in getting back. I tried again and output still sorted by the FIDs instead of time of the update. The following is the actual parameter passed to in ExtractionRequest.
@{'ExtractionRequest': {'@odata.type': '#DataScope.Select.Api.Extractions.ExtractionRequests.TickHistoryRawExtractionRequest', 'IdentifierList': {'@odata.type': '#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList', 'InstrumentIdentifiers': [{'Identifier': '3333.HK', 'IdentifierType': 'Ric'}], 'UseUserPreferencesForValidationOptions': 'false'}, 'Condition': {'DateRangeTimeZone': 'Local Exchange Time Zone', 'TimeRangeMode': 'Inclusive', 'MessageTimeStampIn': 'LocalExchangeTime', 'ReportDateRangeType': 'Range', 'QueryStartDate': '2021-11-08T10:00:00.000Z', 'QueryEndDate': '2021-11-08T10:30:00.000Z', 'ExtractBy': 'Entity', 'SortBy': 'SingleByRic', 'DomainCode': 'MarketPrice', 'DisplaySourceRIC': 'false', 'Fids': '6', 'FidListOperator': 'AND'}}}
0 -
I have fixed the code and issue is fixed. You can close the ticket. Thanks for the help.
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 615 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 249 ETA
- 554 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 643 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 192 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛