Re: Three persistent issues with categorizing downloaded transactions

Hi Hans,
I'm not sure if the link I provided to the new preview works.  If not try this one:
http://help.infinitekind.com/discussions/md2010-beta/7-reconciling-transactions-bring-back-md2008-style-or-improve-the-md2010-style
It's a long post... the preview is in post 146 from Moneydance Support Staffer Ben Spencer on page 5.
HTH -Kevin N.
 
> From: [email protected]
> To: [email protected]
> Date: Sat, 30 Oct 2010 08:01:57 -0400
> Subject: Re: [moneydance] Three persistent issues with categorizing downloaded transactions
> 
> 
> Hi Hans,
> I think I follow you now. When MD 'thinks' it's offered up the proper 'match' to a txn, 
> it doesn't change that 'offer' to the user's manually edited one to make it the default
> choice. It DOES offer the user's edited txn as a possible 'match' but it's NOT offered 
> now as the default (highlighted) offer, which it should. That way the user could then 
> 'Accept' the 'offer' by just hitting 'Enter'. Instead, the user must still choose it 
> from the list of possible 'offers'. Is that it?
> If so, I can recreate this and I agree with you.
> There is a new matching process in the works. There is a preview of it posted here:
> http://s3.amazonaws.com/entp-tender-production/assets/fe945a529022a9d7deeaa2be3e80edc78ef244a2/Screenshot-devided.png?AWSAccessKeyId=1AJ9W2TX1B2Z7C2KYB82&Expires=1288440260&Signature=5YZSfJ04T3r5ohFiw%2Fk5bXVPGY8%3D
> Hopefully it will resolve this issue.
> -Kevin N.
> 
> 
> > From: hans-y8fhgmUD/[email protected]
> > Date: Fri, 29 Oct 2010 23:00:04 -0600
> > To: [email protected]
> > Subject: Re: [moneydance] Three persistent issues with categorizing downloaded transactions
> > 
> > I'm on 751.
> > 
> > Thanks for the tip about the preferences setting. It does just what I need. I can't believe I've been struggling with this for so long, and the solution was this close...
> > 
> > As for the second issue, the problem is not that manually edited transactions change back to the original. The problem is that if I manually edit a transaction, the categorization that the program proposes as the default is not the manually edited one. It keeps proposing some other transaction, but I feel that if I manually edit a transaction, I'm showing an implicit preference for whatever edits I've made myself. So after manually editing, the proposed match should be the line that's marked as the original transaction, not one of the other "categorize" lines.
> > 
> > On Oct 29, 2010, at 7:15 PM, Kevin Nugent wrote:
> > 
> > > 
> > > Hi Hans,
> > > What version of Moneydance are you using? I'm not sure about the tags 
> > > issue but you 2nd issue with manually edited txns changing back to the 
> > > original txn sounds like an issue from earlier builds that have since 
> > > been fixed. 
> > > The current build is 2010r3 (751)
> > > The third issue should be resolved by displaying the full account path.
> > > File > Preferences... > General tab > Show Full Account Paths.
> > > HTH -Kevin N
> > > 
> > >> From: hans-y8fhgmUD/[email protected]
> > >> Date: Fri, 29 Oct 2010 16:15:55 -0600
> > >> To: [email protected]
> > >> Subject: [moneydance] Three persistent issues with categorizing downloaded transactions
> > >> 
> > >> As the subject says, I'm still seeing three problems with the workflow for categorizing downloaded transactions. They greatly increase the time needed to categorize my transactions.
> > >> 
> > >> The first problem is that when categorizing, tags are not coming over. That is, if the proposed transaction has tags, then after accepting the proposal, the incoming transaction will not have any of the tags. This means I have to accept, then go and open the transaction for editing, add the tags, and commit my changes. This is a lot longer than just accepting, of course.
> > >> 
> > >> The second problem is that when I edit the original transaction, the transaction proposal does not change. I think it is more than reasonable that, if I manually edit a transaction, then the manually applied changes are the ones that I want, and the proposed transaction should switch to the original transaction.
> > >> 
> > >> The third problem is that the category field only displays the lowest-level category. I have separate accounts set up for each of my cars, and each has a subaccount for fuel. Obviously, each car get filled up sometimes at the same gas station. When these transactions come in, the proposed category will just say "fuel," without any hint as to what the higher-level categories are. This means I can choose to accept the categorization, but then I have to go back to the register, and open the transaction for editing to confirm that I have the right category applied. As far as the register is concerned, I have no problems with displaying just the lowest-level category. It's only in the categorization area at the bottom that I'm missing a view of the higher-level categories.
> > >> 
> > >> Regards,
> > >> 
> > >> Hans.
> > >> _______________________________________________
> > >> moneydance-info mailing list
> > >> [email protected]
> > >> http://moneydance.com/mailman/listinfo/moneydance-info
> > > 
> > > _______________________________________________
> > > moneydance-info mailing list
> > > [email protected]
> > > http://moneydance.com/mailman/listinfo/moneydance-info
> > 
> > _______________________________________________
> > moneydance-info mailing list
> > [email protected]
> > http://moneydance.com/mailman/listinfo/moneydance-info
> 
> _______________________________________________
> moneydance-info mailing list
> [email protected]
> http://moneydance.com/mailman/listinfo/moneydance-info