Se rendre au contenu
Icône de BI SQL Editor

BI SQL Editor

par OCA · bi_sql_editor

BI Views builder, based on Materialized or Normal SQL Views

19.0 — à porter Module Contrôle qualité : Vérifiée AGPL-3

BI SQL Editor

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

Configuration

  • Go to Dashboard / Configuration / SQL Views

  • tip your SQL request

  • Select the group(s) that could have access to the view

Optionnaly, you can add a domain.

A tipical domain in a multi company context is to write ['|', ('company_id', '=', False), ('company_id', 'in', company_ids)] to make reporting depending on the current companies of the user.

  • Click on the button ‘Validate SQL Expression’

  • 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. On top of that, if the field is of type Many2one, you can also select the option to be clickable on the list view.

  • Click on the button ‘Create SQL elements’. (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)
  • 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 ‘Dashboards > SQL Reports’
  2. Select the desired report
  • You can switch to ‘Graph’ or ‘tree’ views as any report.

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.

Authors

  • GRAP

Contributors

Other credits

The migration of this module from 17.0 to 18.0 was financially supported by Camptocamp.

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.

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.

BI SQL Editor — capture 1
BI SQL Editor — capture 1
BI SQL Editor — capture 2
BI SQL Editor — capture 2
BI SQL Editor — capture 3
BI SQL Editor — capture 3
BI SQL Editor — capture 4
BI SQL Editor — capture 4
BI SQL Editor — capture 5
BI SQL Editor — capture 5

Ce que l'application ne fait pas

L'éditeur n'a pas encore publié la liste de ce que l'application ne fait pas. C'est une règle du magasin : demandez-la au support avant de vous engager.

Applications du magasin nécessaires

Modules Odoo Community utilisés

spreadsheet_dashboard

SérieVersionÉtatPubliée le
19.019.0.2.0.1 En développement 23/09/2026

Fiche générée depuis julien2364/omnifloo-oca-reporting-engine (branche 19.0, commit b9e8c6cdd2d1).

Contrôle automatique du magasin (distinct de l'éditeur), appliqué à toutes les applications. Conforme.

ContrôleRésultatEffet si absent
Manifeste lisible sans exécution conforme bloquant
Licence reconnue (AGPL-3) conforme bloquant
Aucune dépendance vers Odoo Enterprise conforme bloquant
Aucun import de code Enterprise conforme bloquant
Aucun en-tête de licence Enterprise conforme bloquant
Icône static/description/icon.png conforme déclasse
Description (static/description/index.html ou README) conforme déclasse
Tests automatisés (tests/test_*.py) conforme déclasse
Traduction française (i18n/fr.po) conforme info
Section « Ce que le module ne fait pas » absent info

Avis des clients connectés. Un avis noté par client ; l'éditeur peut y répondre. Connectez-vous pour laisser un avis.

Éditeur
Odoo Community Association (OCA)
Signaler un problème
https://github.com/OCA/reporting-engine
Clients Omnifloo
Support inclus selon votre formule : centre d'aide.