Detect securities unknown to Reuters

BTh
BTh Contributor
in DSS

When requesting data for a security through its ISIN over the DSS REST API, I find out very late that actually that security is "not in the dictionary". This happens only through a bad error that I trap when trying to get the row.DynamicProperties.Item(<field name>). It suddenly tells me that the row object is not defined anymore !

But the real reason can be found by using the exception's InnerException.GetBaseException.Message, which says: "The given key was not present in the dictionary."

Isn't there a "faster" way for me to find out about that, right after getting the result of my request ? A kind of status of the request's result ?

Tagged:

Best Answer

Answers

  • Christiaan Meihsl
    Christiaan Meihsl LSEG

    @BTh, could you please post the data request you made, with the incriminated ISIN ? That will help the community to investigate.

  • BTh
    BTh Contributor

    Hi Christiaan

    Here my request:

    extractionRequest = New RatingsExtractionRequest With {.IdentifierList = instrumentList, .ContentFieldNames = fieldNames,


    .Condition = New RatingsCondition With {


    .RatingLevel = New RatingLevel With {.IsIssue = True, .IsIssuer = False},

    .DaysAgo = 7,

    .ReportDateRangeType = ReportDateRangeType.Last,


    .IncludeInstrumentsWithNoRatings = True,

    .RatingSourcesCodes = ratingCodes}}

    With:

    • Identifier list for security with ISIN GB00BDXG0P01, Ident. type Isin
    • Filed list starting with ISIN, then Asset ID. Actually irrelevant, as the error occurs on the first field, the ISIN

    The code than triggers the error is this:

    ' Extract value


    sValue = row.DynamicProperties.Item(extractionRequest.ContentFieldNames.Item(i))

    which normally returns data, but for that ISIN, it trggers an error "row is not defined", but the catch section of the Try surrounding the whole processing of the request's result gets this:

    Catch ex As Exception


    ex.Message = "The given key was not present in the dictionary."

    I have quite a bit of code before that, which "decodes" what's in the result rows, but I get no error until that point. The result shows me 1 row with 12 fields, which is what I requested, I can decode the row.Identifier and the row.IdentifierType, the first field name using


    extractionRequest.ContentFieldNames.Item(0)

    but then the whole thing bombs on the retrieval of the row.DynamicProperties of the first field.

    HTH

    Bernard

  • veerapath.rungruengrayubkul
    veerapath.rungruengrayubkul LSEG
    @BTh

    It seems that the ISIN GB00BDXG0P01 is not valid, so the result doesn't contain any data including the ISIN field. As result, the "ISIN" key is not available in the dictionary, and then cause the error when you try to access the field directly.

  • BTh
    BTh Contributor

    Ah yes, seeing your "Error" label, I discovered I could test on row.Error for the value "Not found", and therefore trap theses non-existing ISINs as the first thing to do when processing each result row. That works fine :)

Categories