Support Board
Date/Time: Tue, 02 Jun 2026 15:02:04 +0000
Post From: ACSIL s_SCNewOrder::TextTag maximum length and truncation behavior
| [2026-06-02 09:46:42] |
| User951086 - Posts: 29 |
|
Hello, I am using ACSIL automated trading and setting "s_SCNewOrder::TextTag" before submitting orders with "sc.BuyEntry() / sc.SellEntry()". I would like to use the TextTag only as a reference identifier for matching orders back to my own external JSONL trading journal. Example TextTag I am considering: TID=20260601_C039_V117_L_093815_042 This is approximately 37 characters. Please address following questions: 1. What is the maximum supported length for "s_SCNewOrder::TextTag" in ACSIL? 2. If the TextTag exceeds the supported length, is it truncated, rejected, or handled another way? 3. Is the same TextTag length available consistently in: - Trade Activity Log / Order Action Source - Trade Activity Log / Note field - Trade Orders window Text Tag field - ACSIL retrieval through order structures such as "s_SCTradeOrder::TextTag" 4. Is there any difference in TextTag behavior between simulated trading and live trading / external trade services? 5. Are there any characters that should be avoided in TextTag? For example: `=`, `_`, `|`, `-`, `:` 6. Is it safe to rely on TextTag as a short identifier, while storing the full detailed order metadata externally? Thank you!! Date Time Of Last Edit: 2026-06-02 09:47:05
|