Thursday, July 11, 2024
6 changes · 17.0
Resolved issues and error corrections
This change prevents an error from interrupting analytic account processing in stock accounting. It helps ensure related accounting operations can complete reliably without unexpected failures.
Original PR description
This fixes the syntax error on function _perform_analytic_distribution of the model AccountAnalyticAccount. opw-3907439 Description of the issue/feature this PR addresses and current behavior before PR: - The _perform_analytic_distribution function on model AccountAnalyticAccount has a syntax error causing a UnboundLocalError Desired behavior after PR is merged: - No UnboundLocalError --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Printed employee resumes no longer show the placeholder company text when a resume item has no description. This prevents incorrect information from appearing in employee documents and avoids requiring users to edit technical templates to fix it.
Original PR description
Steps to reproduce: - Employees > Any employee - Make any resume item with empty description field - Gear in top-left > Print > Print Resume What happens: Resume items with no description default to placeholder "Odoo India pvt. Ltd". Why is this an issue: This put wrong information in resumes and cannot be corrected from the client side (The default is pulled directly from the template, which is not meant to be accessed casually). What was done: Removed description from template. opw-4033434 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error that could appear when creating a product variant with GCC invoicing enabled. Users can now create products normally without being blocked by a traceback.
Original PR description
before this commit, a traceback was showing on creating product variant steps to reproduce: * click create button in product, traceback will be showing after this commit, without any traceback…
before this commit, a traceback was showing on creating product variant steps to reproduce: * click create button in product, traceback will be showing after this commit, without any traceback product is created traceback is introduced in: https://github.com/odoo/odoo/commit/758ced91f8cb220a003a49b01e047b507f8509d7 traceback details:  super()._compute_display_name() File "/data/build/enterprise/sale_renting/models/product_product.py", line 14, in _compute_display_name super()._compute_display_name() File "/data/build/odoo/addons/l10n_gcc_invoice/models/product.py", line 23, in _compute_display_name product.display_name = re.sub(r'(\d)(\s)([\u0600-\u06FF])', repl, product.display_name) File "/usr/lib/python3.10/re.py", line 209, in sub return _compile(pattern, flags).sub(repl, string, count) TypeError: expected string or bytes-like object --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when users choose a source stock quantity while creating a stock move line. It makes the inventory workflow smoother by using the product unit information already available before the related stock move is created.
Original PR description
Before PR: when creating a SML and changing the quant_id (pick from), you get a traceback as the stock_move is not yet created After PR: Since the issue appears before the real creation of the SML (and thus the SM), reading the uom of the product directly from the SML should not pose any issue opw-3931980 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents Google Calendar account resets from failing when users choose to delete events from Odoo while synchronizing all existing events. Businesses can now reset affected calendar accounts without encountering missing-record errors or needing manual intervention.
Original PR description
Before this commit, attempting to reset an account with the policies "Delete from Odoo" and "Synchronize all existing events" set would fail. This was due to a write operation being performed on records after they had been unlinked, resulting in a "Missing Record: Record does not exist or has been deleted." error. opw-4043858 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fix prevents an error when creating a new product variant while the GCC invoice localization is installed. It adds a safe default when a product name is not yet available, allowing users to complete product setup without interruption.
Original PR description
Currently, a traceback is occurring when the user tries to create a new product To reproduce this issue: 1) install sales, `l10n_gcc_invoice` 2) Try to create a new `product variant` from sales Error:- ```TypeError: expected string or bytes-like object``` In this commit `product.display_name` is used in `re.sub()` in which `product display name` should be false when initially creating a product. which leads to a traceback. After applying this commit, it will resolve this issue by giving a default value when the product.display_name is false. commit:- https://github.com/odoo/odoo/pull/169267/commits/89ba4003eea350e9e2833744637b32cd67d62952 https://github.com/odoo/odoo/blob/69e3d9d48dfb138367039e650b826a4f44af5697/addons/l10n_gcc_invoice/models/product.py#L11-L23 sentry-5593088590