How to get rediorderid in Python?
Firstly, I want to get RediOrderID from my Python. After i run the script of ordersending as :
msg = win32com.client.VARIANT(win32com.client.pythoncom.VT_BYREF | win32com.client.pythoncom.VT_VARIANT, None)
res = o.Submit(msg)
The returned result as res have value only "True" or "False" but i expect to get OrderID.
Then i develop my C# to run another process like cachecontrol to capture the return message from wincom32. Now, my ordersending process was change to able to send more than one order at a time. So, this manner can occur of race condition e.g. order a and b are send at the same time to mapping return of b may be matched to order a. then i found the document of Refinitiv REDI EMS API Spec, Document Version 2.4, Date of issue: 3 December 2019, from page 3 in the document, which "Member Name" can we use?. In the document said "ClientData --String 36 -- This field is free text field which persist throughout lifecycle of an order. It is NOT recommended using this field if your firm use portfolio trader or FIX ticket.", can i use another member name?? or do you have any suggest to track the RediOrderID after order was submitted, not concept of cachecontrol?
Best Answer
-
Hello @alongkot.b ,
If I understand your question correctly, the answer is no, you will not be able to monitor/track, cancel or modify order in Python, as REDI Python offers very limited functionality.
You will be able to monitor, cancel or modify orders in C#, please refer to REDI API Spec and REDI Tutorials -> C# for more information on REDI Order Monitoring and on cancelling order by OrderRefKey, perhaps this previous discussion thread can be of more help.
You will also be able to monitor, cancel and modify in VB/Excel, please refer to the relevant spec and VB/Excel tutorial information.
Please let us know of this helps?
0
Answers
-
Hi @zoya.farberov ,
your answer can help me for sure. my system use python to send the order and C# to get the order status. but i still have one more question of the member name. i want to know a reason of clientdata the document suggest me to do not use and which member name you suggest me to use?
0 -
Hello @alongkot.b ,
If I understand your question correctly, to differentiate the orders as well as cancel the orders if they are not executed, you can use OrdeRefKey, as it is a unique identifier for the order, and is system-generated. For example:
res = orderCache.CancelByKey("r151681", "gS05779521", err);
In terms of using ClientData that is self-selected:
Where I think you may wish to be careful is, setting the same ClientData on multiple orders is not supported and can lead to issues.
Secondly not recommended if "using portfolio trader or FIX ticket ", I think otherwise it is ok to populate it.
Hope this helps
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 中文论坛