You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
End of last year, TR introduced a feature to send gifts (e.g. some amount of stock) via email to be accepted by the recipient into their TR portfolio. This event is currently being ignored due to #161 (instead of causing an error), but it also means the event remains entirely unprocessed.
From what I can tell, there is no document related to the particular gifting event. (There are events for accepting the Terms & Conditions related to gifting, which are separate and already handled)
However, this is still a transaction that is missing from pytr export_transactions. This is because the event is not saved into the all_events.json which is used as input to the command.
Research notes
#161 skips the timelineDetailV2 for which there is not corresponding timeline event.
Note how here the id of the detail and the timeline event do not match. Deeper in the detail, in the help section's payload.contextParams we can find the corresponding timelineEventId.
End of last year, TR introduced a feature to send gifts (e.g. some amount of stock) via email to be accepted by the recipient into their TR portfolio. This event is currently being ignored due to #161 (instead of causing an error), but it also means the event remains entirely unprocessed.
From what I can tell, there is no document related to the particular gifting event. (There are events for accepting the Terms & Conditions related to gifting, which are separate and already handled)
However, this is still a transaction that is missing from
pytr export_transactions
. This is because the event is not saved into theall_events.json
which is used as input to the command.Research notes
#161 skips the
timelineDetailV2
for which there is not corresponding timeline event.pytr/pytr/timeline.py
Lines 128 to 130 in f830c55
However, it appears there is a corresponding timeline event, only the mapping we currently do based on the
id
does not match (at least in my case).Corresponding
timelineDetailV2
Note how here the
id
of the detail and the timeline event do not match. Deeper in the detail, in the help section'spayload.contextParams
we can find the correspondingtimelineEventId
.The text was updated successfully, but these errors were encountered: