Report Qweb Element Page Visibility

by ,
Odoo          
v 8.0 v 9.0 v 10.0 Third Party 1947
Download for 8.0 series
You bought this module and need support ? Click here !
Technical name report_qweb_element_page_visibility
LicenseAGPL-3
Websitehttps://odoo-community.org/
Repositoryhttps://github.com/OCA/reporting-engine.git#8.0
Read description for v 10.0 v 9.0
License: AGPL-3

Report Qweb Element Page Visibility

This module allows you to use 4 classes in QWEB reports:

  • not-first-page: shows element in every page but first
  • not-last-page: shows element in every page but last
  • first-page: shows element only on first page
  • last-page: shows element only on last page

Usage

To use this module, you need to:

In the QWEB ir.ui.views used by your report, you can add an element with css class with any of the classes described above. For example if you need to improve invoice report header with invoice's number in every page but first, and sale order report header with order's name in every page but last, add this code to external_layout_header:

<t t-if="o._table=='account_invoice'">
    <div class="not-first-page">
        <span t-esc="o.number"/>
    </div>
</t>
<t t-if="o._table=='sale_order'">
    <div class="not-last-page">
        <span t-esc="o.name"/>
    </div>
</t>
Try me on Runbot

Bug Tracker

Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us smashing it by providing a detailed and welcomed feedback here.

Credits

Contributors

Maintainer

Odoo Community Association

This module is maintained by the OCA.

OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.

To contribute to this module, please visit http://odoo-community.org.

Please log in to comment on this module

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author, please use the developer contact information. They can usually be found in the description.
Please choose a rating from 1 to 5 for this module.