How can I get the key in string type?
I am currently receiving market information for the RIC codes NQZ4
and ESZ4
, with the domain type set to MARKET_BY_PRICE
.
The code I am using generates a unique key for each order in the order book entry, followed by the associated fields.
Map.getEntry().getKey().getBuffer()
Item Name: ESZ24
Service Name: hEDD
Map Summary data:
Name: SEQNUM Value: 1.66947e+07
Name: ACTIV_DATE Value: 11 / 12 / 2024
Name: TIMACT_MS Value: 37283853
Name: TIMACT_NS Value: 10:21:23:853
Action = Update, key = 3132 3a36 3035 3232 352f 32 12:605225/2
Entry data:
Name: ORDER_TONE Value: 1
Name: NO_ORD Value: 37
Name: ACC_SIZE Value: 76
Name: LV_TIM_NS Value: 10:21:23:853
Name: LV_TIM_MS Value: 37283853
Name: LV_DATE Value: 11 / 12 / 2024
Name: ORDER_PRC Value: 6052.25
Name: ORDER_SIDE Value: ASK
My question is: How can I retrieve the key as a string? I attempted the following code, but it did not work as expected, resulting in truncated values.
const EmaBuffer& keyBuff = map.getEntry().getKey().getBuffer();
std::string key(keyBuff.c_buf(), keyBuff.length());
Output : Key : 12:605225/2
Could you assist me with this?
Best Answer
-
Yes. I was getting same with my code itself. My question was key looks like below,
Action = Update, key = 3132 3a36 3035 3232 352f 32 12:605225/2
Out of that we are only getting "12:605225/2". From this what I understood is after colon it indicate the price of the orderbook and after slash it indicates that side of the order(i.e BUY/ASK). What is the value it indicates before the colon?
0
Answers
-
Thank you for reaching out to us.
You can use this one.
EmaString keyStr; … keyStr.set(me.getKey().getBuffer().c_buf(), me.getKey().getBuffer().length());
cout << endl << keyStr << endl;The output looks like this:
The values are not truncated.
0 -
As this forum is more for programming type queries, rather than content queries - I would recommend you raise a 'I need help understanding content within the product' ticket with our helpdesk. That way a Content specialist can work closely with you and verify the assumption.
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 684 Datastream
- 1.4K DSS
- 613 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
- 248 ETA
- 552 WebSocket API
- 37 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
- 629 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
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛