- Home
- Skills
- Ahmed Lakosha
- Odoo Plugins
- Odoo Report
odoo-report_skill
- Python
18
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
3 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill ahmed-lakosha/odoo-plugins --skill odoo-report- SKILL.md60.9 KB
Overview
This skill provides a complete toolkit for creating, managing, validating, and migrating Odoo email templates and QWeb PDF reports across Odoo 14–19. It includes wkhtmltopdf setup, Arabic/RTL and bilingual patterns, and version-aware fixes to keep templates working when upgrading Odoo. It is focused on mail.template and QWeb body_html workflows and automates common validation and migration tasks.
How this skill works
The skill inspects mail.template records, classifies templates by language and rendering engine, and renders subject and header fields via the inline_template engine while rendering body_html with QWeb. It validates syntax, checks attachments/report_template links, applies layout contexts, and can generate previews or PDF via wkhtmltopdf. When migrating, it detects version-specific patterns (field names, report_template_ids, t-out vs t-esc, template_category) and applies guided fixes.
When to use it
- Creating new email templates or QWeb PDF reports for any model
- Previewing or debugging rendering errors (Jinja2/inline or QWeb)
- Migrating templates between Odoo versions 14→19 and fixing breaking changes
- Adding RTL/Arabic support or bilingual email patterns
- Generating PDF attachments via wkhtmltopdf and validating report actions
Best practices
- Always test templates using the preview command with representative records and languages
- Store report actions and link them via report_template_ids on Odoo 17+ to avoid broken attachments
- Use mail layouts (mail_notification_layout) and layout context variables for consistent branding
- Prefer t-out and safe formatting helpers (format_amount, format_date) for QWeb output where supported
- Include auto_delete for temporary templates and keep static attachments minimal to reduce email size
Example use cases
- Create a bilingual invoice email with PDF attachment and company branding colors
- Migrate a legacy Odoo 14 template that used t-esc to a modern t-out QWeb pattern and fix report links
- Debug missing fields in subject or recipient fields caused by inline_template evaluation errors
- Add RTL support and proper font/dir attributes to Arabic notification templates
- Generate a preview PDF of a QWeb report and verify header/footer and signature rendering
FAQ
Supported versions are Odoo 14, 15, 16, 17, 18 and 19; primary development targets Odoo 17.
How does it handle PDF generation?
PDF generation uses wkhtmltopdf configuration and the report action linked from the template; the skill validates wkhtmltopdf availability and report_template links before rendering PDFs.
Will it break custom templates when migrating?
The tool detects common breaking changes (field renames, engine flags, report_template_ids) and offers fixes; manual review is recommended for highly customized templates.