Regression in printing multiple records (5.0)

Bug #597170 reported by Dukai Gábor
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Odoo Server (MOVED TO GITHUB)
Fix Released
Undecided
Unassigned

Bug Description

Hi!
5.0 latest bzr.
The commit <email address hidden> caused a regression in printing multiple records in some cases. The first record is printed multiple times instead of printing all records.

Test case: select at least two outgoing picking records and create a report. Only the first picking selected will appear in the pdf.

Related branches

Changed in openobject-server:
status: New → Confirmed
Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hi Dukai,

I dont see that commit as the root of the problem.

Can you retry please? Till then, I am trying to find more.

Thanks.

Revision history for this message
Dukai Gábor (gdukai) wrote :

I've checked it:
  -with that commit: the first picking record printed multiple times.
  -without that commit: all the picking records are printed properly

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hello Dukai,

It seems, that commit needs to be reverted.
I am investigating more why was that code written, but I could not find the reason!

Revision history for this message
Dukai Gábor (gdukai) wrote :

I'll try to ask him.

Revision history for this message
Jay Vora (Serpent Consulting Services) (jayvora) wrote :

Hi Dukai,

Thanks for the response.
Infact, it has to be reverted as the commit breaks a very important functionality, we will traceout the root for the commit and will clean it asap.

Reverted by revision 2073 <email address hidden>,so it doesn't give birth to anything crucial.

Thanks for your concern.

Changed in openobject-server:
milestone: none → 5.0.12
status: Confirmed → Fix Released
Revision history for this message
Stephane Wirtel (OpenERP) (stephane-openerp) wrote :

Jay,

Please, Could you discuss with Christophe and Quentin about this patch. Because this patch fixes an issue.

May be, there is an other bug with this bugfix in the report engine.

Regards

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.