On Mar 9, 6:58 am, Kevin Hoctor <[email protected]> wrote:
> I have thought of adding this but there are very few scenarios where
> I've wanted to so it became a low priority change. Why don't you want
> to change most of the transactions? Are you not wanting the Payee name
> updated or is it a bucket assignment change that concerns you?
Well, your "few scenarios" is every single time I import a QIF from my
bank. The QIF data on a transaction provided is always unassigned and
my payees are always "WITHDRAW". So every time I import, I have to go
through all the records and uncheck them because only 2-3 of 50 are
similar transactions.
Every month, lather, rinse, repeat. I might have to buy a new mouse
soon; the button's all worn down. ;)
In my opinion, the solution could be:
1. a select/deselect all checkbox
2. less aggressive transaction memorization, like making memorization
less automatic, and make sure *lots* of columns match (rather than any
old txt string in any column) before offering to change them. for
example, I manually labeled my first amazon.com transaction a "gift."
now everything from amazon is a "gift" and it took some work to
straighten this out.
3. more control over the Update Similar process- like filters in the
sheet itself, so I can easily group things I know are similar, and not
trust a ham-fisted string match.
I'm not being overly negative. I really like the app, but there are
some assumptions it makes about clean and regular data input which
just doesn't exist (as I've seen when I have to rely on someone else's
heterogeneous data output).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "No
Thirst Software User Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/no-thirst-software?hl=en
-~----------~----~----~----~------~----~------~--~---
