Limit on Interger in API

we are getting errors within the DataScope Select REST API (C# SDK) trying to receive the "Total Net Asstes" field for the RIC "LP62003260".
I already found out, that the value of this field is lager than the standard integer size. So the API returns an "TRN" for truncated, which leads to an parsing error in the C# SDK.
I'm able to change integer length in the DataScope Select Web Interface. (see my screenshot) With an increased interger length, I get the correct value.
My question is: How can I change the integer length during extractions with the C# REST API SKD?
Best Answer
-
This should be a limitation of the DSS REST API. I got the same Truncation Warning when using the DSS REST with Postman.
The request is:
{
"ExtractionRequest": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.TermsAndConditionsExtractionRequest",
"ContentFieldNames": [
"RIC",
"CUSIP",
"ISIN",
"SEDOL",
"Issuer OrgID",
"Currency Code",
"Total Net Assets"
],
"IdentifierList": {
"@odata.type": "#DataScope.Select.Api.Extractions.ExtractionRequests.InstrumentIdentifierList",
"InstrumentIdentifiers": [
{
"Identifier": "LP62003260",
"IdentifierType": "Ric"
}
]
}
}
}The output is:
{
"@odata.context": "https://selectapi.datascope.refinitiv.com/RestApi/v1/$metadata#DataScope.Select.Api.Extractions.ExtractionRequests.ExtractionResult",
"Contents": [
{
"IdentifierType": "Ric",
"Identifier": "LP62003260",
"Error": "Parsing error for field \"Total Net Assets\", value \"TRN\", format type \"Number\". ",
"RIC": "LP62003260",
"CUSIP": null,
"ISIN": "JP3027650005",
"SEDOL": "6378079",
"Issuer OrgID": "140766",
"Currency Code": "JPY",
"Total Net Assets": null
}
],The note file contains:
Truncation Warning: Some values for Total Net Assets were truncated, (integer places = 12, largest integer width detected was 13).
You need to contact the Datascope Select product team directly to confirm it.
As I know, DecimalPlaces and IntegerPlaces can't be specified in the on-demand extraction. These properties are supported when creating a report template and using schedule extraction.
For more information, please refer to the answer in this thread.
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
- 685 Datastream
- 1.4K DSS
- 615 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
- 252 ETA
- 556 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
- 275 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
- 652 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
- 104 UPA
- 193 TREP Infrastructure
- 228 TRKD
- 917 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛