- Odoo Development Cookbook
- Table of Contents
- Odoo Development Cookbook
- Credits
- About the Authors
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Installing the Odoo Development Environment
- 2. Managing Odoo Server Instances
- 3. Creating Odoo Modules
- 4. Application Models
- Introduction
- Defining the Model representation and order
- Adding data fields to a model
- Using a float field with configurable precision
- Adding a monetary field to a Model
- Adding relational fields to a Model
- Adding a hierarchy to a Model
- Adding constraint validations to a Model
- Adding computed fields to a Model
- Exposing Related fields stored in other models
- Adding dynamic relations using Reference fields
- Adding features to a Model using inheritance
- Using Abstract Models for reusable Model features
- Using Delegation inheritance to copy features to another Model
- 5. Basic Server Side Development
- Introduction
- Defining model methods and use the API decorators
- Reporting errors to the user
- Obtaining an empty recordset for a different model
- Creating new records
- Updating values of recordset records
- Searching for records
- Combining recordsets
- Filtering recordsets
- Traversing recordset relations
- Extending the business logic defined in a Model
- Extending write() and create()
- Customizing how records are searched
- 6. Advanced Server Side Development Techniques
- 7. Debugging and Automated Testing
- Introduction
- Producing server logs to help debug methods
- Using the Odoo shell to interactively call methods
- Using the Python debugger to trace method execution
- Writing tests for your module using YAML
- Writing tests for your module using Python unit tests
- Running server tests
- Using the Odoo Community Association maintainer quality tools
- 8. Backend Views
- Introduction
- Adding a menu item and window action
- Having an action open a specific view
- Adding content and widgets to a form view
- Adding buttons to forms
- Passing parameters to forms and actions: Context
- Defining filters on record lists: Domain
- List views
- Search views
- Changing existing views: View inheritance
- Document-style forms
- Dynamic form elements using attrs
- Embedded views
- Kanban views
- Show kanban cards in columns according to their state
- Calendar views
- Graph and pivot views
- QWeb reports
- 9. Module Data
- 10. Access Security
- 11. Internationalization
- 12. Automation and Workflows
- 13. Web Server Development
- 14. CMS Website Development
- 15. Web Client Development
- 16. Server Deployment
- Index
When you show a one2many or a many2many field on a form, you don't have much control over how it is rendered up to now if you haven't used one of the specialized widgets. Also, in the case of many2one fields, it is desirable sometimes to be able to influence the way the linked record is opened. In this recipe, we'll look into how to define private views for those fields.
- Define your field as usual, but don't close the tag:
<field name="child_ids">
- Simply write the view definition(s) into the tag:
<tree> <field name="name" /> <field name="email" /> <field name="phone" /> </tree> <form> <group> <field name="name" /> <field name="function" /> </group> </form> - Close the tag:
</field>
When Odoo loads a form, it first checks for reference fields if there are views embedded as outlined previously. Those embedded views can have the exact same elements as views we defined before. Only if Odoo doesn't find an embedded view of some type, does it use the model's default view of this type.
While embedded views seem like a great feature in the first place, they complicate view inheritance a lot. For example, as soon as embedded views are involved, the field names are not guaranteed to be unique and you'll usually have to use some quite elaborate XPaths to select elements within an embedded view.
So, in general, you should better served defining the standalone views and use the keys form_view_ref and tree_view_ref described earlier.
-
No Comment