Support Board
Date/Time: Thu, 27 Feb 2025 04:35:49 +0000
Trade Activity Log issue after upgrade to 2270
View Count: 573
| [2021-06-12 22:53:19] |
| Tony - Posts: 549 |
|
Hi, I upgraded from 2253 to 2270 this morning, and noticed some issues with Trade Activity Log. I export activity logs every week, so in the SavedTradeActivity folder, I have one text file for each of past weeks. After I upgraded to 2270, I was only able to import log of the very recent week, and failed for any other weeks. There were no error messages, the Log stayed blank after I went File-->Import and selected the text file I was trying to import. So I switched back to 2253 and everything works fine. Thanks |
| [2021-06-13 01:32:09] |
| |
|
This does not make sense to us. Why is this the case?: fter I upgraded to 2270, I was only able to import log of the very recent week, and failed for any other weeks.
Certainly we do not know. Nothing has changed regarding this. If one file works any of them should work. Are the files different in some way?
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: 2021-06-13 01:32:26
|
| [2021-06-13 02:12:32] |
| |
|
It is only possible to import order fills, and if the FillExecutionServiceID if it already exists, will prevent an order fill from getting imported. So that is another thing to consider. In the next release we will add a count of the number of order fills filtered out of an import operation for this reason, in the Message Log. This information is already there. You need to look in the Trade >> Trade Service Log for this line: RemoveDuplicateFills | TradeAccount: . DatesOfRecordsToInsert: 2021-05-24, 2021-05-25, 2021-05-26, 2021-05-27, 2021-05-28, 2021-05-31, 2021-06-01, 2021-06-02, 2021-06-03, 2021-06-04, 2021-06-07, 2021-06-08, 2021-06-09, 2021-06-10, 2021-06-11, . MostRecentFileNameSearched: TradeActivityLog_2021-06-11_UTC.dmaguilera96gmailcom.data. RecordsRemovedCount: 1677. OriginalRecordsToInsertCount: 1677. RecordsToInsertCount: 0 | 2021-06-12 22:16:14.163 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: 2021-06-13 02:18:32
|
| [2021-06-13 05:34:58] |
| Tony - Posts: 549 |
|
Hi, Thanks so much for replying my message on Saturday! I think I found the problem, the message log had this line: Found 25 tokens in header line, expected 26 | 2021-06-13 07:00:22.646 * Sorry, my bad, I should've checked that earlier. For unknown reason, the last column "TimeInForce" is missing in those logs for the previous weeks, caused 2270 failed to import, after I add that column Title in the text file, I am able to import those logs. First I thought 2253 ignored missing column issue, but now I realized that could be the problem of my Linux Mint, I have another computer running Manjaro Linux, and 2253 on that computer is not able to import a log with missing column either which would be expected. Thanks for the heads up about FillExecutionServiceID and taking the time and effort to perfect Trading Log! Have a great weekend! Date Time Of Last Edit: 2021-06-13 05:51:58
|
To post a message in this thread, you need to log in with your Sierra Chart account: