Kalpesh, That code is in C. If the question is along the lines of "how does this function work" it's probably better in gnucash-devel or on IRC. If you find something specific to the problem at hand it's better to keep it in this thread for context.
Regards, John Ralls > On Dec 19, 2023, at 06:45, Kalpesh Patel <kalpesh.pa...@usa.net> wrote: > > Thank you for that excellent insight. > > I'll review the code to see if there is anything glaring that I can see > before going on the code modification/compile/test cycles. If I have query in > regards to the C++ code, shall I do so here or shall I switch over to the > gnucash-devel? > > -----Original Message----- > From: john <jra...@ceridwen.us <mailto:jra...@ceridwen.us>> > Sent: Monday, December 18, 2023 8:55 PM > To: Kalpesh Patel <kalpesh.pa...@usa.net <mailto:kalpesh.pa...@usa.net>> > Cc: David Carlson <david.carlson....@gmail.com > <mailto:david.carlson....@gmail.com>>; Gnucash Users > <gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org>> > Subject: Re: [GNC] Import issue > > Somebody commented out all of the DEBUG logging statements in > import-backend.cpp so you'd need to uncomment them then build GnuCash > yourself, after which you'd run it from the command line with --log > gnc.import=debug to get the messages added to the tracefile. Dunno how > enlightening that would be. FWIW the matching function starts at > https://github.com/Gnucash/gnucash/blob/bf460b0040f8c9837cca198a9daba83a91c6c35b/gnucash/import-export/import-backend.cpp#L560. > > There is one other option besides importing the transaction as a new one: > Don't import it at all by unchecking all three checkboxes in the match window. > > Regards, > John Ralls > > >> On Dec 18, 2023, at 16:02, Kalpesh Patel <kalpesh.pa...@usa.net> wrot >> >> I had replied as part of broader response, hence the reason for leaving it >> out to the group. Anyways, thank you for doing so. >> >> >> >> While behavior you mentioned is also related to matcher engine during >> import, Gyle’s issue seems not to intersect with yours (function vs. UI). >> >> >> >> Yes, I have seen behavior where GNC does not present the correct, or any >> existing transaction to match an incoming transaction to during the import >> as you mentioned but for me it shows up on very rare occasion. I use the >> same work around, i.e., import it as a new. I had done cursory debugging and >> I believe I had vaguely narrowed it down to a reason that the transaction >> that was already present before import had a date that was AFTER the same >> to-be-matched transaction in the import. I believe I see them for so called >> “Early Direct Deposit” transaction types. I haven’t paid close attention in >> the past but now I’ll have to pay close attention to see what the state of >> transactions are when it happens next time. It makes logical sense that >> matcher engine would be working with transactions from the register that is >> cutoff past “now” for matching. >> >> >> >> I wonder if there is a way to set the matcher engine in a debug mode, >> similar to F::Q debug facility. I am still on 4.14 version of GNC but I >> wouldn’t mind a pointer to a documentation showing debugging various major >> functions. >> >> >> >> From: David Carlson <david.carlson....@gmail.com >> <mailto:david.carlson....@gmail.com>> >> Sent: Monday, December 18, 2023 5:51 PM >> To: Kalpesh Patel <kalpesh.pa...@usa.net <mailto:kalpesh.pa...@usa.net> >> <mailto:kalpesh.pa...@usa.net>>; Gnucash Users >> <gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org> >> <mailto:gnucash-user@gnucash.org>> >> Subject: Re: [GNC] Import issue >> >> >> >> You forgot to cc to users. I did it for you this time. >> >> >> >> My point was that, like the OP, sometimes GnuCash does not present the >> correct, or any existing transaction to match an incoming transaction to >> during the import, so the only option left is to import as new. >> >> There is no option to create a match to an arbitrary existing transaction >> that GnuCash did not offer. >> >> >> >> This is a sticky wicket anyway, because there is always the possibilty of >> many very similar existing transactions to choose from in some cases. >> >> >> >> For OFX imports there is the extra possibility that the UUID may have been >> previously used or re-used inadvertantly, but I know I see a few cases >> where that is not the reason that there is no match offered. >> >> >> >> >> >> >> >> On Mon, Dec 18, 2023, 1:30 PM Kalpesh Patel <kalpesh.pa...@usa.net >> <mailto:kalpesh.pa...@usa.net><mailto:kalpesh.pa...@usa.net><mailto:kalpesh.pa...@usa.net> >> > wrote: >> >> In case you didn’t see the email, for " In those cases I just import the >> transaction unmatched, but It would be nice to have a way to force those >> matches." you'll need to set the transaction as either 'U+C' or 'C' and then >> double-clicking that transaction will bring up 'Select matching existing >> transaction' window where you can set the correct match. >> >> -----Original Message----- >> From: David Carlson <david.carlson....@gmail.com >> <mailto:david.carlson....@gmail.com> >> <mailto:david.carlson....@gmail.com> >> <mailto:david.carlson....@gmail.com> > >> Sent: Sunday, December 17, 2023 11:01 PM >> To: Gyle McCollam <gmccol...@live.com <mailto:gmccol...@live.com> >> <mailto:gmccol...@live.com> >> <mailto:gmccol...@live.com> > >> Cc: gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org> >> <mailto:gnucash-user@gnucash.org> >> <mailto:gnucash-user@gnucash.org> >> Subject: Re: [GNC] Import issue >> >> Gyle, >> >> I have sometimes had GnuCash fail to match transactions with equal amounts >> and dates. I do not know why but I suspect either there is insufficient >> matching text in the description or there is a different reason blocking the >> match. In those cases I just import the transaction unmatched, but It would >> be nice to have a way to force those matches. >> >> >> >> On Tue, Dec 12, 2023 at 5:51 PM Gyle McCollam <gmccol...@live.com >> <mailto:gmccol...@live.com><mailto:gmccol...@live.com><mailto:gmccol...@live.com> >> > wrote: >> >>> I'm importing a credit card statement and matching to transactions >>> already entered. I have a transaction recorded on 11/08/2023 that >>> was processed by the credit card company on 11/12/2023, 4 days later. >>> It is not matching with the entered transaction even though the >>> amount is identical. I've looked at the preferences for importing >>> and attached a screenshot. I don't know what I'm doing wrong. Is >>> there a way to select the item in the import screen and tell it to match to >>> the 11/08/2023 transaction? >>> >>> >>> Thank You, >>> >>> Gyle McCollam >>> >>> Gyle McCollam >>> >>> gmccol...@live.com <mailto:gmccol...@live.com> <mailto:gmccol...@live.com> >>> <mailto:gmccol...@live.com> >>> <mailto:gmccol...@gyleshomes.com<mailto:gmccol...@gyleshomes.com> > >>> email >>> _______________________________________________ >>> gnucash-user mailing list >>> gnucash-user@gnucash.org <mailto:gnucash-user@gnucash.org> >>> <mailto:gnucash-user@gnucash.org> >>> <mailto: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. >>> >> >> >> -- >> David Carlson >> >> >> >> _______________________________________________ >> gnucash-user mailing list >> gnucash-user@gnucash.org <mailto: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.
