report_qweb_field_option

Report Qweb Field Option

This module allows administrators to define the decimal precision of float fields and add option values to fields (e.g., adding a date widget option to datetime fields) for QWeb report and view presentation.

Table of contents

• Configuration
• Usage
• Known issues / Roadmap
• Bug Tracker
• Credits
  • Authors
  • Contributors
  • Maintainers

Configuration

Go to Settings > Technical > Reporting > Qweb Field Options, and create records according to your needs.

For each record:

• Set Model and Field (required)
• Set UoM and UoM Field, or Currency and Currency Field only for fields of float type (optional)
• Set Domain to specify a domain for more specific filtering (e.g., [('secondary_uom_id', '=', 1)] to apply only when a specific secondary UoM is used) (optional)
• Set Company (optional)
• Set Options as a string representation of a dictionary. E.g., {"widget": "date"}, {"widget": "monetary"}, or {"widget": "contact", "fields": ["name", "phone"]}
• Set Digits (only for float-type fields). The value is ignored if Options is set

Usage

Print a QWeb report (quotation, invoice, purchase order, etc.), and the value presentation for fields like line quantity, price unit and date order are adjusted according to the Qweb Field Options configuration.

Note that among matching configuration records, the one with the strictest condition will be applied.

Known issues / Roadmap

#. QWeb field option settings only apply to fields rendered with t-field.

They don’t work with t-esc or other expressions not using t-field.

As a workaround, you could create a module that adds a computed field holding the same value currently computed and displayed in the QWeb report using t-esc, and adjust the report template to display the field value using t-field. This would allow you to adjust the decimal precision as needed.

#. Assigning Options in a QWeb Field Options record can cause UI issues if a field is defined twice with different widgets in a view.

For example, adding {"widget": "date"} to the date_approve field in a purchase order can result in two dates appearing under the Confirmation Date column in the portal view. This occurs because the field is defined twice with different widgets.

Reference: https://github.com/odoo/odoo/blob/5eec379/addons/purchase/views/portal_templates.xml#L101-L102

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 to smash it by providing a detailed and welcomed feedback.

Do not contact contributors directly about support or help with technical issues.

Credits

Authors

• Quartile

Contributors

• Quartile:
  • Yoshi Tashiro
  • Aung Ko Ko Lin

Maintainers

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.

This module is part of the OCA/reporting-engine project on GitHub.

You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.