Best practices as to when to use fields.selection vs fields.many2one

Odoo is the world's easiest all-in-one management software.
It includes hundreds of business apps:

CRM
e-Commerce
Kirjanpito
Varastointi
PoS
Project
MRP

All apps

Kaikki kirjoitukset Ihmiset Merkit

Tunnisteet (Näytä kaikki)

odoo accounting v14 pos v15

Tietoa tästä foorumista

Apua

Best practices as to when to use fields.selection vs fields.many2one

orm model fields.many2one design

1 Vastaa

7012 Näkymät

john5000

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.

Jérémy Kersten (jke)

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

john5000

Tekijä

Thank you jke, that is simple and makes sense.

Ivan

Paras vastaus

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.

Nautitko keskustelusta? Älä vain lue, vaan osallistu!

Luo tili jo tänään nauttiaksesi yksinoikeusominaisuuksista ja osallistuaksesi mahtavaan yhteisöömme!

Rekisteröidy

Aiheeseen liittyviä artikkeleita	Vastaukset	Näkymät
How i can verify record then save in Odoo 12? orm model	0 syysk. 19	3467
Get model data in a controller Ratkaistu orm model controller	4 lokak. 21	37637
How do I dump all the fields and values in a model (ideally including those from relationships)? Ratkaistu development orm model	1 lokak. 20	12556
Usage of ORM methods and ORM API documentation? database orm model	1 maalisk. 15	5039
why res.config model in odoo is TransientModel not Model ? wizard orm model TransientModel	1 elok. 25	3807

Tämä kysymys on merkitty

Nautitko keskustelusta? Älä vain lue, vaan osallistu!