[Bug]: Transaction deduplication happens even if transactions have different imported_id
s
#2562
Open
2 tasks done
Labels
bug
Something isn't working
help wanted
Extra attention is needed
transaction import
Related to manually importing transactions
Verified issue does not already exist?
What happened?
I'm using a custom script to add transaction to Actual. The script uses the
importTransactions
function of the actual API. If I import two "similar" transactions, albeit with differentimport_id
s, Actual's deduplication function merges the two transactions even if it should not.As an example, I imported the following transaction:
Import was successful and the transaction appeared on Actual. Then, I imported the following transaction, which differs in
date
andimported_id
, but has the same amount and other properties of the previous one:The second import was also successful, but the transaction did not get added to Actual. Instead, the date of the first transaction got updated to match the second one (or the second transaction was added and the first disappeared, depending on how you want to see it).
As a sanity check, I changed the amount and tried importing the transaction again (with a fresh
imported_id
):This time, a separate transaction was added to Actual.
This behavior suggests that the deduplication feature does not take different
imported_id
s into account, while it should to avoid unintentionally merging different transactions.This issue was previously discussed on Discord.
Where are you hosting Actual?
Docker
What browsers are you seeing the problem on?
Firefox
Operating System
Mac OSX
The text was updated successfully, but these errors were encountered: