Consecutive intraday-data extractions differ in their contents (TRTHv2)

Hi,
We are retrieving different extraction contents in consecutive calls to the REST Api of TRTH.
The endpoint and report template used for accessing the intraday data are shown below:
/Extractions/TickHistoryIntradaySummariesReportTemplates
{
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ReportTemplates.TickHistoryIntradaySummariesReportTemplate",
"ShowColumnHeaders": false,
"Name": "E24584_REQUESTINTRADAY_0123456789_TEMPL_33164",
"Headers": [],
"Trailers": [],
"ContentFields": [{
"Format": null,
"FieldName": "Open"
}, {
"Format": null,
"FieldName": "High"
}, {
"Format": null,
"FieldName": "Low"
}, {
"Format": null,
"FieldName": "Last"
}, {
"Format": null,
"FieldName": "Volume"
}, {
"Format": null,
"FieldName": "Open Ask"
}, {
"Format": null,
"FieldName": "High Ask"
}, {
"Format": null,
"FieldName": "Low Ask"
}, {
"Format": null,
"FieldName": "Close Ask"
}, {
"Format": null,
"FieldName": "Open Bid"
}, {
"Format": null,
"FieldName": "High Bid"
}, {
"Format": null,
"FieldName": "Low Bid"
}, {
"Format": null,
"FieldName": "Close Bid"
}],
"Condition": {
"MessageTimeStampIn": "LocalExchangeTime",
"ReportDateRangeType": "Range",
"QueryStartDate": "2017-09-14T00:00:00.000",
"QueryEndDate": "2017-09-14T23:59:59.000",
"DisplaySourceRIC": false,
"SummaryInterval": "FiveMinutes"
}
}
After executing several times this data access, we get differences in the contents of their related extractions (extraction records that appears in one side that don't in the other one and vice-versa)
Some screenshots from the comparison tool used are provided:
Any idea about what is happening?
Thanks.
Regards,
Ricardo
Answers
-
Hello @ricardo.siguero,
This does not look right to me, too.
However, for a content question, to get the content question routed to the correct content team within Thomson Reuters, and answered quickly and most efficiently, please either open them in My Account Raise A Case for Tick History Version 2, or call your local Thomson Reuters Helpdesk and raise a content-related question.
If you are not able to do this, please add a comment here, and I will open a case on your behalf and share the resolution back with you.
Ok?
-Zoya
0 -
Hi, @zoya.farberov
Thank you for your help. I'd appreciate you could open a case on my behalf.
Regards,
Ricardo
0 -
0
-
Thanks, @zoya.farberov
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
- 690 Datastream
- 1.5K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 560 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 281 Open PermID
- 46 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 724 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛