Daily updates from Odoo
Thursday, August 16, 2018
7 changes
Enhancements to existing features
Payroll salary rules are now displayed and processed according to their configured sequence instead of their database ID. This makes payslip results easier to predict, review, and troubleshoot when rule order affects calculations.
Original PR description
The most important part of building salary rules is having them in the right sequence. If the salary rules are not order by this field, it's very hard to debug or realize that a salary is not working because is not before (or after) another. This also makes it easier to know how the payslip will show the order of the salary rules. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
CSV and file imports can now optionally create missing linked records for fields such as tags or company names. This reduces import failures and manual cleanup when simple related records do not already exist.
Original PR description
purpose: useful for tags, company names of contacts, where is just one or two fields model before this commit, record not creating if it is not found, when we import csv or valid file after this commit, added an option in the column header "Create if doesn't exist" create a new record if user have check that option on the particular m2m/m2o fields Task:https://www.odoo.com/web#id=1850633&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.b72a1af4d6e1e97ce1eb445073551e12 -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The Point of Sale details report can now use the appropriate selected company instead of always showing the current user's company. This improves reporting accuracy for businesses operating across multiple companies.
Original PR description
**Description of the issue this PR addresses:** This PR adresses the `pos_details` report in `master` branch. The company of the report should be customizable. **Current behavior before PR:** The `pos_details` report always shows the company of the user. **Desired behavior after PR is merged:** This PR fix the report adding the multicompany support. EDIT: Later, I think it's an improvement instead of a fix. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo's report barcode generation is updated to support a wider range of barcode types and customization options through the Elaphe library. This helps businesses create formats such as Data Matrix, Aztec, and Pharmacode without relying on Reportlab limitations, while preserving existing behavior.
Original PR description
Description of the issue/feature this PR addresses: There is a framework to generate barcode, useful in many cases, e.g. if I want to generate Aztec/DataMatrix/Pharmacode barcode or many other types,…
Description of the issue/feature this PR addresses: There is a framework to generate barcode, useful in many cases, e.g. if I want to generate Aztec/DataMatrix/Pharmacode barcode or many other types, I have these options in the elaphe library to use. The elaphe is a python binding of Barcode Writer In Pure PostScript. This framework provides a lot of settings to customize and create a barcode, just passing this information as options in the generating method. Current behaviour before PR: The current barcode generating method in Odoo uses the Reportlab and if I want to generate a Data Matrix code I need to update the Reportlab library to 3.3.0 version, but if I want to change the version/format I can't because it doesn't provide these options. This is only one of much more examples that we can find. Desired behaviour after PR is merged: Keep the current behaviour only adding more settings and options of barcode types, initially. ## I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Odoo can now define default units of measure per language, helping records use units that match a user's locale. This reduces manual selection and supports more region-appropriate defaults for fields such as time or quantity units.
Original PR description
**Description of the issue/feature this PR addresses:**
Adds a concept of a default unit of measure on languages, unique by unit category type.
It also provides a method that can be used in fields to work from said defaults.
**Configuration:**
Set default unit of measures in the `Languages` menu in settings.
**Usage:**
Fields that want to implement the language default should use the provided method, such as in the below example:
```python
class MyModel(models.Model):
_name = 'my.model'
time_uom_id = fields.Many2one(
string='Time Units',
comodel_name='product.uom',
default=lambda s: s.env['res.lang'].default_uom_by_category('Time'),
)
```
**Alternatively:**
If you would prefer the feature be its own module, I can just bring [this](https://github.com/OCA/server-tools/tree/10.0/base_locale_uom_default) over instead.
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prOdoo now keeps track of the original wording of database constraints so it can tell when they have truly changed. This prevents module updates from repeatedly dropping and recreating unchanged constraints, reducing update time and disruption on large databases.
Original PR description
Store the original constraint definition as a comment on the constraint and use it to determine if the constraint definition was changed. This prevents endless re-adding of constraints that are reformatted by postgresql in an unrecognizable way (in which e.g. "CHECK (credit*debit=0)" becomes "CHECK ((credit * debit) = 0::numeric)") Description of the issue/feature this PR addresses: Existing SQL constraints are not properly recognized on module update Current behavior before PR: An update of the account module drops and re-adds _sql_constraints such as those on move and move line balance which can take a long time on large databases. Desired behavior after PR is merged: If the constraint definition is not modified, the constraint is not dropped and re-added -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Project and issue teams can now archive columns instead of keeping every workflow stage visible. This helps teams clean up old or unused stages while preserving their history and reducing clutter in day-to-day task boards.
Original PR description
Task: https://www.odoo.com/web#id=22007&view_type=form&model=project.task&action=333&active_id=248&menu_id=4720