Duplicate Detection

[adfra]

Hi there,

Can someone tell me why these two transactions (which are the same transfer on two accounts) are not being detected as a duplicate? (see json below)

I saw in the documentation that:
The created_at and updated_at fields are not used in the comparison by Firefly III.
The import_hash_v2 and original_source are not used in the comparison by Firefly III.
The id and transaction_journal_id fields are not used in the comparison by Firefly III.

...and also noticed that I do have differences in:
tag_id, tag, transaction_group_id

Are those the crux? The tags here are the standard import tags for importing the two accounts as separate import events - surely they should not cause the duplicate detection to fail?

Thanks in advance,
Frank

[JC5]

Hey, thanks for starting this discussion.

This probably depends more on your import settings than the transaction. Could you share your import configuration file?

Cheers,
James

[adfra]

Hi James,

Thank you! I never considered diving into the json:
"duplicate_detection_method": "",
"ignore_duplicate_lines": false,
"ignore_duplicate_transactions": false

Those would probably explain it. After having another good look I also found the associated documentation here:
https://docs.firefly-iii.org/references/data-importer/json/

It might be worth linking this from the various documentation snippets relating to duplicates. If I am honest I am a bit lost between how-to, references, tutorials etc. It would be easier to have things in less places.

[adfra]

@JC5 I did update the json and went back through the data importer dialog and firmly believe that now after(!) updating the json I only now was given additional options in the data importer UI. Before posting this yesterday I specifically checked the UI as ChatGPT suggested to "just set the setting" and I was unable to find it. So there might be a bug hidden there somewhere...

[JC5]

If you are running the data importer v1.7.5, the issue you probably ran into should be fixed already. I will take up your advise and see if I can clean up the documentation.