Date/Time: Sun, 20 Jan 2019 01:59:34 +0000
Post From: Notice: CTS Trading Service Symbols
|T44 - Posts: 168|
CTS can easily solve this on their side and we have told them that.
We should be able to identify a futures contract by the underlying symbol, the month and year, and the exchange and the security type. They just need to allow this in their market data request. This is so simple. We shouldn't have to go through a complex procedure to look up a market ID and handle all of the failure scenarios.
The market ID concept should not even be exposed for outright futures contracts. And they should not be changing these IDs for existing futures contracts which are already listed.
Thank you for this useful information.
Sounds like poor software development practice on the part of CTS; suggest affected users make their displeasure known through their clearing firms. Anything which may "prevent a chart or Trade DOM from updating and also prevent the submission of orders" is unacceptable for production use.
There is little excuse for breaking interoperability in this way and placing an unfair burden on Sierra Chart developers.