If I ignore the result of get_conflict_list, then I get the matches that I want. That is where the desired transaction is disappearing from the list of possible matches.
Does anyone have any insight on why this function might be excluding transactions? On Sat, 2026-02-28 at 06:40 -0600, Jon Schewe wrote: > I'm trying to track down an issue where I am not presented with the > transactions that I expect for some checks matching. I have a > particularly difficult situation for GnuCash to match in that: > 1) the checks are always the same amount > 2) the checks are written a week apart > 3) the checks are cashed up to 2 weeks after written > 4) the back does not include the check number in the OFX file > > I understand that I can double click on the match dialog and choose > from all possible matches. However I'm finding that the match that I > desire isn't showing up in the list. > > I've added debugging to split_find_match to try and track it down. At > this point I'm finding the transaction that I desire being added to > the > list of possible transactions in this method. The method exits with 3 > transactions. However when the dialog is opened I only see 2 > transactions. I'm always missing the one that I want. > > I see the split_find_match is called from perform_matching and that > it > calls gnc_import_TransInfo_init_matches after all matches are found. > At this point I have the correct number of transactions in > match_list. > However I don't know the gnucash source or gtk well enough to be able > to figure out the steps between there and when the dialog that let's > me > pick transactions is built and displayed. > > Can someone help point me to the flow of execution between these 2 > points? > > Thank you, > Jon > > _______________________________________________ > gnucash-devel mailing list > [email protected] > https://lists.gnucash.org/mailman/listinfo/gnucash-devel _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
