> My bank transactions display without the single transaction that was > never have seen the data that caused me problems.
#Gnucash import bank transactions Pc#
> caused my problems - assuming that however FITIDs are saved this PC would > I did this on a second PC that had never imported the bad qfx file that > Regarding my comment 25, I restored my mysql database from backups and I (In reply to Gerry Matte from comment #31) If coming from 2.6 your old import maps are no longer recognized, can I ask you to file this as a separate bug ? It would become too confusing to treat that one here as well. Gnucash 2.6 and 3.0 treat the previous match data (more formally referred to as "import maps") slightly differently.
If so that would also be a bug, but another one. However if I understand correctly you are seeing the transactions but gnucash doesn't reuse previous match data to automatically recognize them ? Wes, this got a bit sidetracked because we were still struggling to get the transaction matcher to show transactions in the first place. > matching showed up - I wasn't paying enough attention to know if it was the What was weird was that the 2nd time I imported, much more of the > the dll provided by you, the imports came in (YAY!) but none of the matching I used whatever tools are GnuCash out-of-the-box. > My user experience was the bulk of my OFX imported tranx came in with Consider me taken care of - it seems like matching is working "good enough". I am totally up for calling this user-error and marching on but if you guys are running down any kind of bug, I know this type of feedback can sometimes be helpful.
#Gnucash import bank transactions software#
I run a help desk for a software company. What was weird was that the 2nd time I imported, much more of the matching showed up - I wasn't paying enough attention to know if it was the matches that were part of the first. After installing the dll provided by you, the imports came in (YAY!) but none of the matching came in. My user experience was the bulk of my OFX imported tranx came in with matching. > If non Bayesian it's easier as the whole description is in the 'matchīob - apologies in advance - I'm just a user with enough development experience to be dangerous. > these entries to equate to a successful mapping. > point to the required mapped to account. > description and day of transaction in 'match string' column which should all > If Bayesian, find source account in list and look for parts of transaction
> Open tools/'import map editor', may take a short while depending how many > What backend are you using, xml / sqlite ? > Are you using Bayesian matching, preferences/'On line Banking' Are saying the transactions show up unbalanced ?
0 kommentar(er)
