YouTube video by Milynize

Revealing a Global Workspace in Language Models

The Visitor (2024) ⭐ I4.4/10 🎬 Comedy 🗣️ L English 📺 QWEB-DL 🖥️ R1080p | 720p 📅 R2024-12-05 (United Kingdom) 🎭 Bishop Black, Amy Kingsmill, Macklin Kowal, Ray Filar, Kurtis Lincoln, Luca Federici, Joh...

> Learn how to build professional PDF reports in **Odoo 19** using **QWeb**. This guide covers everything from creating your first report to advanced techniques like reusable templates, custom paper formats, barcodes, multilingual reports, RTL support, and performance optimization. ## Introduction Every Odoo application relies on reports. Whether you're printing: * Sales Quotations * Customer Invoices * Purchase Orders * Delivery Slips * Manufacturing Orders * Inventory Labels * Payroll Documents * Custom Certificates you're using **QWeb** , Odoo's XML-based templating engine. Although creating a basic report is straightforward, building **maintainable, scalable, and professional** reports requires understanding how the entire reporting pipeline works. In this tutorial, we'll build a complete report from scratch while exploring best practices used by experienced Odoo developers. By the end of this guide, you'll be able to: * Create custom PDF reports * Understand how Odoo generates PDFs * Design reusable templates * Display relational data * Build dynamic tables * Format currencies and dates correctly * Add company logos, images, barcodes, and QR codes * Create custom paper formats * Pass additional data from Python * Optimize report performance * Debug common QWeb issues # How Odoo Generates a PDF Before writing any XML, it's important to understand the report generation process. User clicks "Print" │ ▼ ir.actions.report │ ▼ Report Model (_get_report_values) │ ▼ QWeb Template │ ▼ Rendered HTML │ ▼ wkhtmltopdf │ ▼ PDF Download Each step has a specific responsibility: Component | Responsibility ---|--- ir.actions.report | Registers the report Report Model | Prepares business data QWeb | Generates HTML wkhtmltopdf | Converts HTML into PDF Understanding this workflow makes debugging significantly easier. # Project Structure A clean module structure helps keep reports maintainable. my_module/ │ ├── models/ │ └── sale_order.py │ ├── report/ │ ├── sale_order_report.xml │ ├── report_action.xml │ └── paperformat.xml │ ├── security/ │ ├── views/ │ └── __manifest__.py Keeping reports inside a dedicated `report` directory is considered best practice. # Step 1 — Create the Report Action Every report starts with an `ir.actions.report`. This record tells Odoo: * which model the report belongs to * which template should be rendered * whether it should generate HTML or PDF * where the report appears in the UI <record id="action_sale_order_custom" model="ir.actions.report"> <field name="name">Sale Order PDF</field> <field name="model">sale.order</field> <field name="report_type">qweb-pdf</field> <field name="report_name"> my_module.sale_order_report </field> <field name="report_file"> my_module.sale_order_report </field> <field name="binding_model_id" ref="sale.model_sale_order"/> <field name="binding_type"> report </field> </record> After installing the module, your report automatically appears inside the **Print** menu. 💡 **Pro Tip:** Always use descriptive report IDs. It makes debugging much easier. # Step 2 — Create the QWeb Template The template defines the visual appearance of your report. <template id="sale_order_report"> <t t-call="web.html_container"> <t t-foreach="docs" t-as="o"> <t t-call="web.external_layout"> <div class="page"> <h2>Sale Order</h2> <p> <strong>Customer:</strong> <span t-field="o.partner_id"/> </p> <p> <strong>Date:</strong> <span t-field="o.date_order"/> </p> </div> </t> </t> </t> </template> Although this template is small, it demonstrates the three most important building blocks of every QWeb report. # Understanding Every XML Tag ## `web.html_container` Creates the HTML document wrapper required before converting HTML into PDF. <t t-call="web.html_container"> ## `web.external_layout` Adds the standard company layout automatically. It includes: * Company Logo * Company Address * Header * Footer * Page Numbers Without this layout your report will not look like a standard Odoo document. ## `div.page` Every printable page should be wrapped inside: <div class="page"> This tells wkhtmltopdf where pages begin. # Accessing Data When multiple records are printed, Odoo sends them to the template inside the variable: docs This loop iterates over every selected record. <t t-foreach="docs" t-as="o"> Think of it like Python: for o in docs: # Displaying Fields The preferred way to display model fields is: <span t-field="o.partner_id"/> Why? Because `t-field` automatically applies: * Translations * Currency formatting * Date formatting * Timezone conversion * Decimal precision Whenever you're displaying an Odoo field, prefer `t-field` over `t-out`. # `t-field` vs `t-out` ## t-field <span t-field="o.amount_total"/> Automatically formats values. ## t-out <t t-out="o.amount_total"/> Outputs the raw evaluated expression. Use it when displaying Python expressions instead of model fields. # Creating Tables Most reports display one2many records. Example: <table class="table"> <thead> <tr> <th>Product</th> <th>Qty</th> <th>Unit Price</th> <th>Total</th> </tr> </thead> <tbody> <tr t-foreach="o.order_line" t-as="line"> <td> <span t-field="line.product_id"/> </td> <td> <span t-field="line.product_uom_qty"/> </td> <td> <span t-field="line.price_unit"/> </td> <td> <span t-field="line.price_total"/> </td> </tr> </tbody> </table> This works exactly like iterating over a Python list. # Conditional Rendering Display content only when necessary. <t t-if="o.state == 'sale'"> <div class="alert alert-success"> Confirmed Order </div> </t> Else: <t t-if="o.amount_total > 1000"> VIP Customer </t> <t t-else=""> Regular Customer </t> # Images Company Logo <img t-if="o.company_id.logo" t-att-src="image_data_uri(o.company_id.logo)" style="height:80px;"/> Product Image <img t-if="line.product_id.image_128" t-att-src="image_data_uri(line.product_id.image_128)" style="width:60px;"/> # Barcodes Odoo can generate barcodes without additional libraries. <img t-att-src="'/report/barcode/Code128/%s' % o.name"/> Useful for: * Inventory * Manufacturing * Shipping * Warehouses # QR Codes Generating QR codes follows the same principle. Perfect for: * Payment Links * Product URLs * Customer Verification * Digital Certificates # Custom Paper Formats Need receipts? Shipping labels? A5? Letter? Create a custom paper format. <record id="paperformat_custom" model="report.paperformat"> <field name="name">A5 Landscape</field> <field name="format">A5</field> <field name="orientation">Landscape</field> </record> Then assign it to your report action. # Passing Extra Data from Python Complex calculations belong in Python—not XML. class SaleOrderReport(models.AbstractModel): _name = "report.my_module.sale_order_report" def _get_report_values(self, docids, data=None): docs = self.env["sale.order"].browse(docids) return { "docs": docs, "grand_total": sum( docs.mapped("amount_total") ), } Inside QWeb: <t t-out="grand_total"/> 💡 **Best Practice:** Keep business logic inside Python. Use QWeb only for presentation. # Calling Reports from Python Generate reports programmatically. return self.env.ref( "my_module.action_sale_order_custom" ).report_action(self) Perfect for: * Buttons * Wizards * Scheduled Actions * Automated Workflows # Reusable Templates Instead of duplicating headers or tables, extract them into reusable templates. <t t-call="my_module.report_header"/> This dramatically reduces maintenance. # Multilingual Reports Odoo automatically translates field labels according to the customer's language. Always use translated strings whenever possible. # RTL Support Need Arabic reports? Add RTL CSS. body{ direction:rtl; text-align:right; } Use fonts that support Arabic glyphs for consistent rendering. # Performance Tips Large reports can become slow. Follow these recommendations: * Move calculations into Python. * Avoid nested loops. * Minimize database queries. * Reuse templates. * Cache expensive computations. * Use `mapped()` instead of repeated traversals. # Common Mistakes ❌ Putting business logic inside XML. ❌ Using `t-out` instead of `t-field`. ❌ Forgetting `web.external_layout`. ❌ Missing `<div class="page">`. ❌ Large nested loops. ❌ Hardcoded text instead of translations. # Debugging Checklist If the PDF is blank: * Check XML syntax. * Verify the template ID. * Confirm the report action. * Test HTML rendering. * Review server logs. If CSS is broken: Remember that **wkhtmltopdf** doesn't support every modern CSS feature. Keep layouts simple. # Best Practices ✅ Use descriptive template names. ✅ Keep XML focused on presentation. ✅ Put calculations in Python. ✅ Reuse templates. ✅ Test with realistic data. ✅ Support multiple languages. ✅ Follow Odoo coding standards. # Conclusion QWeb is much more than an XML templating engine—it's the foundation of every printable business document in Odoo. By understanding the entire reporting pipeline, structuring templates correctly, separating business logic from presentation, and following best practices, you can build reports that are scalable, maintainable, and production-ready. Whether you're creating invoices, quotations, delivery slips, manufacturing work orders, inventory labels, or custom business documents, mastering QWeb is an essential skill for every Odoo developer. If you're just starting with Odoo reporting, begin with a simple template, experiment with dynamic fields and loops, then progressively explore advanced topics like reusable templates, multilingual reports, RTL support, custom paper formats, and report optimization. Happy coding! 🚀

Hello everyone! Welcome back to Odoistic, your go-to channel for Odoo tutorials, tips, and deep dives. Today, we're diving into a feature that's set to transform how you customize Odoo's front-end: Odoo 19 inner inheritance. This powerful new addition to Odoo 19's QWeb templating engine introduces a game-changing mode='inner' that allows for incredibly precise and safe template modifications. If you've ever struggled with complex XPath expressions or feared that an Odoo update might break your carefully crafted customizations, then this article is for you. We’ll break down exactly how&hellip;

In the world of business, first impressions matter. From your marketing materials to your official documents, every touchpoint reflects your brand's professionalism and attention to detail. For businesses utilizing Odoo, one such critical document is the invoice receipt. While Odoo provides robust default templates, there often comes a need to tailor these to specific branding, legal requirements, or operational preferences. This is where the power of&hellip;

Partner-Based Product Restriction Odoo 18 ecommerce controller lets you limit storefront products per customer effortlessly. First, you will set up a custom module. Next, you will add partner fields and override the /shop route. Then, you will update QWeb templates to reflect filtered products. Moreover, you will test user flows and handle errors. Finally, you will follow best practices to maintain your code.

Step-by-Step Tutorial Odoo 18 OWL dashboard empowers you to build custom, interactive dashboards right inside Odoo with minimal code. First, you will learn how to set up your module structure. Next, you will configure assets and QWeb templates. Then, you will implement a JSON controller for live data. Moreover, you will create OWL components to fetch and render data. Finally, you will test and deploy your dashboard in Odoo 18.

Introduction Odoo Portal Template External ID stands as a cornerstone for customizing your Odoo portal experience. In this comprehensive tutorial, we will walk you through the process of finding and using an Odoo portal template external ID while simultaneously diving deep into effective portal customization practices. Firstly, you will learn the importance of the external ID in linking your portal templates to the underlying Odoo system, and secondly, you will explore practical examples and code explanations that show how to customize your portal in real time.

Welcome to this comprehensive tutorial on Odoo Portal Customization. In this guide, you will learn how to transform your Odoo 17 Portal Template into dynamic portal sections using the powerful Odoo QWeb Template engine and advanced website customization techniques. You will explore every detail—from modifying XML code to integrating dynamic backend data—to boost your Odoo website customization. We use practical code examples and explain every step in plain language so that you can quickly master the process.

Introduction Odoo Website Customization empowers you to dynamically edit and manage fields directly on your live website. In this tutorial, we explore how to create editable fields in Odoo Website Edit Mode, setup dynamic QWeb templates, and build a custom controller. We start by explaining each step clearly using active language and smooth transitions, so you can follow along easily. From setting up your Odoo environment to testing the results on your website, every sentence guides you in a direct, action-focused style.

Introduction to Odoo Controllers and Routes Odoo Controllers and Routes empower you to build dynamic web pages and add website support to your custom modules in Odoo 16. In this tutorial, we demonstrate how you can use Odoo Controllers and Routes to customize your website, integrate dynamic content, and render your custom QWeb templates. We start by setting up the environment, then proceed to create a QWeb template, build a controller to render your webpage, and finally customize the layout further.

Introduction to Odoo Controllers and Routes Odoo Controllers and Routes empower developers to create dynamic and responsive websites with ease. In this tutorial, we explain how you can build and customize an Odoo website controller, define clear routes, and render QWeb templates to display data effectively. We begin with a simple example and gradually increase complexity while always using active voice and smooth transition words.

Introduction to Odoo Controllers and Routes Odoo Controllers and Routes empower developers to create dynamic and responsive websites with ease. In this tutorial, we explain how you can build and customize an Odoo website controller, define clear routes, and render QWeb templates to display data effectively. We begin with a simple example and gradually increase complexity while always using active voice and smooth transition words.

In this tutorial, we explore Odoo Web Portal Pagination by building an Odoo 17 web module that implements pagination in a user-friendly web portal. We use an Odoo controller and QWeb template to create a product listing page that features a pager. Additionally, we create a clean and modular design, and we integrate key pagination elements such as the website helper and product model queries.

YouTube video by Cizokat