The foundation for your business
Fork me on GitHub
[ledgersmb-users] Re: [ledgersmb-devel] Re: LedgerSMB 1.8.7 released
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[ledgersmb-users] Re: [ledgersmb-devel] Re: LedgerSMB 1.8.7 released

Hi István,

On Fri, Nov 20, 2020 at 2:27 PM Pongrácz István <..hidden..> wrote:
Hi Erik,

2020. 11. 19, csütörtök keltezéssel 23.08-kor Erik Huelsmann ezt írta:
Hi István,

On Thu, Nov 19, 2020 at 10:41 AM Pongrácz István <..hidden..> wrote:
2020. 11. 18, szerda keltezéssel 21.10-kor Erik Huelsmann ezt írta:

Changelog for 1.8.7

I got a time to check it, the Hungarian coa does not work,

Thanks for checking! What do you mean by "Hungarian coa does not work"? We've implemented checks to see that the coa does load without errors. Maybe it loads without errors (technically), but functionally doesn't make much sense?
To that extent, I'll note that this summer, I cleaned up all CoAs (including the Hungarian one) on "master"; the commit which cleaned up the Hungarian one is https://github.com/ledgersmb/LedgerSMB/commit/5d15e5861c03a3e4f19dfc7c0aa62e3ed2e5f847#diff-88e9cf6f7021d37f8f1b2b4b1e1ae41fb442e4de3a6db94aa78b28e895c838b4

Regarding to this, I will investigate, I got a lot of error in pgsql (duplicate ids adn whatever during the creation of a new company: complete.coa and extended), I suspect the menu. I will check it later.

Ok. I think that company creation always has been a rather "noisy" process in the database logs. I've only recently addressed that for the 1.9 release: all the warnings and errors that used to be thrown, are no longer. I don't really expect that the CoA is to blame, but rather the "old" 1.4 schema upgrade scripts which didn't run cleanly from 1.4 up to 1.8 (including). But please validate!

 I will check it to get it work as it would be move from my 1.3.45 to a more recent one :)

That's a nice step to upgrade. Let us know in case of issues, that allows us to further sharpen the upgrade procedure(s).

I'm afraid I will just stop using the old one and keep as an archive and start using a new one, no migration.

Obviously that works too and is an option as good as any. How do you plan to keep the old instance running? Do you have a VM that you'll start every now and then? Or do you plan to use different means?
Regarding taxes, I do not see the possibility to enter new taxes.
Only one line appears, like this:

Did I miss something?

I think you'll get an extra row when you enter a date into the "Valid To" field. (Not 100% sure, let me know what happens...)

Actually I did not get it :)
In Hungary it is possible to use several (3 + 1) different tax rates, depending on the product (some food, internet service, common products and EU/non EU exports as zero etc.).
So, I tried your method, but an other approach would be better.
Probably these tax rates are hard-wired in the coa during creating new company?
I prefer to be able to add/invalidate via the system settings, using the form shown above.
Anyway, how others handle this use case? I mean, adding a new tax rate.

Ah! Wait! I thought you wanted to add a new rate for the same tax! Now, I understand you want to add 3 more taxes. (Correct?)

If that's the case, that's relatively simple: Add a new account to your CoA and check the "tax" checkmark in the "Options" row of the account setup screen. After that, the account should appear in the taxes setup.





http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
users mailing list -- ..hidden..
To unsubscribe send an email to ..hidden..