Daily updates from Odoo
Wednesday, February 13, 2019
7 changes · master
Enhancements to existing features
This change lets teams identify customers who have placed orders through Point of Sale. It supports business uses such as e-marketing campaigns targeted at customers who bought in store.
Original PR description
Task: https://www.odoo.com/web?#id=1931528&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720 Pad: https://pad.odoo.com/p/r.4ff63496524687424bb440af0e2c53cc 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
When duplicate customer records are merged, their loyalty points are now added together instead of risking points being left behind. This helps keep customer rewards accurate and avoids manual corrections for loyalty balances.
Original PR description
Task link = https://www.odoo.com/web#id=1869488&action=327&model=project.task&view_type=form&menu_id=4720
This update removes direct references to a session identifier from the timesheet synchronization code. It helps align the enterprise app with broader platform changes, reducing internal coupling while keeping user-facing behavior unchanged.
Original PR description
See odoo/odoo#30098
Resolved issues and error corrections
This change restores and updates automated checks for the website editor after recent editor updates. It helps ensure website editing and style customization continue to be validated reliably, reducing the risk of regressions reaching users.
Original PR description
This reverts commit ba0fe3437f79577d9934eeee151f67c1bfaf3a8d, as this should be ok with recent forward-port.
Expense reports now automatically use the same payment mode choices as individual expenses. This prevents missing or inconsistent options when new payment methods are added, making expense handling more reliable.
Original PR description
Description of the issue/feature this PR addresses The field payment mode in the expense sheet is related to the same the field in the expense, but this must be consistent, and if a new option is added in the expense must be considered in the sheet. In Odoo v11 > is not necessary indicate the selection parameter in the field definition. Current behavior before PR: If is added a new option in the hr.expense thas is not considered on the sheet Desired behavior after PR is merged: Make consistent both models -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Timesheet records imported before an employee had a linked user will now be updated once that user is assigned. This keeps employee timesheet data aligned automatically and avoids manual corrections after imports.
Original PR description
Description of the issue/feature this PR addresses: When employee entry has no user set in "Related User" field for any reason, and timesheet entries are imported, `user_id` field of a `account.analytic.line` will never be updated if "Related User" is set after the import. Steps to reproduce 1. Create `hr.employee` w/o "Related User" 2. Create `account.analytic.line` (as Timesheet entry) for created employee 3. Create `res.users` 4. Set created user as "Related User" of previously-created employee Current behavior before PR: `user_id` field of `account.analytic.line` won't get updated Desired behavior after PR is merged: `user_id` field of `account.analytic.line` will get updated -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This update removes an outdated compatibility reference from the Mexican tax cash basis test code. It helps keep the module aligned with current platform standards and prevents a test import error during validation.
Original PR description
Fixes: ``` File "/home/odoo/enterprise/l10n_mx_tax_cash_basis/tests/test_account_tax_cash_basis.py", line 8, in <module> from odoo.tools.pycompat import izip ```