This release is a pre-release and may not be stable for production use.
This module was written to extend the functionality of the reporting engine to support XML reports and allow modules to generate them by code or by QWeb templates.
Table of contents
Installation
To install this module, you need to:
Install lxml in Odoo’s $PYTHONPATH.
Install the repository reporting-engine.
But this module does nothing for the end user by itself, so if you have it installed it’s probably because there is another module that depends on it.
Usage
This module is intended as a base engine for other modules to use it, so no direct result if you are a user.
If you are a developer
To learn from an example, just check the sample module.
To develop with this module, you need to:
Create a module.
Make it depend on this one.
Follow instructions to create reports having in mind that the report_type field in your ir.actions.report.xml record must be qweb-xml.
In case you want to create a custom report, the instructions remain the same as for HTML reports, and the method that you must override is also called _get_report_values, even when this time you are creating a XML report.
You can make your custom report inherit report_xml.xsd_checked_report, name it like your XML <template> id prepended by report., add a xsd() method that returns a XSD in a string, and have XSD automatic checking for free.
You can visit http://<server-address>/report/xml/<module.report_name>/<ids> to see your XML report online as a web page.
For further information, please visit:
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
Contributors
Enric Tobella <etobella@creublanca.es>
-
Jairo Llopis
Other credits
Icon taken from http://commons.wikimedia.org/wiki/File:Text-xml.svg
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.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-report-xml 12.0.1.0.0.99.dev9
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_report_xml-12.0.1.0.0.99.dev9-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_report_xml-12.0.1.0.0.99.dev9-py3-none-any.whl |
Release files / odoo12_addon_report_xml-12.0.1.0.0.99.dev9-py3-none-any.whl
| Download URL | odoo12_addon_report_xml-12.0.1.0.0.99.dev9-py3-none-any.whl |
|---|---|
| Size | 98.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7915c8a25d867a7a7543b9a856733a5b1fed6df783687cae02b3772859cb0bc6
|
|
BLAKE2b-256 checksum How to use checksums |
a34f228a393ab1ad30893c7b989dbfff027f5b3ff00cf5e8f4b6aefcf7b6580c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.5
|
Security for odoo12-addon-report-xml 12.0.1.0.0.99.dev9
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
