Support Board
Date/Time: Tue, 16 Sep 2025 04:24:41 +0000
Post From: DTC test client not supporting OCO and bracket orders
| [2020-03-27 05:06:31] |
| |
|
2. What the Sierra Chart log is showing is the internal order ID. What is called the client order ID is different. That is internally generated and has an additional value. 3. The Git repository is now deleted. It is just not maintained anymore and were not going to say anything further about this. You definitely cannot use the documentation to determine field order. Do not do that. We should not even have to say this. That should be overwhelmingly clear. This is not making any sense because you already have a data structure to work with which is controlling the field order. You should not be attempting to do this manually. Otherwise, you can skip over padding. 4. Refer to: Data and Trading Communications (DTC) Protocol Test Client: Populating Symbol List in Sierra Chart In particular refer to the field IsFinalMessage. Must relate to that. 5. The documentation for that field is updated. Do not use it. It has only specialized purposes. The main issue is that some documentation on the DTC website is outdated and does not match the latest header files. Some new fields may not be documented. We will get to those. Give us an example of what does not match.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2020-03-27 05:11:42
|