Odoo 19: Runtime API Documentation for Developers

🚀 Odoo Tip — Access any record using its XML ID When developing in Odoo, you’ll often need to fetch a record that’s defined through XML (like views, templates, or data records). Here’s the clean and reliable way to do it: record = self.env.ref("calendar_sms.sms_template_data_calendar_reminder") ✅ self.env.ref() returns a recordset for the given XML ID ✅ Always use the full XML ID format — <module_name>.<record_id> ✅ Perfect for referencing data loaded through XML files 💡 Pro Tip: To find a record’s XML ID directly from the Odoo UI: 1️⃣ Enable Developer Mode 2️⃣ Open the record’s form view 3️⃣ Click on the 🐞 “Bug” icon → View Metadata 4️⃣ You’ll see the XML ID right there Once you know this trick, navigating and referencing Odoo records becomes a breeze! ⚡ #Odoo #OdooDevelopment #Python #ERP #DevTips

🚀 Odoo Tip — Understanding _name + _inherit (Prototype Inheritance) When you use both _name and _inherit in an Odoo model, you’re not just extending an existing model — you’re copying its entire definition. ✅ Odoo takes all the fields, attributes, and methods from the inherited model and creates a new model with the name given in _name. This is known as Prototype Inheritance. 💡 Key Points: 💠 Prototype inheritance copies the parent model’s fields, attributes, and methods. 💠 You can modify or extend them freely in the child class. 💠 If _name and _inherit are the same, it behaves like a regular extension (not prototype). 💠 It’s rarely used in practice since delegation inheritance (_inherits) often achieves the same goal more efficiently, without duplicating data structures. In this example from Odoo’s base code (addons/mrp), stock.warn.insufficient.qty.unbuild is a new wizard that reuses all logic from stock.warn.insufficient.qty — same behavior, separate model. #Odoo #OdooDevelopment #OdooTips #Python #ERP #Developers

🚀 Odoo Tip — Understanding _name + _inherit (Prototype Inheritance) When you use both _name and _inherit in an Odoo model, you’re not just extending an existing model — you’re copying its entire definition. ✅ Odoo takes all the fields, attributes, and methods from the inherited model and creates a new model with the name given in _name. This is known as Prototype Inheritance. 💡 Key Points: 💠 Prototype inheritance copies the parent model’s fields, attributes, and methods. 💠 You can modify or extend them freely in the child class. 💠 If _name and _inherit are the same, it behaves like a regular extension (not prototype). 💠 It’s rarely used in practice since delegation inheritance (_inherits) often achieves the same goal more efficiently, without duplicating data structures. In this example from Odoo’s base code (addons/mrp), stock.warn.insufficient.qty.unbuild is a new wizard that reuses all logic from stock.warn.insufficient.qty — same behavior, separate model. 👉 If you found this helpful, follow me for more Odoo development insights and repost to share with your network. #Odoo #OdooDevelopment #OdooTips #Python #ERP #Developers

🚀 Odoo Tip of the Day – auto_install in manifest.py Did you know about the auto_install key in Odoo’s module manifest? 👇 📘 auto_install: True This tells Odoo that your module is a “glue module” — it will automatically install when all its dependencies are installed. 💡 For example: If your module bridges sale and account, and both are installed, Odoo will automatically install your glue module too — no manual step needed! 🧩 Perfect for integration modules like: sale_purchase sale_stock This keeps your setup modular, clean, and automated — exactly how Odoo loves it. #Odoo #OdooDevelopment #TechTips #ERP #Python #Manifest

Why .write() in Loops is Slow (Use Batch Processing Instead) 💡 Did you know? Updating 500 records one by one with .write() can be 10x slower than updating them in batches using the ORM. Most developers still do this 👇 🚫 The Slow Way (Loop + .write()) # ❌ Triggers 500 database writes for rec in records: rec.write({'state': 'done'}) ❌ Problem: Each .write() hits the database → 1 SQL query per record ❌ Also triggers computed fields & @api.depends 500 times ❌ Not scalable for large datasets ✅ The Optimized Way — Batch Write in One Line # ✅ Only 1 write — highly efficient records.write({'state': 'done'}) ✔ Only 1 SQL query ✔ Dependencies & constraints triggered once ✔ Best practice for bulk processing ⚙️ Example — Real Use Case from Manufacturing Module # Mark all draft work orders as 'in_progress' work_orders = self.env['mrp.workorder'].search([('state', '=', 'draft')]) work_orders.write({'state': 'in_progress'}) ⏱ 1000+ records updated under a second 📉 Server CPU usage dropped by ~60% 🧠 When to Use Batch Processing? Scenario Batch Write? Updating many records with same value ✅ Yes Writing inside cron jobs or scheduled scripts ✅ Yes Looping to compute different values per record ⚠ Maybe — depends Need to trigger logic for each record individually ❌ Use loop 🌏 Why This Matters for Businesses In high-volume systems (accounting, inventory, payroll), inefficient .write() usage can: – Slow down workers' UI – Increase server load & hosting cost – Delay automation tasks (emails, reports, approvals) Especially in markets like Australia & Europe — where companies care about performance and scalability — these optimizations create real business value. 🤝 Building High-Performance Odoo Systems I focus on building Odoo systems that are clean, maintainable, and scalable — not just “working code”. If you're working on ERP automation or digital transformation and want to discuss ideas, happy to connect. #Odoo #Odoo19 #Performance #Python #ERPDevelopment #BatchProcessing #SydneyTech #OdooConsultant

🚨 Odoo Error Fix: “External dependency qifparse not installed” Ever tried installing base_accounting_kit in Odoo and got this frustrating error? Unable to install module "base_accounting_kit" because an external dependency is not met: External dependency qifparse not installed: No package metadata was found for qifparse Here’s the quick fix for developers facing this issue 🧰 Step-by-Step Solution Activate your Odoo virtual environment: source /opt/odoo/venv/bin/activate pip install qifparse or If that fails, install directly from GitHub: pip install git+https://lnkd.in/dHJ7BnQM Restart your Odoo service: sudo systemctl restart odoo Reinstall your odoo module from Apps — problem solved Why this happens The base_accounting_kit module depends on an external Python library (qifparse) that’s not bundled with Odoo. Without it, Odoo can’t parse QIF (Quicken Interchange Format) files for bank imports. Senior Python + Odoo Consultant @ Full Stack Zone (Pvt) Ltd Helping teams debug, deploy, and scale enterprise Odoo environments #Odoo #Python #ERP #TechTips #FullStackZone #OdooDevelopment #base_accounting_kit #Debugging #Developers

🚨 Odoo Dev Tip — @api.onchange can’t return domains anymore (Odoo 16+) Ever written this classic code? @api.onchange('service_id') def _onchange_service_id(self):   return {'domain': {'task_id': [('service_id', '=', self.service_id.id)]}} …and wondered why it stopped working after upgrading to Odoo 16+? 😅 No error. No warning. It just silently ignores your domain. 💡 Here’s why: Starting with Odoo 16, the frontend runs on OWL — a modern JavaScript framework. It no longer processes return {'domain': ...} values from @api.onchange methods. Domains are now handled entirely client-side, so the old way of “returning” them from Python doesn’t work anymore. ✅ The new correct way You must store your domain in a computed Binary field, so OWL can read it directly from the model — safely and reactively. This approach works in Odoo 16, 17, and 18. 💬 Have you hit this issue after upgrading your modules? Try this Binary Domain pattern — it’s the clean, future-proof solution for modern Odoo #Odoo #Odoo18 #OdooDev #Python #ERP #WebDevelopment #Tips #OpenSource

🚀 Odoo Tip — The Subtle Change in compute_sudo You Might Have Missed When defining computed or related fields in Odoo, you’ve probably seen the attribute compute_sudo=True. But did you know its default behavior changed starting from Odoo v13? 👇 🧩 Before Odoo v13: compute_sudo was always False by default. ⚙️ From Odoo v13 onward: The default value now depends on the store attribute: If store=True → compute_sudo=True If store=False → compute_sudo=False ✅ You can still override this by explicitly setting compute_sudo in your field definition, ensuring the computation runs with superuser rights — especially useful when accessing restricted models like res.users or hr.employee. 💡 Tip: Even for related fields, compute_sudo still applies since they are computed fields under the hood. Being explicit keeps your code consistent and avoids access-right issues across versions. 💡 Enjoyed this tip? Follow for more Odoo tricks and don’t forget to repost to help others learn! #Odoo #OdooTips #ERPDevelopment #Python #ComputedFields #OdooTechnical

 Odoo Icon Maker Skill  Created an automation tool for generating professional icons for Odoo modules.  How it works:  • Input: module name + description keywords  • Output: 128x128 Material Design PNG icon  • Auto-updates __manifest__.py and menu XML files  The script detects visual primitives from keywords (warehouse → box, planning → calendar, tasks → checkbox) and composes them into a clean white background with colored circle design.  Configurable addon directories via config.py. 12 built-in primitives covering most Odoo module types.  Perfect for rapid development of custom Odoo modules without manual icon design.  GitHub: https://lnkd.in/ds9vsF_6 #Odoo #Python #Automation #ERP #OpenSource #SoftwareDevelopment #DevTools #Productivity #MaterialDesign #OdooDevelopment #Claude #AI

🚀 Connecting to Odoo with JSON-RPC Odoo provides multiple RPC APIs to interact with its server — one of them is JSON-RPC, which follows the JSON-RPC 2.0 specification. Interestingly, the Odoo web client itself uses JSON-RPC under the hood to fetch data. Keypoints 🔹 JSON-RPC requests must follow the JSON-RPC 2.0 spec → jsonrpc.org/specification 🔹 Requires {"Content-Type": "application/json"} header 🔹 Works very similar to XML-RPC but returns results in JSON 🔹 The common service is used for login and other public methods 🔹 The object service is used to interact with Odoo models (search, create, write, unlink, etc.) 🔹 JSON-RPC is the same protocol Odoo Web client uses internally, making it a reliable integration option 🔹 You can use any HTTP client (e.g., requests, urllib, axios in JS, etc.) to interact with Odoo via JSON-RPC This method allows you to authenticate and then interact with Odoo models through JSON-RPC calls — just like the web client does. #Odoo #JSONRPC #Python #API #OdooDevelopment #Integration