follow-up report / overdue payments : "maturity" amount isn't computed

[Francois Pietquin (OpenERP)]

- open a partner form view.
- print the report "overdue payments".

=> the pdf contains a mistake : the formula to compute the "maturity" amount is broken. (In place of the amount, I got : [[formatLang(reduce(lambda x,y: x+(y['debit'] - y['credit']), filter(lambda x: x['date_maturity'] < time.strftime('%Y-%m-%d'), getLines(o)), 0)) ]] [[company.currency_id.name]] ).

[Ajay Patel (OpenERP) (ajay-openerp)]

Hello francois

I have checked with the latest revisions of server,client and addons (trunk).
It is ok.
So please kindly update your revisions.
Still if you get same problem than re-open the bug.

thanks
apa(OpenERP)

[Jay Vora (Serpent Consulting Services) (jayvora)]

@ Francois,

Please describe the problem with the version of OpenERP. APA(OpenERP) has checked in trunk.
Illustrate the circumstance where you meet the error.

Thanks.

[Francois Pietquin (OpenERP) (fpi-openerp)]

You right.
Sorry I forgot it!

Jay (OpenERP) wrote:
> @ Francois,
>
> Please describe the problem with the version of OpenERP. APA(OpenERP) has checked in trunk.
> Illustrate the circumstance where you meet the error.
>
> Thanks.
>
>

[Francois Pietquin (OpenERP) (fpi-openerp)]

Sorry I forgot to say I'm using 5.0.14
Thanks.

[Francois Pietquin (OpenERP) (fpi-openerp)]

Create a simple invoice and then open the report from the appropriate partner form... you'll see the problem!
Contact me for any questions.

Many thanks.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Francois,

I tried with latest code on 5.0.14, but I could not see the error.

It possible for you to give me access rights to connect your DB? Or can you attach the one?

Thanks.

[Jay Vora (Serpent Consulting Services) (jayvora)]

Francois,

Can you share the DB or the actual scenario?

Thanks.

[Nick White (r-launchpad-njw-me-uk)]

I can confirm this. It occurs with a fresh install of the AllInOne 5.0.14 pack on Windows, with the sale module and its dependants installed, and the demo db. It also occurs on a colleague's Linux install 5.0.14 of, though that one is rather more customised.

Looking into it, I found that for some reason the filter() call causes an error. The RML reporting helpfully gives no traceback or any error reporting at all. However, in testing I found that even something along the lines of filter(lambda x: True, (1,2,3)) caused a failure.

So I rewrote the code to not need filter. It works exactly the same. It is a little ugly, but so was the previous code, due to the fun on constraining python code to one line. I'll attach it here.