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

Dynamic views


View elements also support a few dynamic attributes that allow views to dynamically change their appearance or behavior depending on field values. We may have on change events, able change values on other fields while editing data on a form, or have fields be mandatory or visible only when certain conditions are met.

On change events

The on change mechanism allows us to change values in other form fields when a particular field is changed. For example, the on change on a Product field can set the Price field to a default value whenever the product is changed.

In older versions, the on change events were defined at the view level, but since Version 8.0 they have been defined directly on the Model layer, without the need for any specific markup on the views. This is done by creating methods to perform the calculations, and by using @api.onchange('field1', 'field2') to bind it to fields. The on change methods are discussed in more detail in Chapter 6, The ORM API – Handling Application...