MoneyWell 1.5.1 bug reports
Andrew
via web
Importing from QIF file
I've set up some Favorites and these seem to be correctly applied
to transactions imported from a QIF file in that they are amending
the Payee name as I have asked them to, however they are not
amending the Bucket name. Yet when I first set up each of these
Favorites, MoneyWell asked me if I wanted to apply the changes to
similar transactions and it did correctly apply both the new Payee
name and the Bucket. Note - the bank has pre-assigned generic
categories for their transactions, could this be interfering? This
is a complete deal breaker for me, I can't understand how I didn't
pick that up with the beta testing. Did something change?
Importing from QIF file
It would be really helpful if when I choose Import, MoneyWell would
remember the column width I last used in the Column view. Otherwise
I find I'm continually resizing the columns to be able to read the
contents.
Moving from Cash flow, Favorites, and Cash flow views
When I am in the Cash flow view and select a transaction then
right-click to make a new Favorite, then go to the Favorites view
to edit that Favorite, when I switch back to the Cash flow view,
some other transaction is always selected. It should retain the
selection I had previously made.
Favorites
Right-clicking Favorites doesn't provide a useful contextual menu -
e.g. to Delete an entry (and entries here should not be described
as transactions).
Favorites
It would be helpful to be able to widen the view of the Favorite
details panel on the right hand side of the screen so as to be able
to see the full text of the Aliases - for example, when creating an
alias from an imported bank statement entry, often the text is
quite lengthy and needs to be trimmed.
Preferences
What font size is being displayed in the Preferences dialog? The
antialiasing looks odd.
Licensing
I purchased the license directly from the No Thirst web site, then
downloaded the release version of the software, launched it, and
entered my serial number. It appeared to have registered correctly,
but kept displaying the "Get License" dialog but now with a blank
license code field. This was confusing. Perhaps instead it could
either display a dialog that confirms registration was done
correctly?
Thanks for your consideration.
Support Staff 2 Posted by Kevin Hoctor on 10 Mar, 2010 03:41 PM
Hi Andrew:
For the favorites, MoneyWell should be assigning a bucket if the favorite you set up has a bucket option checked and a bucket assignment on it. Use Transactions > Edit Ignored Alias List to make sure the generic payee names don't cause your transactions to use the wrong favorite. Typical generic aliases are CHECK, WITHDRAWAL, ATM WITHDRAWAL, etc.
Do you mean the delimited import? There are no columns on the QIF import panel for MoneyWell to remember the width or position. We are looking at enhancing the delimited panel to remember different setups.
I agree. There are technical reasons why this isn't happening now but I don't like it.
Future versions may allow the detail view to be adjusted in width. I recommend keeping the aliases as short as possible since they only need to match a partial string in the payee or memo during import.
This has been reported by others but I can't recreate it. We are working on a fix.
I agree. This was useful in early testing but has caused confusion for users and is being changed. Thanks.
3 Posted by Andrew Nielsen on 11 Mar, 2010 08:20 AM
(1) Importing from QIF file
> I've set up some Favorites and these seem to be correctly applied to transactions imported from a QIF file in that they are amending the Payee name as I have asked them to, however they are not amending the Bucket name. Yet when I first set up each of these Favorites, MoneyWell asked me if I wanted to apply the changes to similar transactions and it did correctly apply both the new Payee name and the Bucket. Note - the bank has pre-assigned generic categories for their transactions, could this be interfering? This is a complete deal breaker for me, I can't understand how I didn't pick that up with the beta testing. Did something change?
The favorites ALL have buckets selected and the bucket option ticked. NONE of the buckets are applied when importing from the QIF file but the Payee name is definitely being changed, so clearly the favorites are having _some_ effect. The buckets that the bank has pre-allocated to transactions have names like DEBIT, DEP, POS, PAYMENT etc, but they're just bucket names, not Payee names as you suggested might be the cause of the problem. I checked, the Ignored Alias list is empty. So it seems there's definitely some problem here.
(2) Importing from QIF file
> It would be really helpful if when I choose Import, MoneyWell would remember the column width I last used in the Column view. Otherwise I find I'm continually resizing the columns to be able to read the contents.
The columns I'm referring to are in the Import dialog itself - Mac OS X allows File Open dialogs to be displayed in icon, list or column view. I like column view. But it always defaults to showing really narrow columns which is really inconvenient.
(5) Favorites
> It would be helpful to be able to widen the view of the Favorite details panel on the right hand side of the screen so as to be able to see the full text of the Aliases - for example, when creating an alias from an imported bank statement entry, often the text is quite lengthy and needs to be trimmed.
Sure, I agree, they should generally be short text strings BUT when I'm creating a new favorite from an existing bank statement transaction, if the bank provided long text in the memo field then MoneyWell doesn't display it as nicely as it might and it makes it fiddly to edit.
(6) Preferences dialog
Screen shot shown below so you can see the strange anti-aliasing if you hadn't already seen it. It's only in the static text, not in the popup menus. And it does apply in General, Documents and Updates tabs.
Thanks for your help.
Support Staff 4 Posted by Kevin Hoctor on 14 Mar, 2010 08:59 PM
The blurry text in the Preferences panel has been resolved in the next build of MoneyWell 1.5.2.
Kevin Hoctor resolved this discussion on 14 Mar, 2010 08:59 PM.
Andrew Nielsen re-opened this discussion on 15 Mar, 2010 06:48 AM
5 Posted by Andrew Nielsen on 15 Mar, 2010 06:48 AM
Thanks. I note that 1.5.2 (493) doesn't yet resolve the problem of setting Buckets using Favorites on importing from a bank file, hoping that's resolved soon as I can't use MoneyWell yet, but looking forward to it.
Support Staff 6 Posted by Kevin Hoctor on 15 Mar, 2010 10:40 PM
Andrew: MoneyWell is assigning buckets if you have favorites set up with the bucket option active and the bucket assigned. Make sure that one of the aliases assigned to that favorite will match part of the payee or memo for the imported transaction.
Please let me know immediately if you don't see this working. My tests show it works well right now in all builds and releases.
7 Posted by Andrew Nielsen on 16 Mar, 2010 10:36 AM
Thanks for looking at it. I will endeavour to prepare some step-by-step details on how to reproduce this bug from a blank MoneyWell document and some test data for importing. As I indicated previously, the favorites all are obviously being applied because they are amending the Payee name, but they are not amending the bucket during the same import, even though the bucket option is explicitly set for each of the favorites.
Support Staff 8 Posted by Kevin Hoctor on 17 Mar, 2010 04:09 AM
Thanks Andrew. i really can't imagine how this isn't working for you. If you do have success in recreating this problem, please do post steps and/or your document here.
9 Posted by Andrew Nielsen on 17 Mar, 2010 08:37 AM
Created new MoneyWell file from scratch using default buckets; created one new savings account then imported the QIF file attached below; created three new favorites from the three transactions, setting the Payee and Bucket options on all of them (you can see the Favorites I created by opening the MoneyWell file attached below); deleted all the transactions in the file; reimported the QIF file and found that on import the Payee names had correctly been amended but the Buckets all still had the word "PAYMENT" instead of my selected bucket name.
I really hope you can see what I'm seeing. Attachments below.
Cheers, Andrew
Support Staff 10 Posted by Kevin Hoctor on 17 Mar, 2010 12:28 PM
Hi Andrew: Thank you for these documents, especially the QIF file. The problem is that the QIF file has a category set for each transaction. It's the line that starts with an 'L' and follows with "PAYMENT."
MoneyWell is designed to respect these categories that come from the QIF file. Typically, these are not set by banks and are only used when a QIF is exported from another application like Quicken.
Where are you getting this QIF from and do they offer a better format like OFX or QFX for download?
I'll look at the QIF import rules and see if I can override the category without breaking the imports that need it.
11 Posted by Andrew Nielsen on 18 Mar, 2010 04:55 AM
The QIF file comes from one of Australia's major banks. Downloads are available in other formats, I've experimented with a CSV file from that same bank and that works fine because MoneyWell provides me with control over the import process (which fields are used, and which are ignored).
I would appreciate you reconsidering the way it currently handles QIF imports because if a Favorite can make a change to the Payee during import but ignores changes to the Bucket on import then that's very inconsistent behaviour, so either informing the user that this is going to happen or allowing them to override it, or actually just applying the changes that are specified in the Favorites, would be preferable.
Thanks for your consideration.
12 Posted by Dan Noguerol on 20 Mar, 2010 04:22 PM
Hi all: I just noticed an irritating and confusing issue. I have View...Show Pending Transactions off. I then enter a new transaction with a date in the future. Everything seems ok. However, if I create another new transaction, the date appears to default to the future date I used for the previous one. This has the effect of making it appear that I'm modifying an existing transaction since the last visible transaction in the list is the one highlighted and appearing to be modified. Turning View...Show Pending Transactions on results in the correct behavior. This was never an issue before so I assume it's something new in 1.5.1.
Support Staff 13 Posted by Kevin Hoctor on 21 Mar, 2010 05:11 AM
Dan: This has been fixed in 1.5.2. Thanks for catching it.
Please start a new discussion for future issues. We don't want to miss anything in long discussions.
14 Posted by Daniel Noguerol on 21 Mar, 2010 06:48 PM
Thanks, Kevin.
Support Staff 15 Posted by Kevin Hoctor on 21 Mar, 2010 06:58 PM
MoneyWell 1.5.2 is out. Use Check for Updates… to get it.