Bug 739571 - Matching imported transactions doesn't indicate previously matched entries
david.carlson.417 at gmail.com
Sun Jan 24 09:36:20 EST 2016
Re: Can you explain that a bit more? Under what circumstance would multiple
transactions at your bank would be reflected as a single one in your book?
When there are multiple accounts in the OFX file and there are transfers
between them, you get duplicates. In files from one of my banks this
happens regularly and I personally like to merge the split description
lines from both of them into the notes fields of the GnuCash book
transaction record because they reference the other account involved in the
On Sat, Jan 23, 2016 at 11:28 PM, John Ralls <jralls at ceridwen.us> wrote:
> > On Jan 23, 2016, at 4:56 PM, Tracy <tracy at arisiasoft.com> wrote:
> > On 1/23/2016 19:46, John Ralls wrote:
> >>> On Jan 23, 2016, at 2:37 PM, Jesse Olmer <jesse at wickedgoodtimes.com>
> >>> The second route (and the one I've already started on) is to have a
> >>> new object which ref counts pending matches (essentially, a map of
> >>> match info's to their ref count and some metadata for display). An
> >>> instance of this object lives in GNCImportMainMatcher and is passed to
> >>> the GNCImportMatchPicker providing fast lookup for each match. If this
> >>> doesn't pass the sniff test please let me know.
> >> Why not just add a gboolean "used" attribute to _matchinfo, set it true
> when the corresponding transaction is used in a match and exclude the
> instance from the match_list if its used attribute is true?
> > Or display an indicator showing that it has been previously matched (in
> case someone wants or needs to match two imported transactions to the same
> existing register transaction)….
> Can you explain that a bit more? Under what circumstance would multiple
> transactions at your bank would be reflected as a single one in your book?
> John Ralls
> gnucash-devel mailing list
> gnucash-devel at gnucash.org
More information about the gnucash-devel