Book Image

Odoo 11 Development Essentials - Third Edition

By : Daniel Reis
Book Image

Odoo 11 Development Essentials - Third Edition

By: Daniel Reis

Overview of this book

Odoo continues to gain worldwide momentum as the best platform for open source ERP installations. Now, with Odoo 11, you have access to an improved GUI, performance optimization, integrated in-app purchase features, and a fast-growing community to help transform and modernize your business. With this practical guide, you will cover all the new features that Odoo 11 has to offer to build and customize business applications, focusing on the publicly available community edition. We begin with setting up a development environment, and as you make your way through the chapters, you will learn to build feature-rich business applications. With the aim of jump-starting your Odoo proficiency level, from no specific knowledge to application development readiness, you will develop your first Odoo application. We then move on to topics such as models and views, and understand how to use server APIs to add business logic, helping to lay a solid foundation for advanced topics. The book concludes with Odoo interactions and how to use the Odoo API from other programs, all of which will enable you to efficiently integrate applications with other external systems.
Table of Contents (20 chapters)
Title Page
Packt Upsell
Contributors
Preface
Index

Inheritance on Kanban views


The templates used in Kanban views and reports are extended using the regular techniques used for other views, for example using XPath expressions. See Chapter 3, Inheritance – Extending Existing Applications, for more details.

A common case is to use the <field> elements as selectors, then add other elements before or after them. In the case of Kanban views, the same field can be declared more than once, for example, once before the templates, and again inside the templates. Here, the selector will match the first field element and won't add our modification inside the template as intended.

To work around this, we need to use XPath expressions to make sure that the field inside the template is the one matched. For example:

<record id="res_partner_kanban_inherit" model="ir.ui.view"> 
  <field name="name">Contact Kanban modification</field> 
  <field name="model">res.partner</field> 
  <field name="inherit_id" ref="base.res_partner_kanban_view...