Community mailing list archives
Re: Report Writer in Odoo (RML, QWeb and other issues)by
Firstly, thanks for articulating the lack of solid reporting in Odoo. We have found ourselves in the similar boat , tried different reporting options RML, WebKit, Jasper / Pentaho and ended up with different set of reports developed in different technologies - It gets the Job done from our end, but when customer requests us to show them to change small reporting design issues which they want to do themselves than we don’t have an answer ,except saying to them we will do it, which is not an ideal solution and more importantly we don’t charge for those small changes, not productive at all.
We have categorised two areas :- 1) Reports - Like Invoices and other transactional reporting 2) Business Intelligence - We use Tableau
RU3IX Pty Ltd
On 4 Mar 2015, at 10:47 pm, Nuria Arranz Velazquez <firstname.lastname@example.org> wrote:Report Writer in OdooWhen we migrated our old V6.1 Odoo to V8, we had all sort of problems with our Stationary reports, like Invoices.It was not a straight-forward transition with either RML nor QWeb, and we want to share our experience with the community and learn what is the community experience too, so please do give us your feedback, we’d really appreciate it.
How is Odoo Report Editing at the moment?At the moment, Odoo is pointing at deprecating RML files and using QWeb views to replace them, and an inbuilt WebKit that will allow the user to do headers and footers in html and css rather than the current RML sitting in the Company Settings screen.This would be good when we get there, but at the moment there are a number of issues outstanding:
- To display your main logo you need to add a system parameter by going to Settings > Technical > Parameters > System Parameters and then create an item with:
- Key: report.url
- You need to have wkhtmltopdf version 12.1 for the headers and footers to work.
- wkhtmltopdf 12.1 is known to have bugs related to pagination that affect headers and footers.
- From the UI Odoo forces you to work on original views by:
- Not assigning an External ID (which corresponds to the xml_id of the object) to new views.
- Not allowing the user to edit/add the External ID on any new view.
- Without a xml_id, views cannot be called using the <t-call> tags, which means although you can create new views, you cannot include them in any other views.
- To add an xml_id to a new view, the user needs to and access to source code located in the back end files in the addons directory and manually hard-coding an xml_id into them.
- This means that a customer without programming knowledge cannot successfully create a report and apply it.
- It is possible to alter the layout of a report using the WebBuilder, by changing the type of the view from PDF to HTML and editing it on your browser. Problems:
- This will only edit the static content. Any variables needed, like Company Name, Contact Address, etc., need to be added through the view in the Settings options.
- Testing is slow and arduous because you are required to change the view type every so often to check that the pdf version works with the changes, at the same time than working on the view itself, and this will only work if you have the correct version of the library and don’t encounter any more bugs with headers and footers.
- The HTML editor in the WebBuilder only edits the wrapper of the page, not the content, which means that to use it you would need to copy the xml code from the view in the Settings, paste it in the editor and debug the code before you can start making changes to the report.In other words: If you want to edit a report you need to pay a software development company fluent in xml and QWeb and familiar with Odoo’s platform and Python, to go into your source code and do the necessary changes.
What is needed?A way for users to alter / create a report through the UI without having to revert to the back end files in the addons directory.
The basicThe way of making this possible with the minimal effort would be:
- Automatically assigning xml_id to any new view.
- Fixing the wkhtmltopdf known bugs.
- Adding to the reporting editing documentation notes about what library version needs to be used and steps to install/upgrade it.
2. WebBuilder Functionality applied to ReportsCreate a module that:
- Applies the WebBuilder blocks concept to create the layout of the report.
- Extend the HTML editor to display the content of the page as well as the outer frame.
3. New Report Designer pluginSame concept than the old OpenOffice Report Designer, but up to date and able to work with newer versions of OpenOffice AND LibreOffice.A good example of a report designer is the OpenDoc Mill:
CommunityThe purpose of putting this to the community is to report on our findings and find out if this is consistent with what others have found, so:Have you found the same issues? Please post to the list your experiences.Also, it's probably worth mentioning that we have created a set of UK friendly sales order and invoice documents and will make available to anyone who wants them through github.-- N. Arranz-Velazquez OpusVL Odoo Specialist Team (OOST) OpusVL Drury House Drury Lane Rugby CV21 3DE T: 01788 298 450 W: www.opusvl.com
OpusVL, Nuria Arranz-Velazquez