Tuesday, May 13, 2025
3 changes · saas-17.4
Resolved issues and error corrections
This update refreshes the spreadsheet component and fixes several issues affecting formulas, pivot tables, charts, and sheet duplication. Business users should see more reliable spreadsheet reports, especially when working with date-based pivot data and complex spreadsheet edits.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/e3ac48a41 [REL] 17.4.34 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0)…
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/e3ac48a41 [REL] 17.4.34 [Task: 0](https://www.odoo.com/odoo/2328/tasks/0) https://github.com/odoo/o-spreadsheet/commit/fb6101bee [FIX] function: IF should not mutate its input [Task: 4783504](https://www.odoo.com/odoo/2328/tasks/4783504) https://github.com/odoo/o-spreadsheet/commit/91be4cd5a [FIX] pivot: handle undefined granularity [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/392cdf83d [FIX] pivot: add missing month granularity [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/d534332e2 [FIX] pivot: date dimension detection [Task: 4742696](https://www.odoo.com/odoo/2328/tasks/4742696) https://github.com/odoo/o-spreadsheet/commit/f3dae84e6 [FIX] spreadsheet: add name to DUPLICATE_SHEET [Task: 4640070](https://www.odoo.com/odoo/2328/tasks/4640070) https://github.com/odoo/o-spreadsheet/commit/1076c3f39 [IMP] pivots: table type synced with pivot structure [Task: 4771509](https://www.odoo.com/odoo/2328/tasks/4771509) https://github.com/odoo/o-spreadsheet/commit/321f34d1a [FIX] chart: can `UPDATE_CHART` on a non-chart figure [Task: 4775605](https://www.odoo.com/odoo/2328/tasks/4775605) https://github.com/odoo/o-spreadsheet/commit/2094035c7 [FIX] GridComposer: limit the composer size [Task: 4686816](https://www.odoo.com/odoo/2328/tasks/4686816) Co-authored-by: Anthony Hendrickx (anhe) <anhe@odoo.com> Co-authored-by: Alexis Lacroix (laa) <laa@odoo.com> Co-authored-by: Lucas Lefèvre (lul) <lul@odoo.com> Co-authored-by: Dhrutik Patel (dhrp) <dhrp@odoo.com> Co-authored-by: Adrien Minne (adrm) <adrm@odoo.com> Co-authored-by: Mehdi Rachico (mera) <mera@odoo.com> Co-authored-by: Florian Damhaut (flda) <flda@odoo.com> Co-authored-by: Rémi Rahir (rar) <rar@odoo.com> Co-authored-by: Pierre Rousseau (pro) <pro@odoo.com> Co-authored-by: Vincent Schippefilt (vsc) <vsc@odoo.com>
This fix prevents receipt validation from crashing when an inventory push rule uses the same destination location as the receipt. Businesses can validate affected warehouse receipts normally, reducing interruptions in stock operations.
Original PR description
Currently, an exception is raised when validating a new receipt transfer where both the stock move and the push rule have the same destination location. Steps to Reproduce: 1. Install `stock` module…
Currently, an exception is raised when validating a new receipt transfer where both the stock move and the push rule have the same destination location. Steps to Reproduce: 1. Install `stock` module 2. Enable Multi-Step Routes in Inventory 3. Routes -> Enable Warehouses and ensure they are linked to `YourCompany`. 4. Create a new rule for that route. 5. Set action to 'Push To' with same source and destination (e.g., WH/Stock) and Automatic Move to 'Automatic No Step Added'. 6. Go to Inventory -> Operations-> Receipts 7. Create a new receipt with the same destination location as defined in the rule. 8. Click on Validate TypeError: ```TypeError unsupported operand types in: stock.move() - None ``` This issue[1] occurs when the rule and stock have the same destination location. It does not execute and returns None, resulting in new_move being None. When `move.move_dest_ids - new_move` is executed, it raises an error. [1]- https://github.com/odoo/odoo/blob/5c182227514af87659ee48360c63f33487de71bf/addons/stock/models/stock_move.py#L1048 sentry-6551676919 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Azure cloud storage container names that include hyphens are now accepted when uploading attachments. This prevents server error pop-ups for users sending messages with attachments while using valid Azure container names.
Original PR description
Versions -------- - saas-17.4+ Steps ----- 1. Create a Azure storage container with a hyphen in its name; 2. connect it to your database; 3. go to a contact; 4. click "Send message"; 5. upload an attachment. Issue ----- Server Error pop-up. In the logger, you get: > `TypeError: UserError.__init__() takes 2 positional arguments but 3 were given` Cause ----- 1. The `ValidationError` string is badly formatted. 2. The regex to verify Azure Blob Storage URLs doesn't allow hyphens in the container name. Solution -------- 1. As the `ValidationError` is only shown in the logger, format it as an f-string. 2. Update the regex to the constraints imposed by Azure[^1]. [^1]: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules#microsoftstorage opw-4770160