Exposing Related fields stored in other models
by Daniel Reis, Alexandre Fayolle, Holger Brunn
Odoo Development Cookbook
- 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 reading data from the server, Odoo clients can only get values for the fields available in the model being queried. Client-side code can't use dot notation to access data in the related tables like server-side code can.
But those fields can be made available there by adding them as related fields. We will do this to make the publisher's city available in the Library Book model.
We will reuse the my_module addon module from Chapter 3, Create Odoo Modules.
Edit the models/library_book.py file to add the new "related" field:
- Make sure that we have a field for the book Publisher:
class LibraryBook(models.Model): # ... publisher_id = fields.Many2one( 'res.partner', string='Publisher') - Now, add the related field for the Publisher's city:
# class LibraryBook(models.Model): # ... publisher_city = fields.Char( 'Publisher City', related='publisher_id.city')
Finally, we need to upgrade the addon module for the new fields to be available in the Model.
Related fields are just like regular fields, but they have the additional attribute, related, with a string for the separated chain of fields to traverse.
In our case, we access the Publisher related record through publisher_id, and then read its city field. We can also have longer chains, such as publisher_id.country_id.country_code.
Related fields are in fact computed fields. They just provide a convenient shortcut syntax to read field values from related models. As a computed field, this means that the store attribute is also available to them. As a shortcut, they also have all the attributes from the referenced field, such as name, translatable, required, and so on.
Additionally, they support a related_sudo flag similar to compute_sudo; when set to True, the field chain is traversed without checking user access rights.
-
No Comment