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

Calendar views


As the name suggests, this view type presents the records in a calendar that can be viewed at different periods of time: per month, week, or day. A calendar view for the To-Do Tasks could look like this:

<record id="view_calendar_todo_task" model="ir.ui.view"> 
  <field name="model">todo.task</field> 
  <field name="arch" type="xml"> 
    <calendar date_start="date_deadline" color="user_id"> 
      <!-- Fields used for the display text --> 
      <field name="name" /> 
      <field name="stage_id" /> 
    </calendar> 
  </field> 
</record> 

The calendar attributes are:

  • date_start is the field for the start date. Mandatory.
  • date_end is the field for the end date. Optional.
  • date_delay is the field with the duration of days, which can be used instead of date_end.
  • all_day provides the name of a Boolean field that is to be used to signal full day events. In these events, the duration is ignored.
  • color is the field used...