Daily updates from Odoo
Tuesday, June 12, 2018
10 changes · master
New functionality added to Odoo
Sales invoicing can now be customized so related sales orders are grouped into invoices using additional business rules when needed. The change also allows new invoices to be combined with existing draft invoices, helping reduce duplicate invoice drafts and support more tailored billing workflows.
Original PR description
Description of the issue/feature this PR addresses: This PR allows to add flexibility to the logic to group sales orders when the invoice is created. - With the new method '_get_invoice_group_key'…
Description of the issue/feature this PR addresses: This PR allows to add flexibility to the logic to group sales orders when the invoice is created. - With the new method '_get_invoice_group_key' other modules can change the key fields that will be used to group sales orders into a single invoice. - With the new method '_get_draft_invoices' other modules can change this method in order to merge new invoices with existing draft ones. Even the code was changed a bit, the logic of this method is 100% respected. Current behavior before PR: - Only fields invoice_partner_id and currency_id are being considered as the grouping key. - No draft invoice is considered when creating new invoices. Desired behavior after PR is merged: - The grouping key can be extended by other modules, if needed. - New invoices can be merged to existing draft ones automatically when creating them. @etobella @jbeficent @mreficent -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
The stock module now asks the database for only the first matching warehouse instead of retrieving all matches and filtering them later. This reduces unnecessary work and can improve performance in operations that need warehouse information.
Original PR description
- Description of the issue/feature this PR addresses: This PR increase the performance to `get_warehouse` method. Other matter, IMHO this method should be in a `fields.function` with stored like as [commercial_partner_id](https://github.com/odoo/odoo/blob/a5df5e8/openerp/addons/base/res/res_partner.py#L270) Because waste many resources in each invoke. But I added this PR with a small fix. - Current behavior before PR: Return all items from database and filter after by python. - Desired behavior after PR is merged: Return first item from database.
This change adds a cleaner way to prepare information when converting leads into contacts or companies. It helps future CRM customizations handle lead-to-contact conversion more reliably without changing the normal user workflow.
Original PR description
Relaunch https://github.com/odoo/odoo/pull/8899 to master. I think I broke that PR somehow when rebasing.
Resolved issues and error corrections
Stock receipts now show the destination location, while delivery orders show the source location. This makes warehouse documents clearer and helps users verify where goods are coming from or going to at a glance.
Original PR description
Description of the issue/feature this PR addresses:
issue: https://www.odoo.com/web?#id=1853350&action=333&active_id=1278&model=project.task&view_type=form&menu_id=4720
pad: https://pad.odoo.com/p/r.040c408a0dd3d8fb644482752f9228b9
Current behavior before PR:
- In current picking receipts show the source location and
picking delivery show the destination location
Desired behavior after PR is merged:
- In picking receipts show the destinaion(https://goo.gl/TPNgqZ) and
- picking delivery show the source location(https://goo.gl/HnBfNw)
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prThis change makes the account move line form match the existing list view behavior by removing the easy create option. It helps prevent users from accidentally creating accounting entries from a place where creation was not intended.
Original PR description
Description of the issue/feature this PR addresses: The `view_move_line_tree` view in `account` module has `create=false`. But the `view_move_line_form` view doesn't have this clause. This is an inconsistency, as the user in the tree view can click on a record to go to the form view and then click on the create button. Current behavior before PR: You can create easily new account move lines from the form view. Desired behavior after PR is merged: You can't create easily account move lines from the form view. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes misleading help text for product volume so it matches Odoo’s standard use of liters instead of cubic meters. Users will see clearer, consistent unit guidance when entering or reviewing product volume information.
Original PR description
Description of the issue/feature this PR addresses: The helper of the field volume is not good. it says that the volume is expressed in m3. but in the rest of odoo, the default volume uom is in Liter. See for exemple : https://github.com/odoo/odoo/blob/master/addons/product/data/product_data.xml#L115 Current behavior before PR: confusing for the user. Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update cleans up duplicate logic in the messaging component. It reduces unnecessary checks and helps keep message handling easier to maintain without changing expected user-facing behavior.
Original PR description
Two identical conditions in L288 and L290 The condition needs to be removed L332. Description of the issue/feature this PR addresses: Current behavior before PR: Desired behavior after PR is merged: -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
The barcode field on customer and contact records is now available as part of the core base setup instead of requiring the Point of Sale module. This removes an unnecessary dependency and lets businesses manage partner barcodes without installing extra functionality they may not use.
Original PR description
**Description of the issue/feature this PR addresses:** Ref : https://github.com/odoo/odoo/issues/13544 **Current behavior before PR:** point_of_sale module is required to use the field ```barcode``` (```res.partner``` model) defined in base. **Desired behavior after PR is merged:** installing base allow user to fill this field. CC : @Yenthe666, @bealdav, @mart-e, @pedrobaeza -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Code cleanup and technical improvements
This update modernizes how company, contact, user, and CRM forms react when a state or region is selected. It reduces fragile workarounds in the system, making these forms easier to maintain and less likely to break during future updates.
Original PR description
This method leads to ugly hacks as [this one](https://github.com/Yajo/l10n-germany/commit/599221635f5f091954efed54ab44d53a90517852#diff-cb32caaa5c33bbc0caf735a300e39703R69), mangling with context, to make it compatible with new api ochanges. Let's just update it.
Documentation and clarification updates
Eric Lembregts has been added to the DynApps NV corporate CLA and also has a personal CLA record. This keeps contributor legal documentation up to date and confirms contribution permissions are properly recorded.
Original PR description
Description of the issue/feature this PR addresses: Adding Eric Lembregts to DynApps NV CLA in master. Current behavior before PR: Eric Lembregts is missing from DynApps NV CLA in master. Desired behavior after PR is merged: Added Eric Lembregts to DynApps NV CLA in master. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr