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

The form views


As we have seen in previous chapters, form views can either follow a simple layout or a business document layout, similar to a paper document.

We will now see how to design these business document views and how to use the elements and widgets available. We would normally do this by inheriting and extending the todo_app views. But, for the sake of clarity, we will instead create completely new views to override the original ones.

Dealing with several views of the same type

The same Model can have several Views of the same type, by default the view with the lowest Priority value, but an Action can set a specific view to be used, through its XML ID. Using this, we can have two different menu items opening the same model but use different views. This is achieved using the  view_id attribute of the Window Action, with the XML ID of the view to use. For example, in the todo_app.action_todo_task Action, we could add to it the view_id="view_form_todo_task_ui" attribute.

To add a new View...