Odoo is the world's easiest all-in-one management software. It includes hundreds of business apps:
CRM | e-Commerce | Accounting | Inventory | PoS | Project management | MRP | etc.
I've seen a model that has a status or state field which is done as fields.selection() and I've seen it done as a fields.many2one(). Both ways of doing it seem to work fine and do the job.
I suppose many2one is best when you expect to have new values to add over time.
I am wondering if there are any best practices as to which should be used under what cirmustances. And what are the advantages and disavantages of each. Or any notable experince in using one or the other.
I wouldn't say that this is best practices, but here are some "differences" that would be your consideration points when making the design decision:
- selection is a fixed list once rendered (this also applies to many2one fields which is viewed with widget="selection"), you cannot apply domain to it
- selection will be pulled altogether at once when HTML is rendered (this also applies to many2one fields which is viewed with widget="selection"). Not a good choice if you have hundreds or thousands selection.
- selection fields (this does NOT apply to many2one fields viewed with widget="selection") is not stored as a Foreign Key. So you can remove an entry from the selection and no integrity problem will ensue.
As for the states, you can still make it a selection field whilst making it dynamic by supplying the entries from a table. Selection field can accept a function as selection source.
About This Community
This platform is for beginners and experts willing to share their Odoo knowledge. It's not a forum to discuss ideas, but a knowledge base of questions and their answers.Register
Odoo Training Center
Access to our E-learning platform and experience all Odoo Apps through learning videos, exercises and Quizz.Test it now
|Asked: 12/1/14, 1:54 PM|
|Seen: 1089 times|
|Last updated: 3/16/15, 8:10 AM|