-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cleared status resets on re-import #20
Comments
Hi @Yumekui, thanks for reporting this. I will have to check whether Actual skips updating the cleared flag if I pass |
I've had a look at this tonight and it turns out that Actual defaults the My opinion is that the defaults should only apply when creating transactions in Actual, not when updating. I will raise this with the Actual team and put this ticket on hold until then. |
Thanks for looking into this! I agree with you - defaulting the |
@Yumekui Good news! My proposed changes to the API implementation were merged earlier today, so on the next API release in February, I'll be able to hook this up on the importer side as well. Stay tuned :) |
Oh wow. That's really great news! Thank you very much for your fast response and all the work you put into this. This will make managing my finances much easier. Keep up the great work! |
Issue:
When importing transactions a second time, their
cleared
status is reset tofalse
. I have the settingimport.synchronizeClearedStatus
set tofalse
.Expected Behavior:
The cleared status should not be reset when re-importing transactions, as per my current configuration.
Reference:
According to the Actual Budget API documentation, setting the cleared status is not required. However,
convertToActualTransaction
setscleared
tofalse
when theimport.synchronizeClearedStatus
setting isfalse
:actual-moneymoney/src/utils/Importer.ts
Lines 373 to 387 in 107a8a0
Additional Information:
I'm not proficient in JavaScript but can test this behavior further once I have set up a suitable environment, which may take some time.
Please let me know if additional details are required. Thank you!
The text was updated successfully, but these errors were encountered: