Will Firefly III importer prevent re-importing deleted transactions when using external id duplicate detection?

[Rokirok]

The importer will match deleted transactions when using content-based duplicate detection in the transaction import process. Is this same behavior present when using external id field as the duplicate detection method instead of content-based duplicate detection?

I am importing transactions using Nordigen Bank Account Data API and would like the Firefly III importer not to import transactions that I have cleaned up already. Every transaction has an external id (deleted ones and the ones being imported) and those do not change between imports as far as I've seen in my testing.

TL;DR: Will Firefly III importer prevent re-importing deleted transactions when using external id duplicate detection and Nordigen Bank Account Data API?

[JC5]

Hi, thanks for starting a discussion.

Yes, Firefly III will prevent that.