Thank you David.
Would it be correct for me to assume that *any* account type can be edited
prior to the addition of any data?
Either way, it sounds like this can be an iterative process to an extent. And
that most negative consequences can be reversed with a little creativity.
Tim
> On Feb
Just a reminder -- please quote just enough to give the context of your
reply.
It's easy to put a three-line comment at the top of a ten-screen article
and hit "send", but then everyone who receives it gets to scroll through
ten screens to find out whether there's anything new buried there.
And
Thank you David.
Would it be correct for me to assume that *any* account type can be edited
prior to the addition of any data?
Either way, it sounds like this can be an iterative process to an extent. And
that most negative consequences can be reversed with a little creativity.
Tim
> On Feb
Hi Simon,
I appreciate that perspective.
I have considered only only assigning only top level types, because if someone
is importing 25 or 30 accounts (INCOME/EXPENSES types should be much easier for
most users), going through and editing them isn’t that difficult.
But as I said earlier, the
FWIW, I have taken the perspective that if I don't know what
category/account to put something in, I don't guess, I put it in
"Unbalanced" and then ask someone who knows. As I understand it, there
shouldn't be anything in that category, so it's a big red flag that you
can't miss that this thing
Tim ,
In most cases if you get an account type wrong you can edit the account type and
its parent account from the account tree structure. There may be some
limitations associated with the type of the parent account which may have to be
worked around. In the worst case scenario you can create an
Thanks Jim for the reply.
> On Feb 20, 2023, at 15:49, Jim DeLaHunt wrote:
>
> It sounds like you are trying to answer two questions:
>
> 1. How do you extract meaning from account name strings in incoming migration
> data, such that you can pick the appropriate GnuCash account type?
Ummm,
On 2023-02-19 05:32, m...@tgr66.me wrote:
The approach I’m taking in a migration app I’m writing will be conservative,
erring on the side of more general vice more specific. For example, ASSET,
LIABILITY, INCOME, EXPENSE, EQUITY are pretty easy to accurately apply based on
account names (for
The approach I’m taking in a migration app I’m writing will be conservative,
erring on the side of more general vice more specific. For example, ASSET,
LIABILITY, INCOME, EXPENSE, EQUITY are pretty easy to accurately apply based on
account names (for example, “assets:current assets:cash”). In
