Deleting 'pending' transactions / transfers reloading #8718
Unanswered
alexchatwin
asked this question in
Q&A
Replies: 2 comments 14 replies
-
I'm actually not aware of transactions that are "pending" being duplicate with the ones that are "booked", is that something I should look into? |
Beta Was this translation helpful? Give feedback.
13 replies
-
If you use gocardless for import switch to external id duplicate detection, these transactions you are describing should have the same id so they will not be duplicated when then change the state |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Situation:
Hi, I'm using the gocardless automation to pull from my accounts.
I had an issue where it was pulling duplicates with booked vs pending status (I basically never want to see pending). https://github.com/orgs/firefly-iii/discussions/8276#discussioncomment-8346096
I setup an automation to delete these, then I also automatically call the purge api to remove the deletions, so that the booked transactions don't get scrubbed as duplicates by the importer
I also, separately delete one side of any transfer transactions - these have to be manually matched as the bank doesn't provide consistent data on both sides.
Problem:
When I reload to get booked transactions, I also get reloads of the deleted transfer (cos I'm purging deletes)
I know I'm deep into 'messing around' territory, can anyone think of a better way to achieve my desired state - no pending vs booked conflicts, deleted transfers not 'rising from the dead'?
Beta Was this translation helpful? Give feedback.
All reactions