how to interpret the OmmTime.Hour's "Gets Hour. Range is 0 - 23 where 255 indicates blank." comment
I am using C#, I am wondering how I should interpret the OmmTime.Hour's "Gets Hour. Range is 0 - 23 where 255 indicates blank." comment. Other fields of OmmTime, such as the Minute and Second fields, have similar description. Does it mean the entire OmmTime structure should be considered invalid?
Also, from another question I posted on the Refinitiv's forum: https://community.developers.refinitiv.com/questions/116730/how-to-handle-omminvalidusageexception-attempt-to.html
There is another generic way to check whether or not a field is empty. How should I understand the existence of these two seemingly identical features?
Best Answer
-
Thank you for reaching out to us
In EMA C#, you can check if the data is blank by using the following code.
private static void Decode(FieldList fieldList)
{
foreach (FieldEntry fieldEntry in fieldList)
{
Console.Write("Fid: " + fieldEntry.FieldId + " Name = " + fieldEntry.Name + " DataType: " + DataType.AsString(fieldEntry.Load!.DataType) + " Value: ");
if (Data.DataCode.BLANK == fieldEntry.Code)
...You can refer to the 290_Custom_Decode example in the RTSDK C# package.
0
Answers
-
Regarding the generic way to check whether a field is empty, it's common to have multiple methods for achieving the same result. It's possible that the two features serve different purposes or have different use cases, even if they appear to be identical. It might be helpful to consult the documentation or seek clarification from the community to better understand when to use each approach. By the way, have you tried using a time card calculator for your time-related tasks?
0 -
Both methods can be seen as complementary—field value Tunnel Rush checks for specific blank fields, and exception handling for more comprehensive error checking when working with OmmTime objects.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 367 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛