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

[GNC-dev] Translators struggle with commit 2020bee

2019-03-06 Thread Frank H. Ellenberger
Hi Alex, while I did some translation I had Problems to understand the meaning of #: gnucash/gnome-utils/dialog-options.c:858 msgid "" "You have selected a placeholder account, which is shown so that child " "accounts are displayed, but is invalid. Please select another account. (You " "can

Re: [GNC-dev] GnuCash 3 on Linux

2019-03-06 Thread Frank H. Ellenberger
Adrien, I do not agree. While you are free in your choice for a private book, which is not used for tax preparation, all other cases are limited by governmental rules. If you then as a border crosser have books for different countries already the date and number formats differ for the same

Re: [GNC-dev] GnuCash 3 on Linux

2019-03-06 Thread Adrien Monteleone
I’ll hazard a quick guess that everything not in the accounts tab is non-book specific. At the very least, the display and general tabs are not. How you want figures to be displayed, which sets of figures, which periods... Content settings may be tied to the book, but formatting settings are

Re: [GNC-dev] GnuCash 3 on Linux

2019-03-06 Thread Derek Atkins
Hi, Coming at this late... Geert Janssens writes: > For starters the user preference is an all or nothing thing, either all > reports are in a book or in a common location. That's not very fine-grained. > Perhaps you consider some reports common and some reports book-specific. This > could

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