For instance, let the "export.csv" file with the following contents:
*********************************************************************
Transaction Date,Account ID,Description,Amount
"04/01/2010",91,"Selling Bonus","1050.75"
"04/02/2010",22,"Savana Grill","-30.25"
"04/02/2010",,"Tip","-5.00"
"04/03/2010",41,"Oil Change","-65.00"
Summary = Count: 4, Sum: 950.50
*********************************************************************
I tried to create a new reader by extending *TransactionReader* and
using the methods setAcctToAcctID(), setAcctToKey(), and
setAcctToType(), according to [1]. However, none of them worked: the
default account category was used instead.
Do you have any other ideas on how to solve this?
Thanks in advance.
Best regards,
Rodrigo Hjort
Reference:
[1] http://moneydance.com/dev/apidoc/
Any way. From my knowledge, the reason is that my plug-in tries to
simulate downloading transactions, and then integrate with the exising
downloaded transaction workflow. Which means that 'some' information
is downloaded from the bank, stored in the 'unaccepted or new' list,
and then user has to go through each one one by one and fill in
unknown data and then accept them.
During this 'filling in' part Moneydance attempts to guess the
category for the new transaction, which interferes with what you are
attempting to do.
Basically you are seeing the difference between a OnlineTxn and
SplitTxn.
If you known all the transaction information, you can do what you want
by creating an importer plugin, which actually creates real
transactions (ones that user does not have to manually accept).
However this is not appropriate for most CSV formats as they are
rather primitive for most banks. Also, I am very wary of messing with
peoples real financial numbers without them being to approve each real
change.
Regards,
Miki.