summaryrefslogtreecommitdiff
path: root/addons/uom/data
AgeCommit message (Collapse)Author
2018-04-09[IMP] uom: unique reference UoM per categoryjem-odoo
Users can configure multiple references in a same category. This might cause problems during conversion and does not make sense. Since this is a "late" constraint, we define it in python to avoid conflict with existing data. We allow user to have multiple unactive reference, but force to have exactly one active. So when a new UoM category is created, user have to encode the reference unit first, and then the bigger/smaller ones. This commit also update stock tests, since they were redefining new reference UoM in the same category, and finally, this commit provides some tests for this uniqueness and custom UoM behavior. Task #1820076
2018-04-09[IMP] uom: measurement type on categoryjem-odoo
In order to restrict some uom field to some uom category, it is required to add a measurement type on uom.category. Also, this will lessen the use of master data. Some technical justifications: - measure_type is not required, to allow people creating their own uom.category. Those ones will not interfere with addons business. - measure_type is unique: we restrict to only one category containing time, weight, ... in order to avoid mismatch category during conversion. (2 different weight categories can not be converted). - measure_type on uom.uom is stored: to allow search and domain on field, we need to store it. Usually, UoM are not updated every day, and the number of uom in a database is not that important. To illustrate this mecanism, a domain is added on 'project_time_mode_id', in project module. This field is use as timesheet default uom, and we obviously want to restrict it to time category (timesheeting in liter does not make sense ...) Task #1820076
2018-02-26[IMP] product: rename product.uom into uom.uomXavierDo
Also rename product.uom.categ into uom.category to give it a decent name.
2018-02-26[IMP] product: move uom in a new addonXavierDo
Moves UoM models, test and data to a new addon in order to be able to use uom without product. A simple example is be to be able to use UoM for timesheets. This commit only move code, and adapt xml ids without chaging any feature or functionnal behavior. Note: 'product' module now depends on new 'uom' module.