v 15.0 Third Party 3201
Download for v 15.0 Deploy on Odoo.sh
Availability
Odoo Online
Odoo.sh
On Premise
Community Apps Dependencies
Lines of code 1162
Technical Name bi_sql_editor
LicenseAGPL-3
Websitehttps://github.com/OCA/reporting-engine
Versions 17.0 9.0 15.0 8.0 10.0 11.0 12.0 13.0 16.0 14.0
You bought this module and need support? Click here!

BI SQL Editor

Beta License: AGPL-3 OCA/reporting-engine Translate me on Weblate Try me on Runboat

This module extends the functionality of reporting, to support creation of extra custom reports. It allows user to write a custom SQL request. (Generally, admin users)

Once written, a new model is generated, and user can map the selected field with odoo fields. Then user ends the process, creating new menu, action and graph view.

Technically, the module create SQL View (or materialized view, if option is checked). Materialized view duplicates datas, but request are fastest. If materialized view is enabled, this module will create a cron task to refresh the data).

By default, users member of ‘SQL Request / User’ can see all the views. You can specify extra groups that have the right to access to a specific view.

Warning

This module is intended for technician people in a company and for Odoo integrators.

It requires the user to know SQL syntax and Odoo models.

If you don’t have such skills, do not try to use this module specially on a production environment.

Use Cases

this module is interesting for the following use cases

  • You want to realize technical SQL requests, that Odoo framework doesn’t allow (For exemple, UNION with many SELECT) A typical use case is if you want to have Sale Orders and PoS Orders datas in a same table
  • You want to customize an Odoo report, removing some useless fields and adding some custom ones. In that case, you can simply select the fields of the original report (sale.report model for exemple), and add your custom fields
  • You have a lot of data, and classical SQL Views have very bad performance. In that case, MATERIALIZED VIEW will be a good solution to reduce display duration

Table of contents

Installation

  • You must put this module as server_wide_modules in your odoo configuration file or add ‘–load=bi_sql_editor’ if you start odoo in command line.

Configuration

To configure this module, you need to:

  • Go to Settings / Technical / Database Structure / SQL Views

  • tip your SQL request

    https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/01_sql_request.png
  • Select the group(s) that could have access to the view

    https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/02_security_access.png
  • Click on the button ‘Clean and Check Request’

  • Once the sql request checked, the module analyses the column of the view, and propose field mapping. For each field, you can decide to create an index and set if it will be displayed on the pivot graph as a column, a row or a measure.

    https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/03_field_mapping.png
  • Click on the button ‘Create SQL View, Indexes and Models’. (this step could take a while, if view is materialized)

  • If it’s a MATERIALIZED view:

    • a cron task is created to refresh the view. You can so define the frequency of the refresh.
    • the size of view (and the indexes is displayed)
    https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/04_materialized_view_setting.png
  • Before applying the final step, you will need to add a specific Parent Menu to use when creating the UI Menu for the report. By default, it will be set with the SQL Views menu, which can be changed before creating the UI elements in order to have the report accessible from a different place within Odoo.

  • Finally, click on ‘Create UI’, to create new menu, action, graph view and search view.

Usage

To use this module, you need to:

  1. Go to ‘Reporting’ / ‘Custom Reports’
  2. Select the desired report
https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/05_reporting_pivot.png
  • You can switch to ‘Pie’ chart or ‘Line Chart’ as any report,

    https://raw.githubusercontent.com/OCA/reporting-engine/15.0/bi_sql_editor/static/description/05_reporting_pie.png

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

  • GRAP

Contributors

  • Sylvain LE GAL (https://twitter.com/legalsylvain)
  • Richard deMeester, WilldooIT (http://www.willdooit.com/)
  • David James, WilldooIT (http://www.willdooit.com/)
  • Guillem Casassas <guillem.casassas@forgeflow.com>
  • This module is highly inspired by the work of
    • Onestein: (http://www.onestein.nl/) Module: OCA/server-tools/bi_view_editor. Link: https://github.com/OCA/reporting-engine/tree/9.0/bi_view_editor
    • Anybox: (https://anybox.fr/) Module : OCA/server-tools/materialized_sql_view link: https://github.com/OCA/server-tools/pull/110
    • GRAP, Groupement Régional Alimentaire de Proximité: (http://www.grap.coop/) Module: grap/odoo-addons-misc/pos_sale_reporting link: https://github.com/grap/odoo-addons-misc/tree/7.0/pos_sale_reporting

Maintainers

This module is maintained by the OCA.

Odoo Community Association

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:

legalsylvain

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.

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.