Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:
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:
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.
Tạo tài khoản ngay hôm nay để tận hưởng các tính năng độc đáo và tham gia cộng đồng tuyệt vời của chúng tôi!
Đăng ký| Bài viết liên quan | Trả lời | Lượt xem | Hoạt động | |
|---|---|---|---|---|
|
0
thg 9 19
|
3469 | ||
|
Get model data in a controller
Đã xử lý
|
|
4
thg 10 21
|
37637 | |
|
1
thg 10 20
|
12557 | ||
|
1
thg 3 15
|
5041 | ||
|
1
thg 8 25
|
3808 |
1. Use the live chat to ask your questions.
2. The operator answers within a few minutes.
Hello Best practice according to me is to use : many2one : for relations with another object (wich can be edited... add choice, ...) Eg: Category, manager, ... Selection : A static list (not evolutive). Eg: Status (Open / WIP / Close) JKE
Thank you jke, that is simple and makes sense.