Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Odoo 12 Development Essentials
  • Table Of Contents Toc
  • Feedback & Rating feedback
Odoo 12 Development Essentials

Odoo 12 Development Essentials

By : Daniel Reis
4.4 (5)
close
close
Odoo 12 Development Essentials

Odoo 12 Development Essentials

4.4 (5)
By: Daniel Reis

Overview of this book

Odoo is one of the best platforms for open source ERP and CRM. Its latest version, Odoo 12, brings with it new features and updates in Python packages to develop more customizable applications with additional cloud capabilities. The book begins by covering the development essentials for building business applications. You will start your journey by learning how to install and configure Odoo, and then transition from having no specific knowledge of Odoo to being ready for application development. You will develop your first Odoo application and understand topics such as models and views. Odoo 12 Development Essentials will also guide you in using server APIs to add business logic, helping you lay a solid foundation for advanced topics. As you progress through the chapters, you will be equipped to build and customize your applications and explore the new features in Odoo 12, such as cloud integration, to scale your business applications. You will get insights into building business logic and integrating various APIs into your application. By the end of the book, you will be able to build a business application from scratch by using the latest version of Odoo.
Table of Contents (17 chapters)
close
close

Chapter 4

  1. How do we extend an existing Model to add a mixin, such as mail.thread?

Both in-place classic extension and mixin prototype inheritance use the same _inherit Model attribute. For example, to extend x and add the y mixin, we should have the _name='x' model attribute and the _inherit = ['x', 'y'] Model attribute.

  1. What changes are needed to also have the phone field available in the member form view?

No model changes are needed, since a phone field exists in partners, and delegation inheritance makes all partner fields also available on the member Model. We only need to add the field to the form view, for example, next to the email field: <field name=phone" />.

  1. What happens if you create a Model class with name attribute different form the inherit attribute (for example, _name='y' and _inherit='x')?
  2. ...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech

Create a Note

Modal Close icon
You need to login to use this feature.
notes
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Delete Note

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete

Edit Note

Modal Close icon
Write a note (max 255 characters)
Cancel
Update Note

Confirmation

Modal Close icon
claim successful

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY