Search 1.9 billion lines of Odoo code on GitHub
report_py3o
<a class="reference external image-reference" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.svg">
</a>
<a name="report-py3o"></a>
<h2>Report Py3o</h2>
<p>The py3o reporting engine is a reporting engine for Odoo based on <a class="reference external" href="http://www.libreoffice.org/">Libreoffice</a>:</p>
<ul class="simple">
<li>the report is created with Libreoffice (ODT or ODS),</li>
<li>the report is stored on the server in OpenDocument format (.odt or .ods file)</li>
<li>the report is sent to the user in OpenDocument format or in any output format supported by Libreoffice (PDF, HTML, DOC, DOCX, Docbook, XLS, etc.)</li>
</ul>
<p>The key advantages of a Libreoffice based reporting engine are:</p>
<ul class="simple">
<li>no need to be a developer to create or modify a report: the report is created and modified with Libreoffice. So this reporting engine has a full WYSIWYG report development tool!</li>
<li>For a PDF report in A4/Letter format, it's easier to develop it with a tool such as Libreoffice that is designed to create A4/Letter documents than to develop it in HTML/CSS, also some print peculiarities (backgrounds, margin boxes) are not very well supported by the HTML/CSS based solutions.</li>
<li>If you want your users to be able to modify the document after its generation by Odoo, just configure the document with ODT output (or DOC or DOCX) and the user will be able to modify the document with Libreoffice (or Word) after its generation by Odoo.</li>
<li>Easy development of spreadsheet reports in ODS format (XLS output possible).</li>
</ul>
<p>This reporting engine is an alternative to <a class="reference external" href="https://github.com/aeroo-community/aeroo_reports">Aeroo</a>: these two reporting engines have similar features but their implementation is entirely different. You cannot use aeroo templates as drop in replacement though, you'll have to change a few details.</p>
<a name="installation"></a>
<h3>Installation</h3>
<p>Install the required python libs:</p>
<pre class="code">
<code class="code">pip install py3o.template
pip install py3o.formats</code>
</pre>
<p>To allow the conversion of ODT or ODS reports to other formats (PDF, DOC, DOCX, etc.), install libreoffice:</p>
<pre class="code">
<code class="code">apt-get --no-install-recommends install libreoffice</code>
</pre>
<a name="configuration"></a>
<h3>Configuration</h3>
<p>For example, to replace the native invoice report by a custom py3o report, add the following XML file in your custom module:</p>
<pre class="code">
<code class="code"><?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="account.account_invoices" model="ir.actions.report.xml">
<field name="report_type">py3o</field>
<field name="py3o_filetype">odt</field>
<field name="module">my_custom_module_base</field>
<field name="py3o_template_fallback">report/account_invoice.odt</field>
</record>
</odoo></code>
</pre>
<p>where <em>my_custom_module_base</em> is the name of the custom Odoo module. In this example, the invoice ODT file is located in <em>my_custom_module_base/report/account_invoice.odt</em>.</p>
<p>It's also possible to reference a template located in a trusted path of your
Odoo server. In this case you must let the <em>module</em> entry empty and specify
the path to the template as <em>py3o_template_fallback</em>.</p>
<pre class="code">
<code class="code"><?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="account.account_invoices" model="ir.actions.report.xml">
<field name="report_type">py3o</field>
<field name="py3o_filetype">odt</field>
<field name="py3o_template_fallback">/odoo/templates/py3o/report/account_invoice.odt</field>
</record>
</odoo></code>
</pre>
<p>Moreover, you must also modify the Odoo server configuration file to declare
the allowed root directory for your py3o templates. Only templates located
into this directory can be loaded by py3o report.</p>
<pre class="code">
<code class="code">[options]
...
[report_py3o]
root_tmpl_path=/odoo/templates/py3o</code>
</pre>
<p>If you want an invoice in PDF format instead of ODT format, the XML file should look like:</p>
<pre class="code">
<code class="code"><?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="account.account_invoices" model="ir.actions.report.xml">
<field name="report_type">py3o</field>
<field name="py3o_filetype">pdf</field>
<field name="module">my_custom_module_base</field>
<field name="py3o_template_fallback">report/account_invoice.odt</field>
</record>
</odoo></code>
</pre>
<p>If you want to add a new py3o PDF report (and not replace a native report), the XML file should look like this:</p>
<pre class="code">
<code class="code"><?xml version="1.0" encoding="utf-8"?>
<odoo>
<record id="partner_summary_report" model="ir.actions.report.xml">
<field name="name">Partner Summary</field>
<field name="model">res.partner</field>
<field name="report_name">res.partner.summary</field>
<field name="report_type">py3o</field>
<field name="py3o_filetype">pdf</field>
<field name="module">my_custom_module_base</field>
<field name="py3o_template_fallback">report/partner_summary.odt</field>
</record>
<!-- Add entry in "Print" drop-down list -->
<record id="button_partner_summary_report" model="ir.values">
<field name="key2">client_print_multi</field>
<field name="model">res.partner</field>
<field name="name">Partner Summary</field>
<field name="value" eval="'ir.actions.report.xml,%d'%partner_summary_report" />
</record>
</odoo></code>
</pre>
<a name="configuration-parameters"></a>
<h4>Configuration parameters</h4>
<dl class="docutils">
<dt>py3o.conversion_command</dt>
<dd>The command to be used to run the conversion, <code>libreoffice</code> by default. If you change this, whatever you set here must accept the parameters <code>--headless --convert-to $ext $file</code> and put the resulting file into <code>$file</code>'s directory with extension <code>$ext</code>. The command will be started in <code>$file</code>'s directory.</dd>
</dl>
<a name="usage"></a>
<h3>Usage</h3>
<a class="reference external image-reference" href="https://runbot.odoo-community.org/runbot/143/9.0"><img alt="Try me on Runbot" src="https://odoo-community.org/website/image/ir.attachment/5784_f2813bd/datas" /></a>
<p>The templating language is <a class="reference external" href="http://py3otemplate.readthedocs.io/en/latest/templating.html">extensively documented</a>, the records are exposed in libreoffice as <code>objects</code>, on which you can also call functions.</p>
<a name="available-functions-and-objects"></a>
<h4>Available functions and objects</h4>
<dl class="docutils">
<dt>user</dt>
<dd>Browse record of current user</dd>
<dt>lang</dt>
<dd>The user's company's language as string (ISO code)</dd>
<dt>b64decode</dt>
<dd><code>base64.b64decode</code></dd>
<dt>format_multiline_value(string)</dt>
<dd>Generate the ODF equivalent of <code><br/></code> and <code>&nbsp;</code> for multiline fields (ODF is XML internally, so those would be skipped otherwise)</dd>
<dt>html_sanitize(string)</dt>
<dd>Sanitize HTML string</dd>
<dt>time</dt>
<dd>Python's <code>time</code> module</dd>
<dt>display_address(partner)</dt>
<dd>Return a formatted string of the partner's address</dd>
</dl>
<a name="sample-report-templates"></a>
<h4>Sample report templates</h4>
<p>Sample py3o report templates for the main Odoo native reports (invoice, sale order, purchase order, picking, ...) are available on the Github project <a class="reference external" href="https://github.com/akretion/odoo-py3o-report-templates">odoo-py3o-report-templates</a>.</p>
<a name="known-issues-roadmap"></a>
<h3>Known issues / Roadmap</h3>
<ul class="simple">
<li>generate barcode ?</li>
<li>add more detailed example in demo file to showcase features</li>
<li>add migration guide aeroo -> py3o</li>
</ul>
<a name="bug-tracker"></a>
<h3>Bug Tracker</h3>
<p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/reporting-engine/issues">GitHub Issues</a>. 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.</p>
<a name="credits"></a>
<h3>Credits</h3>
<a name="contributors"></a>
<h4>Contributors</h4>
<ul class="simple">
<li>Florent Aide (<a class="reference external" href="http://odoo.consulting/">XCG Consulting</a>)</li>
<li>Laurent Mignon <<a class="reference external" href="mailto:laurent.mignon@acsone.eu">laurent.mignon@acsone.eu</a>>,</li>
<li>Alexis de Lattre <<a class="reference external" href="mailto:alexis.delattre@akretion.com">alexis.delattre@akretion.com</a>>,</li>
<li>Guewen Baconnier <<a class="reference external" href="mailto:guewen.baconnier@camptocamp.com">guewen.baconnier@camptocamp.com</a>></li>
<li>Omar Castiñeira <<a class="reference external" href="mailto:omar@comunitea.com">omar@comunitea.com</a>></li>
<li>Holger Brunn <<a class="reference external" href="mailto:hbrunn@therp.nl">hbrunn@therp.nl</a>></li>
</ul>
<a name="maintainer"></a>
<h4>Maintainer</h4>
<a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a>
<p>This module is maintained by the OCA.</p>
<p>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.</p>
<p>To contribute to this module, please visit <a class="reference external" href="https://odoo-community.org">https://odoo-community.org</a>.</p>