Daily updates from Odoo
Tuesday, August 21, 2018
8 changes · master
New functionality added to Odoo
This update adds a complete set of Chinese city records to the China localization module. Businesses using Odoo in China will have more accurate and comprehensive city data available for addresses, localization, and related workflows.
Original PR description
Description of the issue/feature this PR addresses: add all china city data 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
Enhancements to existing features
Project tasks can now show the main company or customer associated with a contact. This makes it easier for teams to filter and group tasks to get a unified view of work for the same customer, even when tasks are assigned to individual contacts.
Original PR description
Before this commit, in the case where tasks where assigned to contacts, it was very cumbersome to get a unified view of one customer. Now, commercial partner is set as a task column and as such available on filters and groupings. Note: This is a basic step towards such feature, maybe UX needs to be tweaked further. (eg. hide commercial partner field if it doesn't differ from partner - not sure how to implement that properly) It's probably just a first step in the right direction... -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Custom models can now use an active status so records can be archived and filtered consistently in the web interface. This helps businesses manage custom data without losing records, while keeping inactive items out of day-to-day views.
Original PR description
Towards solving #26162 This PR does not include: - ~Necessary changes to WebClient~ (ed865af1610) - Necessary changes to Studio - Safeguards on UX (`x_active` can only be Boolean) - Tests One alternative implementation: - Add `active` as a base model field. Similar to what the chatter field checkbox does. - But: Side effects of being a `base` field with no underlying python code?? -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Traceability reports are now available for manufacturing orders even when the finished product is not individually tracked, making it easier to follow component and production history. The update also improves report accuracy, clearer clickable links, and replaces lot-related sales and purchase lists with easier navigation buttons.
Original PR description
Task: https://www.odoo.com/web#id=1873101&model=project.task&view_type=form&menu_id=
The generic tax report now includes a dedicated Tax Adjustment section alongside Sales and Purchases. This makes tax adjustments easier to identify and review in financial reporting, supporting clearer compliance and accounting workflows.
Original PR description
Task : https://www.odoo.com/web#id=38076&view_type=form&model=project.task&action=327&menu_id=4720 Pad : https://pad.odoo.com/p/r.713cb06bbfa13a95a32983e4a7b37bd6 Description of the issue/feature this PR addresses: On the generic tax report, create a section "Tax Adjustment" (same level than Sales and Purchases sections) Current behavior before PR: On the generic tax report, there is no "Tax Adjustment" (same level than Sales and Purchases sections) Desired behavior after PR is merged: On the generic tax report, create a section "Tax Adjustment" (same level than Sales and Purchases sections)
Resolved issues and error corrections
Voucher-generated accounting entries now retain the selected product and quantity, matching the behavior users expect from invoices. This helps businesses analyze costs and revenues by product when vouchers are used for smaller expenses or similar transactions.
Original PR description
- [x] Test failure unrelated - [x] Manual QA locally, can only be validated on an ee runbot (eg. by group journal entries by product) Possibly as an oversight, before this commit, product_id was not…
- [x] Test failure unrelated - [x] Manual QA locally, can only be validated on an ee runbot (eg. by group journal entries by product) Possibly as an oversight, before this commit, product_id was not passed to the aml on account vouchers. This caused inexpected behaviour, if products are a relevant dimension in cost or revenue analysis analysis: Whereas on invoices, this product is copied to aml on voucher, it is not. Now products are copied to the amls thereby enabling this reporting dimension. This is especially usefull for people who use vouchers for minor expenses, but need some additional visibility to what general or analytic accounts provide. **Description of the issue/feature this PR addresses:** - Products are not available on voucher generated amls - This is a missing analytic dimension as compared to normal invoices **Current behavior before PR:** - Products are not copied on vouchers **Desired behavior after PR is merged:** - As vouchers permit to choose a product - Users expects information not to be lost on aml as compared to similar behavior on invoices. **Note:** Please do not close, even if not immediately accepted (`wishlist` tag). This PR is meant to be carried along and actively maintained, until this semantic will be completed this way or another. -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr @xoe-labs
This fixes an error that prevented companies from installing the Mexican chart of accounts. The correction restores the expected setup flow for Mexican accounting localization, helping users complete configuration without a crash.
Original PR description
The name of **_prepare_transfer_account** method was changed by **_prepare_transfer_account_for_direct_creation**…
The name of **_prepare_transfer_account** method was changed by **_prepare_transfer_account_for_direct_creation** [here](https://github.com/odoo/odoo/commit/87f0d2eefb77bfc6a9a0fa7f7dcd1475c7c34639#diff-ce53c5491cb2c9ab3dbbd41ecabf594f)
But, I think by mistake was changed the name of **_prepare_transfer_account** method by **_get_default_banck_journals_data** and that it's wrong and occurs the following error when I try install **l10n_mx** module:
``` python
File "/.repo_requirements/odoo/odoo/tools/convert.py", line 750, in parse
self._tags[rec.tag](rec, de, mode=mode)
File "/.repo_requirements/odoo/odoo/tools/convert.py", line 342, in _tag_function
_eval_xml(self, rec, env)
File "/.repo_requirements/odoo/odoo/tools/convert.py", line 193, in _eval_xml
return odoo.api.call_kw(model, method, args, {})
File "/.repo_requirements/odoo/odoo/api.py", line 749, in call_kw
return _call_kw_multi(method, model, args, kwargs)
File "/.repo_requirements/odoo/odoo/api.py", line 736, in _call_kw_multi
result = method(recs, *args, **kwargs)
File "<decorator-gen-174>", line 2, in try_loading_for_current_company
File "/.repo_requirements/odoo/odoo/api.py", line 372, in loop
result = [method(rec, *args, **kwargs) for rec in self]
File "/.repo_requirements/odoo/odoo/api.py", line 372, in <listcomp>
result = [method(rec, *args, **kwargs) for rec in self]
File "/home/odoo/odoo-master/addons/account/models/chart_template.py", line 170, in try_loading_for_current_company
self.load_for_current_company(15.0, 15.0)
File "/home/odoo/enterprise/account_reports/models/chart_template.py", line 9, in load_for_current_company
res = super(AccountChartTemplate, self).load_for_current_company(sale_tax_rate, purchase_tax_rate)
File "/home/odoo/odoo-master/addons/account/models/chart_template.py", line 240, in load_for_current_company
self._create_bank_journals(company, acc_template_ref)
File "/home/odoo/odoo-master/addons/payment/models/chart_template.py", line 11, in _create_bank_journals
res = super(AccountChartTemplate, self)._create_bank_journals(company, acc_template_ref)
File "/home/odoo/odoo-master/addons/account/models/chart_template.py", line 311, in _create_bank_journals
for acc in self._get_default_bank_journals_data():
File "/home/odoo/odoo-master/addons/account/models/chart_template.py", line 311, in _create_bank_journals
for acc in self._get_default_bank_journals_data():
File "/usr/lib/python3.5/bdb.py", line 48, in trace_dispatch
return self.dispatch_line(frame)
File "/usr/lib/python3.5/bdb.py", line 67, in dispatch_line
if self.quitting: raise BdbQuit
odoo.tools.convert.ParseError: "" while parsing /home/odoo/odoo-master/addons/l10n_mx/data/account_chart_template_data.xml:4, near
<function model="account.chart.template" name="try_loading_for_current_company">
<value eval="[ref('l10n_mx.mx_coa')]"/>
</function>
2018-08-17 17:26:25,632 3917 INFO test odoo.service.server: Initiating shutdown
2018-08-17 17:26:25,633 3917 INFO test odoo.service.server: Hit CTRL-C again or send a second signal to force the shutdown.
```:
--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-prPurchase orders created from purchase agreements now handle vendor names according to the agreement type. Blanket orders keep the agreed vendor locked, while calls for tender allow users to choose or change the vendor during the request-for-quotation stage.
Original PR description
…se agreements. Task link : https://www.odoo.com/web?debug#id=1866975&action=327&model=project.task&view_type=form&menu_id=4720 Pad link : https://pad.odoo.com/p/r.42624a44d71b668ebc959b5243a9f646 This commit is related to task ID 1866975. 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