Question on decimal and integer setting on DSS API

Regarding the default data type for two fields that we are calling on the Datascope API. The Accumulated Volume Unscaled and Open Interest fields, we are currently configured to consume these are decimals. However, my understanding of these fields and the responses that we receive via the Datascope API requests, suggest that they should be integers. If we were to change this request so that we call just for integers, do you see there being any issues with this? What would happen if the fields were represented as a decimal, but we coded to only consume integers, would this return a null value, or would it truncate?
Best Answer
-
According to the DataScope Select Data Content Guide, the type of Accumulated Volume Unscaled and Open Interest fields are numeric with decimal points.
However, from their definitions, they look like to be integers. Therefore, you need to directly contact the DSS support team via MyRefinitiv to verify that the Accumulated Volume Unscaled and Open Interest fields can have decimal points.
For converting those fields to integers, the behavior should depend on the programming languages.
For example, if I use C# with the DSS .NET library to extract EndOfDayPricingExtractionRequest, the values are returned as objects.
foreach (KeyValuePair<string, object> item in row.DynamicProperties)
{
if(item.Key == "Universal Close Price")
{
int temp = Convert.ToInt32(item.Value);
Console.WriteLine(temp);
}
}Then, if I convert the object to an integer by using Convert.ToInt32(item.Value), the returned integer will be rounded. For example:
Object => Integer
108.91 => 109
46.25 => 46
103.5 => 104
null => 00
Answers
-
Hello @rishabh.nahata,
It would help to know, which request type you use.
Per specific request type, you can request all available content fields, with their type. For example, we request and examine fieldtypes for EndOfDayPricing:
{{protocol}}{{host}}{{api}}Extractions/GetValidContentFieldTypes(ReportTemplateType=ThomsonReuters.Dss.Api.Extractions.ReportTemplates.ReportTemplateTypes'EndOfDayPricing'
You should process the field result according to the field type, if I understand your question correctly.
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
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 24 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 279 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 713 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
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛