Hello @Hubert CANEVET,

Perhaps this would help to further clarify On Demand vs Scheduled approaches, to be able to examine both types of request/response visually.

Have you had a chance to download and run the GUI client example

C# Example Application ?

The example has On Demand Extractions section as well as Schedule Example section, one would just run Authentication-> RequestToken first, and then trigger the requests of interests, and be able to examine both types of requests with the corresponding responses in detail, in HTTP tab on the right.

@Hubert CANEVET

There are two approaches for data extractions which cannot be mixed up.

- Scheduled extractions

Scheduled extractions use instrument lists, report templates and schedules that are stored on the server, and visible in the web GUI. You need to create instrument list, report template and schedule and then get extracted data from the server.

- On Demand extractions

On Demand extractions use simplified high level API calls that create extractions on the fly. They do not have their equivalent in the GUI. Instrument list and report template is not stored in the server. Instrument lists and field lists are passed as a parameter to the API call. Also, Report template are passed as Extraction Request to the same API call.

The ".Net SDK Tutorial 3 - GUI control calls - Lists reports schedules" tutorial is about the Scheduled extractions, so there is no information related to On Demand extractions such as Extraction Request in this tutorial. For On Demand extractions, please see this ".Net SDK Tutorial 5: On Demand extraction, file IO" tutorial. There is another example code in the "C# Example Application" which can be downloaded from this page.

For more information about the difference between the extraction approaches, please see this tutorial.

Hope this helps.

Hello,

Well yes thank you, but TickHistoryIntradaySummariesExtractionRequest can only be called asynchronously, so it must be scheduled.

_

Oh, I realize what you mean : I mentioned a documentation for OnDemand extractions.

Well, I should like to ask another question : did you test the code that is given in the demo application ?

When I say that "TickHistoryIntradaySummariesExtractionRequest can only be called asynchronously, so it must be scheduled", it is because it has been confirmed to me by Thomson Reuters, after I noticed that the proposed code returned hyeroglyphs, that is was not a question of characters set, and that some other examples that were sent to me stated an async call.

Hello, thank you for your answer.

I just looked at the page "Schedule Extractions - Immediate" in the example application. The proposed code does not contain "ExtractionRequest". So, maybe I do not need it.