OCA reporting engine fork for dev and update.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

40 lines
1.6 KiB

  1. This module extends the functionality of reporting, to support creation
  2. of extra custom reports.
  3. It allows user to write a custom SQL request. (Generally, admin users)
  4. Once written, a new model is generated, and user can map the selected field
  5. with odoo fields.
  6. Then user ends the process, creating new menu, action and graph view.
  7. Technically, the module create SQL View (or materialized view, if option is
  8. checked). Materialized view duplicates datas, but request are fastest. If
  9. materialized view is enabled, this module will create a cron task to refresh
  10. the data).
  11. By default, users member of 'SQL Request / User' can see all the views.
  12. You can specify extra groups that have the right to access to a specific view.
  13. Warning
  14. -------
  15. This module is intended for technician people in a company and for Odoo integrators.
  16. It requires the user to know SQL syntax and Odoo models.
  17. If you don't have such skills, do not try to use this module specially on a production
  18. environment.
  19. Use Cases
  20. ---------
  21. this module is interesting for the following use cases
  22. * You want to realize technical SQL requests, that Odoo framework doesn't allow
  23. (For exemple, UNION with many SELECT) A typical use case is if you want to have
  24. Sale Orders and PoS Orders datas in a same table
  25. * You want to customize an Odoo report, removing some useless fields and adding
  26. some custom ones. In that case, you can simply select the fields of the original
  27. report (sale.report model for exemple), and add your custom fields
  28. * You have a lot of data, and classical SQL Views have very bad performance.
  29. In that case, MATERIALIZED VIEW will be a good solution to reduce display duration