+
+
Choose a language:
+
Choose an engine:
+
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.
diff --git a/bi_view_editor/__manifest__.py b/bi_view_editor/__manifest__.py index 3ed1160..dfd43e3 100644 --- a/bi_view_editor/__manifest__.py +++ b/bi_view_editor/__manifest__.py @@ -12,6 +12,9 @@ "version": "2.0.1.0.0", "development_status": "Beta", "depends": ["web"], + "external_dependencies": { + "deb": ["graphviz"], + }, "data": [ "security/ir.model.access.csv", "security/rules.xml", diff --git a/kpi_dashboard/__manifest__.py b/kpi_dashboard/__manifest__.py index d2ad227..b61c9fc 100644 --- a/kpi_dashboard/__manifest__.py +++ b/kpi_dashboard/__manifest__.py @@ -5,7 +5,7 @@ "name": "Kpi Dashboard", "summary": """ Create Dashboards using kpis""", - "version": "2.0.1.0.0", + "version": "2.0.1.1.0", "license": "AGPL-3", "author": "Creu Blanca,Odoo Community Association (OCA)", "website": "https://gitlab.com/flectra-community/reporting-engine", diff --git a/kpi_dashboard/i18n/kpi_dashboard.pot b/kpi_dashboard/i18n/kpi_dashboard.pot index 561120e..19ce953 100644 --- a/kpi_dashboard/i18n/kpi_dashboard.pot +++ b/kpi_dashboard/i18n/kpi_dashboard.pot @@ -99,6 +99,7 @@ msgid "Computation Method" msgstr "" #. module: kpi_dashboard +#: model:ir.model.fields,field_description:kpi_dashboard.field_kpi_dashboard_item__compute_on_fly #: model:ir.model.fields,field_description:kpi_dashboard.field_kpi_kpi__compute_on_fly msgid "Compute On Fly" msgstr "" @@ -549,6 +550,11 @@ msgstr "" msgid "Size Y of the widget cannot be bigger than 10" msgstr "" +#. module: kpi_dashboard +#: model:ir.model.fields,field_description:kpi_dashboard.field_kpi_dashboard_item__special_context +msgid "Special Context" +msgstr "" + #. module: kpi_dashboard #: model:ir.model.fields,field_description:kpi_dashboard.field_kpi_kpi__store_history msgid "Store History" diff --git a/kpi_dashboard/models/kpi_dashboard.py b/kpi_dashboard/models/kpi_dashboard.py index 740d737..2c1d906 100644 --- a/kpi_dashboard/models/kpi_dashboard.py +++ b/kpi_dashboard/models/kpi_dashboard.py @@ -3,6 +3,7 @@ from flectra import _, api, fields, models from flectra.exceptions import ValidationError +from flectra.tools.safe_eval import safe_eval class KpiDashboard(models.Model): @@ -119,9 +120,11 @@ class KpiDashboardItem(models.Model): color = fields.Char() font_color = fields.Char() modify_context = fields.Boolean() + compute_on_fly = fields.Boolean(related="kpi_id.compute_on_fly") modify_context_expression = fields.Char() modify_color = fields.Boolean() modify_color_expression = fields.Char() + special_context = fields.Char() @api.depends("row", "size_y") def _compute_end_row(self): @@ -195,9 +198,17 @@ class KpiDashboardItem(models.Model): } ) if self.kpi_id.compute_on_fly: + kpi = self.kpi_id + if self.special_context: + try: + ctx = safe_eval(self.special_context) + if isinstance(ctx, dict): + kpi = kpi.with_context(**ctx) + except SyntaxError: + pass vals.update( { - "value": self.kpi_id._compute_value(), + "value": kpi._compute_value(), "value_last_update": fields.Datetime.now(), } ) diff --git a/kpi_dashboard/views/kpi_dashboard.xml b/kpi_dashboard/views/kpi_dashboard.xml index a3fd462..fb5d3d3 100644 --- a/kpi_dashboard/views/kpi_dashboard.xml +++ b/kpi_dashboard/views/kpi_dashboard.xml @@ -162,15 +162,15 @@ widget="ace" options="{'mode': 'python'}" /> +
Define KPI dashboard graphs using bokeh.
+Table of contents
+In order to define the value, you can must define a function like:
+
+from bokeh.plotting import figure
+from bokeh.embed import components
+
+def test_demo_bokeh(self):
+ p = figure(width=1000, height=1000, sizing_mode="scale_both")
+ # import that as `from bokeh.plotting import figure`
+ p.line([0, 1, 2], [1, 10, random.random() * 10], line_width=5)
+ # (...)
+ # fill the record field with both markup and the script of a chart.
+ script, div = components(p)
+ return {"bokeh": "%s%s" % (div, script)}
+
+You can also use code. The following items will be added automatically to the +code items:
+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.
+Do not contact contributors directly about support or help with technical issues.
+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.
+
+
|
+
\n"
+"
| \n"
+"
The new menu “Report Center” is the central place to host your reports in one place. +From here, there are 2 ways to launch the report,
+By using the queue job, option 2 is great for long running report. +The report file will be saved for later use, with the option to send report +by email as soon as it is ready.
+Notes:
+Table of contents
+Menu: Dashboard > Report Center
+As Technical Feature users, you can manage reports for Report Center.
+As normal user, you can run your reports from Report Center
+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.
+Do not contact contributors directly about support or help with technical issues.
+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.
+Current maintainer:
+
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.
++ No files found +
+
This module provides a basic report class to generate csv report.
+Table of contents
+An example of CSV report for partners on a module called module_name:
+A python class
+
+from odoo import models
+
+class PartnerCSV(models.AbstractModel):
+ _name = 'report.report_csv.partner_csv'
+ _inherit = 'report.report_csv.abstract'
+
+ def generate_csv_report(self, writer, data, partners):
+ writer.writeheader()
+ for obj in partners:
+ writer.writerow({
+ 'name': obj.name,
+ 'email': obj.email,
+ })
+
+ def csv_report_options(self):
+ res = super().csv_report_options()
+ res['fieldnames'].append('name')
+ res['fieldnames'].append('email')
+ res['delimiter'] = ';'
+ res['quoting'] = csv.QUOTE_ALL
+ return res
+
+A report XML record
++<report + id="partner_csv" + model="res.partner" + string="Print to CSV" + report_type="csv" + name="module_name.report_name" + file="res_partner" + attachment_use="False" +/> ++
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.
+Do not contact contributors directly about support or help with technical issues.
+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.
+
This module provides new report template +with possibility to add image to replace header and footer.
+Table of contents
+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.
+Do not contact contributors directly about support or help with technical issues.
+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.
+
The py3o reporting engine is a reporting engine for Odoo based on Libreoffice:
+The key advantages of a Libreoffice based reporting engine are:
+This module report_py3o is the base module for the Py3o reporting engine. If used alone, it will spawn a libreoffice process for each ODT to PDF (or ODT to DOCX, ..) document conversion. This is slow and can become a problem if you have a lot of reports to convert from ODT to another format. In this case, you should consider the additionnal module report_py3o_fusion_server which is designed to work with a libreoffice daemon. With report_py3o_fusion_server, the technical environnement is more complex to setup because you have to install additionnal software components and run 2 daemons, but you have much better performances and you can configure the libreoffice PDF export options in Odoo (allows to generate PDF forms, PDF/A documents, password-protected PDFs, watermarked PDFs, etc.).
+This reporting engine is an alternative to Aeroo: 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.
+Table of contents
+Install the required python libs:
++pip install py3o.template +pip install py3o.formats ++
To allow the conversion of ODT or ODS reports to other formats (PDF, DOC, DOCX, etc.), install libreoffice:
++apt-get --no-install-recommends install libreoffice ++
For example, to replace the native invoice report by a custom py3o report, add the following XML file in your custom module:
++<?xml version="1.0" encoding="utf-8"?> +<odoo> + +<record id="account.account_invoices" model="ir.actions.report"> + <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> ++
where my_custom_module_base is the name of the custom Odoo module. In this example, the invoice ODT file is located in my_custom_module_base/report/account_invoice.odt.
+It’s also possible to reference a template located in a trusted path of your +Odoo server. In this case you must let the module entry empty and specify +the path to the template as py3o_template_fallback.
++<?xml version="1.0" encoding="utf-8"?> +<odoo> + +<record id="account.account_invoices" model="ir.actions.report"> + <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> ++
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.
++[options] +... + +[report_py3o] +root_tmpl_path=/odoo/templates/py3o ++
If you want an invoice in PDF format instead of ODT format, the XML file should look like:
++<?xml version="1.0" encoding="utf-8"?> +<odoo> + +<record id="account.account_invoices" model="ir.actions.report"> + <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> ++
If you want to add a new py3o PDF report (and not replace a native report), the XML file should look like this:
++<?xml version="1.0" encoding="utf-8"?> +<odoo> + +<record id="partner_summary_report" model="ir.actions.report"> + <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> + <!-- Add entry in "Print" drop-down list --> + <field name="binding_type">report</field> + <field name="binding_model_id" ref="base.model_res_partner"/> +</record> + +</odoo> ++
The templating language is extensively documented, the records are exposed in libreoffice as objects, on which you can also call functions.
+Sample py3o report templates for the main Odoo native reports (invoice, sale order, purchase order, picking, etc.) are available on the Github project odoo-py3o-report-templates.
+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.
+Do not contact contributors directly about support or help with technical issues.
+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.
+