summaryrefslogtreecommitdiff
path: root/addons/web/static/src/xml
diff options
context:
space:
mode:
authorDenis Ledoux <dle@odoo.com>2016-05-25 14:32:49 +0200
committerDenis Ledoux <dle@odoo.com>2016-05-25 14:42:24 +0200
commitaedd0251b2ddfd0460ec1eb0502f443ca3430aca (patch)
treeb0ca3946f147e3f31b5b90dd2701f8b80ad6e42b /addons/web/static/src/xml
parentbd9fc14659bc948c751ad95ae98034d8494242be (diff)
[FIX] account: invoice onchange partner accounts properties
Since revision 7eab8e26d3d46c53f4be924d6a34e80a66e74960 the `_onchange_partner_id` of `account.invoice` failed if the SUPERUSER created an invoice for another company than his own, and if the partner had not a specific receivable or payable account (meaning the default accounts are used, the accounts coming from the properties of this company without any partner specified) because ``` prop.search([ ('name', '=', 'property_account_receivable_id'), ('company_id', '=', company_id) ])` ``` can return multiple records, if several partners have their own receivable accounts set, and, since the above revision, `get_by_record` specify `ensure_one`, meaning you cannot pass multiple records to this method. This domain was built a the time (2009, rev. 80861660c6fd598c29b3cf6bb044490f2b1feec9) to handle the multi-company property, which can now be handle with a simple `force_company` passed in the context. It was not the case at the time. This revision could be applied in former releases, but this is not a necessity. This is a necessity in saas-10, because of the above revision. opw-678536
Diffstat (limited to 'addons/web/static/src/xml')
0 files changed, 0 insertions, 0 deletions