Re: [GNC-dev] Transactions vs Splits

2019-03-11 Thread Wm via gnucash-devel
On 05/03/2019 12:57, David Cousens wrote: I will get to testing the import of these transactions either tomorrow morning or Thursday. I don't know yet whether it is possible to import them in the multiline format with 2 or more splits yet. Yes, it is possible but you have to be very careful

Re: [GNC-dev] Transactions vs Splits

2019-03-07 Thread cicko
David, that's a very elaborate explanation. I'm sure there will be enough information once you are through with testing. So far our findings match. One thing I'd like to note, David Cousens wrote > Date,Transaction ID,Number,Description,Notes,Commodity/Currency,Void > Reason,Action,Memo,Full

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread David Cousens
Alen, The multicurrency transactions are a problem because at the moment GnuCash is introducing a spurious unrelated amount into the transaction. For eg I had a simple $100 AUD debit to an AUD Savings Account with a split to a Savings USD account for $110 USD. This is correctly exported but when

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread cicko
cicko wrote > However, if the price is taken into account, then perhaps the Price field > may have some role there? Hm, the Price column definitely affects the destination amount but not in a way I can understand. Using 111,2019-03-06,,,15,"HSBC savings",,0 111,2019-03-06,,9.8788,,"cash, EUR",,2

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread cicko
cicko wrote > If this works as expected, then multi-currency transfers should not be an > issue at all. Each split would specify the amount so no need for GnuCash > to > fiddle with prices. This works great for single-currency transactions. Everything fits, as specified in CSV records. There

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread cicko
OK, now I see that I'll need to use the Multi-split option always, to cover for the eventual real multi-split in the source. So, I'll be focusing on that option. The good news is, when multi-split is selected, the Transaction ID field becomes available for mapping. That helps a lot as the matcher

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread David Cousens
Hi Alen, >I see that, with Multi-split checked, I can no longer select the Transfer >Account destination field. This is a dead end for my current approach, using >Transfer Account. With a multisplit multiline record there should be no need. GnuCash should interpret the following lines as

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread cicko
This helps: -- Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html ___ gnucash-devel mailing list gnucash-devel@gnucash.org

Re: [GNC-dev] Transactions vs Splits

2019-03-06 Thread cicko
Thanks a lot, David. I have completely missed that checkbox. Will try it out. Also, to comment on your reference to single- vs multi-split import. I saw the Transfer Account field available and decided to use it from the start. That way I don't need two splits for simple transactions, meaning

Re: [GNC-dev] Transactions vs Splits

2019-03-05 Thread David Cousens
Alen When you are importing a multiline exported transaction you should see a multiline checkbox at the bottom of the first window. You may get multiline import to work if you select this as it tells GnuCash to look for following lines which are part of a single transaction. David - David

Re: [GNC-dev] Transactions vs Splits

2019-03-05 Thread David Cousens
Alen, Each exported transaction occupies at least 2 or more lines, one for each split in the transaction. The following is an exported multiline format single transaction for a credit of $100 to the Savings account with splits which debit the Checking account by $50 and the cash in Wallet

[GNC-dev] Transactions vs Splits

2019-03-05 Thread cicko
What is meant by "multiline" in this case? I've tried importing a CSV file with multiple records and it seems to be going fine. However, I'd like to keep the split structure in place but am not sure if that is possible. Currently I create rows for each split in a transaction and so it makes sense