GoogleCodeExporter
commented
8 years ago Is the CSV Importer extension an active project still?Original comment by kmnugent...@gmail.com on 17 Dec 2012 at 12:25
Closed GoogleCodeExporter closed 8 years ago
GoogleCodeExporter
commented
8 years ago Is the CSV Importer extension an active project still?Original comment by kmnugent...@gmail.com on 17 Dec 2012 at 12:25
GoogleCodeExporter
commented
8 years ago Hi. I was not getting emails for issues. Maybe someone took me off them.
As for your accountName issue; you are not using it like I expected it to be
used, and I see it did more than I expected with what you gave it.
For one, why would you expected the Importer to enter the 'account name' data
into the 'Category' field? Aren't those 2 different things? :-)
I know Accounts and Categories are kind of different but kind of the same in
MD, but just going by the name I would not expect that to work. Just because
your 'label' says 'Category' means nothing because you told it to put it into
an 'account name'.
I do not remember the nuanced difference between the two but how I expected it
to be used was from a user request to be able to import txns into multiple
accounts not categories. I took those to be top level 'accounts' only, so if
you had say a Scottrade download that had maybe different stock names or
something, that would work. 'account name' Overrides the 'Import to Account'
selection, not the Category like you were thinking.
Original comment by stashu....@gmail.com on 23 Jan 2013 at 6:26
Attachments:
GoogleCodeExporter
commented
8 years ago did not get an email for my message. just trying to trigger one.Original comment by stashu....@gmail.com on 23 Jan 2013 at 6:29
GoogleCodeExporter
commented
8 years ago Hi Stan,
Thank you for your reply and explanation of the intended use of the 'Account'
field selector.
If you have a minute to look at the Text File Importer extension used in MD, it
behaves in the manner that I had expressed in my report. I was curious that
the
CSV importer did not treat the 'Account' field in the same manner.
BTW, I received only one email so far. It was this morning. It was your reply
to issue #22. I had voted to receive email notification of changes of that
issue.
I did not however receive an email indicating that you had replied to my issue
# 21
I'll keep checking back at the Google site now that I know it is still active.
Thanks again,
-Kevin N.Original comment by kmnugent...@gmail.com on 23 Jan 2013 at 2:15
GoogleCodeExporter
commented
8 years ago Hi. Here's a question though. I think I thought of letting people have an input
field called 'category', but decided not to because who would take the time to
fill all those out in a csv file? Why not just do it in MD? So I thought it not
worth doing.
Now, Discover card and maybe others assign their own categories to txn's that
can be downloaded, so maybe you could mass change them in your downloaded file
before importing them into MD, but again, you could just do that with the 'Find
and Replace' extension after importing. Any other thoughts on that, let me know.Original comment by stashu....@gmail.com on 29 Jan 2013 at 11:08
GoogleCodeExporter
commented
8 years ago Hi Stan,
I was recently helping a Moneydance user on the IK Help forums who was trying
to import his data through a .csv generated at Mint.com. His main concern was
retaining the Categories associated with his txns.
Mint.com generates their .csv with the 'Amounts' formatted as a single column.
With that in mind, as well as the ability to import Categories, I recommended
that
he use the Text File Importer.
It's my understanding that the use of .csv's is still quite prevalent outside
the U.S.
I can't help but feel that adding a 'Category' field would be a welcome
addition by the many people who are forced to use the .csv format. Provided
it's not terribly
difficult to include.
Thank you again for your work on this extension.
-Kevin N.
Original comment by kmnugent...@gmail.com on 30 Jan 2013 at 12:33
GoogleCodeExporter
commented
8 years ago Hi Stan,
Using my test.csv with a workaround, the importer successfully imports to an
Account including Categories.
The workaround assumes that:
A) The .csv file is formatted with separate Deposit and Payment columns.
B) The user's Moneydance data file contains a blank named Expense Category.
Performing the import will result in txns importing to individual Category
accounts.
Each txn in the Category's register will have the blank Expense Category as its
chosen Category.
Hence, all txns will also be entered into the blank Expense Category's account.
Use Batch Change > Account to move the txns from the blank Expense Category's
account to the intended import
Account.
In spite of this work around, I still feel that a 'category' field would prove
useful and should be made
available as an option in the Custom Reader.
-Kevin N.
Original comment by kmnugent...@gmail.com on 17 Feb 2013 at 5:55
Attachments:
GoogleCodeExporter
commented
8 years ago 
Hi. I do not understand: B) The user's Moneydance data file contains a blank
named Expense Category.
1.) do you mean you created a blank 'account' named "Expense Category"?
2.) what do you mean by 'blank'? empty as in no txn's or what?
Can you please send screen shots of the txn's after your first import so I can
see what is going on?
do you really need this blank 'account' named "Expense Category"?
I will look at creating a 'category' field to import.
I will look at creating a single amount field to import also. Does this just
make it a payment if it is positive and a deposit if the amount is negative or
that type of thing?
Original comment by stashu....@gmail.com on 17 Feb 2013 at 6:45
GoogleCodeExporter
commented
8 years ago Hi Stan,
The blank Expense account is an Expense account with no name.
The blank account might actually be created by the import.
The txns pool together in the blank account due to the individual txns in each
Category account having the blank expense account as their designated Category.
I've attached screenshots of the initial import, the txns residing in the blank
expense account and of one of the Category accounts.
Original comment by kmnugent...@gmail.com on 17 Feb 2013 at 7:20
GoogleCodeExporter
commented
8 years ago Sorry about that I answered the capcha before attaching the screenshots.
I've included a screenshot of the checking account after the batch change from
the
blank expense account.Original comment by kmnugent...@gmail.com on 17 Feb 2013 at 7:27
Attachments:
GoogleCodeExporter
commented
8 years ago 
Hi Stan,
One caveat of my workaround is that the txns in the Checking account are
treated as
'The Other Side' of the original txns.
This may or may not produce unsuspected results in certain reports.
-Kevin N.Original comment by kmnugent...@gmail.com on 17 Feb 2013 at 7:57
GoogleCodeExporter
commented
8 years ago Hi. Here is an alpha test file. I just added a category_name option and tested
a file and it seemed to work but I did not do any further testing. If you want
to test it on a TEST MD file and it wets your appetite, let me know. Just a
couple of test so DO NOT use it on a real MD file.Original comment by stashu....@gmail.com on 4 Jul 2013 at 6:48
Attachments:
GoogleCodeExporter
commented
8 years ago Hi Stan,
Thank you for your work on this.
Here are my findings so far when working in the following environment:
Starting Moneydance 2012.5 (866) at Thu Jul 04 17:16:04 EDT 2013
Settings Folder: C:\Users\Kevin_2\.moneydance
OS: Windows 7 6.1 x86
Java: 1.7.0_07 (Oracle Corporation)
Is in sandbox: false; restricted file access: false
name and version =CSV Importer *** Alpha 15.7.11 ***=
opening last file: Practice
Using the attached 'Issue-21.txt file, I was able to successfully import txns
with
Category names but only when 'Regular' was the selected option for 'Import
Transaction as:'.
When selecting 'Online' as the 'Import Transactions as:' option, the Category
names
would be assigned whatever the default category was for that account in
Moneydance.
Payments and Deposits are reversed between the 'Regular' and 'Online' settings.
This however is easily remedied by creating separate custom file readers. Not an
issue as far as I'm concerned.
Thanks again.
HTH -Kevin N.Original comment by kmnugent...@gmail.com on 4 Jul 2013 at 9:41
Attachments:
GoogleCodeExporter
commented
8 years ago Sorry. Glad you thought about using the non online settings. I forgot to
mention you need to do that.
I will see why it reverses when I can.
So you think account and transaction wise this works correctly?
On Jul 4, 2013 5:41 PM, <mdcsvimporter@googlecode.com> wrote:Original comment by stashu....@gmail.com on 4 Jul 2013 at 9:46
GoogleCodeExporter
commented
8 years ago Hi Stan,
Yes, in that Windows environment, I think it worked correctly.
I'm not a Mac user so I can not speak to those environments.
This should prove a vast improvement for those wishing to import csv files that
contain categories.
Thank you again.
-Kevin N.
Original comment by kmnugent...@gmail.com on 4 Jul 2013 at 9:53
GoogleCodeExporter
commented
8 years ago Hi Stan,
Playing around with this on another machine using MD 2011r2 (808).
I imported Issue-21.txt using 'Regular' as the 'Import Transactions as:' option.
The txns imported as expected but when selecting a 'blue dot' transaction, the
Confirmation side bar is not invoked.
(see screenshot Issue_21_Csidebar.jpg)
When more than one 'blue dot' txn is selected, the Confirmation bar IS invoked.
(see screenshot Issue_21_Csidebar_1.jpg)
I've attached the console window output after selecting a single 'blue dot' txn.
(Console_MD2011.txt)
I'm posting this only for informational purposes. I would not expect you to
devote
any time to making the CSV Importer work on older versions of Moneydance.
HTH -Kevin N.
Original comment by kmnugent...@gmail.com on 4 Jul 2013 at 10:23
Attachments:
GoogleCodeExporter
commented
8 years ago 
new version 15.7.11
Adds: Can import Categories, added try to find Mac Prefs in more places - has
all latestOriginal comment by stashu....@gmail.com on 12 Jul 2013 at 5:40
GoogleCodeExporter
commented
8 years ago Hi Stan,
Again, thank you for your work on this.
Should I create a separate issue ticket regarding the reversal of -Payment- and
-Deposit- columns when selecting 'Regular' vs. 'Online' as the 'Import
Transaction as' option?
-Kevin N.
Original comment by kmnugent...@gmail.com on 12 Jul 2013 at 12:30
GoogleCodeExporter
commented
8 years ago Oops. I think you mentioned that, and i forgot. Yes, I guess we can close
this one if it works for all the transactions and the opposite side of the
transaction properly. Then open an issue about the reversal.
StanOriginal comment by stashu....@gmail.com on 12 Jul 2013 at 12:56
GoogleCodeExporter
commented
8 years ago Hi Stan,
It's interesting that you mention the 'Other Side' of the transaction.
Before we close this issue, I noticed that the 'Other Side' of the transaction
is
given a 'blue dot' designation which requires confirmation from the
Confirmation side bar.
I don't know whether or not this would cause issues, but it is not the expected
behavior.
Confirming the original transaction does not remove the 'blue dot' designation
of
the 'Other Side' of the transaction.
-Kevin N.Original comment by kmnugent...@gmail.com on 12 Jul 2013 at 1:31
GoogleCodeExporter
commented
8 years ago The developer api I have found to be out of date which is a pain when you try
to call a method and it does not work or does not exist. I know there are a
couple of things I wanted to do differently but could not figure it out. The
api is basically a method/fuction list. I have to do a lot of guessing by the
names to see what I can get to do what I want it do it. I don't work there so
it's not easy :-)Original comment by stashu....@gmail.com on 13 Jul 2013 at 4:04
GoogleCodeExporter
commented
8 years ago Hi Stan,
Have you tried posting to the Moneydance Extension Development forum?
http://help.infinitekind.com/discussions/moneydance-development
Maybe Sean or one of the other developers can point you in the right direction.
-Kevin N.Original comment by kmnugent...@gmail.com on 13 Jul 2013 at 6:20
Original issue reported on code.google.com by
kmnugent...@gmail.comon 16 Oct 2012 at 4:52Attachments: