I do see a good reason to do so, at least in my use case. I am imagining case where if I were to download good number of transfers transactions (I do so for last three months in a moving window fashion through CSV, QIF and OFX imports), I could end up needing to touch many other accounts, possibly ones that were already reconciled after import would entail needless download again, and then re-imports again for those accounts, especially now that description can be appended from two sides of import of a transaction. Since CSV and QIF already permits reimport and reconciliation window, having the same capabilities on OFX/QFX would make the behavior consistent amongst three heavily used import methods in the States. I do not see any adverse effect from permitting it. If it finds same FITID, permit to update, update and reconcile existing one or just reconcile existing one. Just a thought....
-----Original Message----- From: Jean Laroche <rip...@gmail.com> Sent: Monday, May 13, 2024 6:19 PM To: gnucash-user@gnucash.org Subject: Re: [GNC] Question about OFX imports Also, you definitely would not want to double-import the same transaction, so there isn't a good reason to want to mock with the FITID. What *could* be useful (but in extremely rare cases) would be to force a re-import of the same transaction despite the fact that it's been imported previous, while avoiding a duplication (i.e. the second import would update the existing transaction instead of being skipped altogether). But I don't see a good reason to implement that at this point... Deleting the existing one achieves the same result for these rare cases. Jean On 5/13/24 3:12 PM, David Reiser via gnucash-user wrote: >> On May 13, 2024, at 17:50, David Carlson<david.carlson....@gmail.com> wrote: >> >> Now it is my turn to ask a question. >> >> My bank recently had an issue with the description text for a few >> transactions that resulted in the transactions being reposted with >> corrected descriptions. Now I am trying to import the corrected >> transactions but they do not appear in the OFX importer even though >> they are in the file generated by the bank. >> >> My question is: If I delete the previously imported transactions, can >> I import the corrected transactions? > yes. > >> A corollary; is there any way to check, edit or remove the FITID >> value of a transaction that prevents the duplicate import without >> doing tricks in the OFX file before importing? > only if you are willing to risk damaging your datafile editing it outside of > gnucash. The FITID values are stored as a key/value pair like: > > <slot> > <slot:key>online_id</slot:key> > <slot:value type="string">20180906246910059666</slot:value> > </slot> > > and finding specific transactions in the raw XML is harder than you might > imagine. The online_id is not available to the user anywhere in the gnucash > interface. > > I have never tried editing a gnucash SQL file outside of gnucash. > >> -- >> David Carlson >> _______________________________________________ > > -- > Dave Reiser > dbrei...@icloud.com > > > > > > _______________________________________________ > gnucash-user mailing list > gnucash-user@gnucash.org > To update your subscription preferences or to unsubscribe: > https://lists.gnucash.org/mailman/listinfo/gnucash-user > ----- > Please remember to CC this list on all your replies. > You can do this by using Reply-To-List or Reply-All. _______________________________________________ gnucash-user mailing list gnucash-user@gnucash.org To update your subscription preferences or to unsubscribe: https://lists.gnucash.org/mailman/listinfo/gnucash-user ----- Please remember to CC this list on all your replies. You can do this by using Reply-To-List or Reply-All.
