Hi, how can I get RAW-TAS and RAW-MD data in trth v2

@muneish.adya, you get it, but only as the 1st element of the 1st line of an update:

CARR.PA,Market Price,2016-09-29T12:00:00.942730204Z,Raw,UPDATE,UNSPECIFIED,,,,8132,,2800,13

The RIC is not included in the next lines (those with the individual updates by FID), because they are part of the same update:

,,,FID,4981,,TRTN,0.89,
,,,FID,4982,,TRTN_3MT,5.85,
etc.

In other words, an update has a kind of "header" line that includes the RIC, timestamp, and number of changed FIDs, followed by all the individual changes, one line by FID.

In V1 the RIC was in all lines. V2 removed it to avoid duplication.

@muneish.adya, maybe we are not talking about the same thing ?

I am referring to what is described in REST API Tutorial 8, i.e. a TickHistoryRawExtractionRequest. If you run the same query you should see the RIC as the first column of the first line of an update, like in this case where the RIC is CARR.PA:

CARR.PA,Market Price,2016-09-29T12:00:00.950557616Z,Raw,UPDATE,UNSPECIFIED,,,,8132,,2800,13
,,,FID,4981,,TRTN,0.89,
,,,FID,4982,,TRTN_3MT,5.85,

I retested it now to be sure.

That said, for a TickHistoryRawExtractionRequest the value of DisplaySourceRIC has no influence on the output.

@muneish.adya, the output of call TickHistoryRawExtractionRequest is predefined, i.e. TRTH output fields are not configurable.

Obviously, once you have retrieved the result from the server, you can programmatically add anything you want to it (like a SourceRIC column), but this treatment is done on your own machine independently from TRTH. And yes, you can use the RIC column for that.

In V1 the RIC was in all lines, but repeating the RIC in every single line is not very efficient in terms of processing and storage. V2 removed it to avoid duplication.

@muneish.adya, to your query: why don't I get SourceRIC in TickHistoryRawExtractionRequest even if I set "DisplaySourceRIC": true

This was submitted to the data support team. Here is their answer:

In certain cases the RIC of the item being displayed can be different from the requested RIC; this is the case for RIC aliases. It is by design that TRTH v2 replaces the TRTH v1 “Source RIC” column with other similar columns when "display Source
RIC" is set to true.
This column is an optional field, it will be delivered only if:

1. "DisplaySourceRIC": true
2. and the requested RIC is an alias RIC.

Various scenarios:

1: The request is for raw Market Price data of a normal RIC

<RIC> is always equal to 'Source RIC’, therefore the ‘Source
RIC’ is not delivered.

2: The request is for raw Market Price data of an alias RIC

<RIC> is not equal to ‘Source RIC’, therefore the ‘Alias
Underlying RIC’ is delivered (instead of ‘Source RIC’).

3: The request is for raw Market Depth data of a normal RIC

<RIC> may or may not be equal to ‘Source RIC’, therefore the ‘Market
Depth RIC’ is delivered (instead of ‘Source RIC’).

4: The request is for raw Market Depth data of an alias RIC

<RIC> is not equal to ‘Source RIC’, therefore the‘Alias
Underlying RIC’ and the ‘Market Depth RIC’ are delivered (instead of
‘Source RIC’).

In other words, TRTH v2 provides more explicit information of ‘Source RIC’ than TRTH v1.

I tried this out. Here is an example for use case 3. Request:

{
  "ExtractionRequest": {
    "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.TickHistoryMarketDepthExtractionRequest",
    "IdentifierList": {
      "@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",  
      "InstrumentIdentifiers": [{
        "Identifier": "CARR.PA",
        "IdentifierType": "Ric"
      }]
    },
    "Condition": {
      "View": "LegacyLevel2",
      "MessageTimeStampIn": "GmtUtc",
      "ReportDateRangeType": "Range",
      "QueryStartDate": "2016-09-29T12:00:00.000Z",
      "QueryEndDate": "2016-09-29T12:10:00.000Z",
      "DisplaySourceRIC": true
    }
  }
}

Result, containing the 'Market Depth RIC' (0CARR.PA):

#RIC,Domain,Date-Time,Type,MsgClass/FID number,UpdateType/Action,FID Name,FID Value,FID Enum String,PE Code,Template Number,Key/Msg Sequence Number,Market Depth RIC,Number of FIDs
CARR.PA,Market Price,2016-09-29T12:00:02.512691123Z,Legacy Level 2,UPDATE,UNSPECIFIED,,,,6508,,31440,0CARR.PA,3
,,,FID,17,,ACTIV_DATE,2016-09-29,
,,,FID,5,,TIMACT,12:00:00.000000000,
,,,FID,4148,,TIMACT_MS,43202452,
CARR.PA,Market Price,2016-09-29T12:00:03.172723827Z,Legacy Level 2,UPDATE,UNSPECIFIED,,,,6508,,31456,0CARR.PA,6

Note: this request was for a LegacyLevel2 view. For this particular instrument the Market Depth RIC is not returned if you request a RawMarketByPrice or RawMarketByOrder view.

Conclusion:

If the source RIC is the same as the RIC it will not be delivered, you can use the RIC field. If the source RIC is different from the RIC then it will be delivered, in field(s) ‘Alias Underlying RIC’ and/or ‘Market Depth RIC’.