Dates fields

Hello everybody,
I still have to make some progress with the use of the search engine.
In an ExtractionRequest, I see the fields QueryStartDate and QueryEndDate, it seems rather clear that the request targets transactions with a datetime included between both.
In a ReportExtraction, I find ExtractionDateUtc, ExtractionStartUtc, and ExtractionEndUtc.
I presume that ExtractionDateUtc is the date/time when the request is supposed to be launched -probably some precisions could be brought in consideration of the trigger, I am more hesitant about ExtractionStartUtc and ExtractionEndUtc.
Are they also limits about the range of transactions, or do they precise a limit of time to execute the treatment of the transaction, a sort of timeout ?
The presence of a ReportExtraction inclines me to have a preference for the last hypothesis, but I fear to be wrong.
Best Answer
-
Refer to REST API Reference Tree in Extraction/ReportExtraction.
ExtractionDateUtc: The time and date the system recorded as when the extraction occurred. Often this is the same as ExtractionStartUtc. However, when ExtractionStart is unavailable, this value indicates a time and date that reflects when some activity regarding the extraction occurred. The value is always available. In the case of pending extractions, it is the time and date that the extraction is planned to occur.
ExtractionStartUtc: The time and date that the system recorded for the start of execution of the extraction. This value is sometimes unavailable. For example, pending extractions have not yet started or ended.
ExtractionEndUtc: The time and date that the system recorded for the end of execution of the extraction. This value is sometimes unavailable. For example, pending extractions have not yet started or ended.
For the timeout, please refer to this question.
You can refer to REST API Reference Tree for usage and description of fields.
0
Answers
-
Hello,
Thank you for this detailed answer.
Perhaps I missed it at the moment, do you know whether it is possible to display the times of messages in the forum ?
The REST API Reference Tree was something I was searching for, and that for a certain time. For this, I clicked on "All API" on top of the forum page, but obviously this was not the correct link.
So now, I know it is meaningless to provide an ExtractionStartUtc when launching an asynchronous extraction.
And I know that if a query fails for I forgot to provide dates, it is not by timeout.
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
- 687 Datastream
- 1.4K DSS
- 622 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
- 255 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 680 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
- 105 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 91 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛