Hi Michael,
Not at my keyboard right now, will get more elaborate when I am. However,
you can get your old (last year) report layout by selecting the 'account
category' layout instead of 'account hierarchy'. The selector between one
or the other is on the report settings page for both the pnl and
This is what my tree looks like.
My income report looks better, but doesn't look like what it used to look like.
sswbooks=# select * from account_heading_tree;
id | accno |description| level |path
---+---+---+---+-
sswbooks=# select id,accno,description,category from chart where category IS
NULL;
id | accno |description| category
---+---+---+--
10006 | 1500 | INVENTORY ASSETS |
10015 | 2000 | CURRENT LIABILITIE
I've discovered that some of my "Expense" header accounts have become marked
"Asset", and changing them back to Expense results in:
Please select a valid heading at LedgerSMB/Scripts/account.pm line 92.
My income accounts seem to still be income accounts.
Heading in psql now...
--
]
Erik Huelsmann wrote:
> Hi Michael,
Thanks for the reply.
I had struggled through with data from CoA report and a spreadsheet,
and the result was a mess which the tax authority rejected.
I now have time to "fix" it...
I don't really get why it is messed up, I did my 2014 report with 1.4 las
On Sat, Jun 25, 2016 at 2:00 AM, Michael Richardson
wrote:
> Trying to clear up these unposted drafts, I found that some could be
> deleted
> without hassle (if I do them one at a time).
> Others, I thought I could post and then reverse.
>
> I get this after copy-to-new on the Add Transaction,
For some time I've been using the "permalink" button as way to reload/redo a
query. After a few uses (somewhere between 2 and 4), it will fail and put up
an HTTP Auth box. All windows/tabs are now screwed and I have to login again
from scratch.
I caught this in the logs today:
==> /var/log/apach
Trying to clear up these unposted drafts, I found that some could be deleted
without hassle (if I do them one at a time).
Others, I thought I could post and then reverse.
I get this after copy-to-new on the Add Transaction, and inserting - signs
everywhere:
==> /var/log/apache2/error.log <==
DBD:
Hi Michael,
On Wed, Jun 22, 2016 at 3:21 PM, Michael Richardson
wrote:
> Erik Huelsmann wrote:
> > Thanks for your report! Based on it, I can conclude that apparently
> > nobody has been using check printing in 1.4... because the
> "project_id"
> > column has been removed when maki
Erik Huelsmann wrote:
> Thanks for your report! Based on it, I can conclude that apparently
> nobody has been using check printing in 1.4... because the "project_id"
> column has been removed when making the step from 1.3 to 1.4.
More problems with 1.4.28:
http://www.sandelman.ca/tm
On Wed, May 4, 2016 at 10:17 AM, Chris Travers
wrote:
> I think filling it in with null in 1.4 is a good idea, as is removing it
> in 1.5
>
On review, this problem doesn't exist in 1.5. So, it's a 1.4-only fix which
I'll treat as such.
Thanks for the quick response!
Regards,
--
Bye,
Erik.
Hi Michael,
1.4.29 will have a fix for this. If you want to patch your local install in
order to be able to proceed your upgrade / accounting, this is the fix you
can apply. It won't interfere with a regular 1.4.29 upgrade:
https://github.com/ledgersmb/LedgerSMB/pull/1489/commits/8d28270f04c7cb8b9
I think filling it in with null in 1.4 is a good idea, as is removing it in
1.5
On Wed, May 4, 2016 at 10:14 AM, Erik Huelsmann wrote:
> Hi Michael,
>
> Thanks for your report! Based on it, I can conclude that apparently nobody
> has been using check printing in 1.4... because the "project_id" c
Hi Michael,
Thanks for your report! Based on it, I can conclude that apparently nobody
has been using check printing in 1.4... because the "project_id" column has
been removed when making the step from 1.3 to 1.4.
@Chris, I've searched for the use of the project_id column in:
LedgerSMB::Scripts::
with both 1.4.27 and 1.4.28, having run setup.pl to upgrade each time, I
get the following when attempting to pay (post+print PDF/screen) a payment to
an open invoice.
Does not happen with just POST.
I can't recall last time I successfully printed a checque in 1.4: I know I
have been writing them
15 matches
Mail list logo
