Most reports should have a <pageNumberReset/> tag before </story>

Bug #546918 reported by Numérigraphe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo Addons (MOVED TO GITHUB)
New
Undecided
Unassigned
Nominated for 5.0 by Numérigraphe
Nominated for Trunk by Numérigraphe

Bug Description

In the current v5.0 branches, most reports don't have a <pageNumberReset/> tag before the </story>.
The results of this is that, if you use a corporate header with :
    <drawRightString x="19.7cm" y="28.3cm"><pageNumber/> / </drawRightString>
    <drawString x="19.8cm" y="28.3cm"><pageCount/></drawString>
and you print several orders (or packing lists, or invoices or mostly anything), then you get a report with a single "page 1", where you would naturally expect to have a "page 1" for each new document.
I think this should be fixed in the SXW and RML files for most reports where you expect several documents to be printed at once.
Lionel.

Revision history for this message
Numérigraphe (numerigraphe) wrote :

I'm subscribing you "Usability people" to this bug, so you can have your say if you want.
Lionel

Revision history for this message
Numérigraphe (numerigraphe) wrote :

By the way, I'm pretty sure we'll need bug #516966 fixed before we can do this right.
Lionel

summary: - Most reports should have a <pageCountReset/> tag before </story>
+ Most reports should have a <pageNumberReset/> tag before </story>
description: updated
Changed in openobject-addons:
milestone: none → 5.0.8
Revision history for this message
Numérigraphe (numerigraphe) wrote :

I'm marking this a duplicate of bug #516966 because the solution I proposed in comment #10 would solve this bug.

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.