Friday, April 26, 2024
6 changes · saas-17.2
Resolved issues and error corrections
This update refreshes the spreadsheet component to a newer version with fixes for calculation updates, row removal borders, and data validation suggestions. Users should see more reliable spreadsheet behavior and faster recalculation in everyday use.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/a730f5c20 [REL] 17.2.5 https://github.com/odoo/o-spreadsheet/commit/05fd37f3f [FIX] evaluator: Prevent incorrect invalidation of spread Task: 3883954 https://github.com/odoo/o-spreadsheet/commit/bc831e37f [PERF] evaluation: faster dependencies checking Task: 3874821 https://github.com/odoo/o-spreadsheet/commit/48cfd16b6 [IMP] helpers: backport recompute zone https://github.com/odoo/o-spreadsheet/commit/6f5dea847 [FIX] borders: wrong borders on remove rows Task: 3884112 https://github.com/odoo/o-spreadsheet/commit/e654b7ef0 [FIX] dataValidation: Display suggestions on dv-icon click Task: 3872312 https://github.com/odoo/o-spreadsheet/commit/9d115e6ce [FIX] tests: rewrite autocomplete test
Updates the Colombian localization base data so it can support the latest electronic invoicing requirements under Anexo 1.9. This helps businesses operating in Colombia remain aligned with current invoicing compliance rules when using the related EDI functionality.
Original PR description
The spec for electronic invoices in Colombia was updated and is now known as Anexo 1.9. This was done in the related enterprise PR (module l10n_co_edi). This commit introduces some changes in the base module that are needed for the Anexo 1.9 update. task-3639271 ### related PRs FW-port of https://github.com/odoo/odoo/pull/148953 (15.0) https://github.com/odoo/odoo/pull/151407 (16.0) https://github.com/odoo/odoo/pull/151418 (saas-16.3) https://github.com/odoo/odoo/pull/151431 (17.0) https://github.com/odoo/odoo/pull/151432 (17.1)
This fix ensures marketing automation actions always get the needed date range setting when they are created. It prevents scheduled server actions from failing because of a missing scheduled date, improving reliability for automated campaigns and CRM follow-ups.
Original PR description
The default value is removed from `activity_date_deadline_range_type` field, this causes server action scheduled date to be NULL which raises an error when server action is run. To solve the issue we added range type when server action is created. ticket-3884415
Creating a planning shift no longer crashes when the selected sales order line belongs to another active company. This helps businesses using multiple companies schedule work reliably without being blocked by an error.
Original PR description
Steps to reproduce: --------------------- -Go to the planning module -Activate more than one company -create Sales order in company A -create shift in company B and select sales oder of comapny A -save the record -traceback Issue: ---------------------- On saving, when more than one company is activated and a shift is created for a specific company with an SOL selected from other company, a Singleton Error occurs. Cause: --------------------------- The traceback arises due to inability to iterate over multiple companies during this process on creating a shift. Solution: ------------------------ Implemented a looping to iterate over each company, ensuring proper handling of the multiple company on the shift task-3859050
Updates Colombian electronic invoicing to comply with the latest Anexo 1.9 requirements, including currency conversion changes needed for official reporting. It also fixes credit note handling and adds checks to help ensure vendor documents continue working as before.
Original PR description
### [FIX] l10n_co_edi: add a test for the vendor document Previously there was no test for the vendor document. This commit adds a (simple) test.c In the next commit of the same PR the code for the…
### [FIX] l10n_co_edi: add a test for the vendor document Previously there was no test for the vendor document. This commit adds a (simple) test.c In the next commit of the same PR the code for the vendor document had to be adapted while keeping the result the same. This test helps in making sure nothing went wrong. The reason was that the electronic invoice and vendor document share some common code / logic but the shared parts had to be changed for an update to the electronic invoice spec (Anexo 1.9). (See the next commit for details) ### [FIX] l10n_co_edi: update for anexo 1.9 The spec for electronic invoices in Colombia was updated and is now known as Anexo 1.9. This commit updates the electronic invoice to meet the new spec A bit part of the new spec is the conversion of many fields from document to company currency / COP. There is also a vendor document. But it follows a different spec. Thus some shared logic / section with the electronic invoice was updated so that the vendor document remains unchanged. The following sections were removed since they are obsolete and also (basically) dead code: * OVT section: dead code * FE1 section: content is dead code Previously when creating a credit note from an invoice with the reversal wizard (account.move.reversal) there was the following bug. The Credit Note Concept (l10n_co_edi_description_code_credit on account.move) was set after posting. This was corrected in this commit (since a validation on post was added to check that the concept is there). ### task task-3639271 ### related PRs forward-port of https://github.com/odoo/enterprise/pull/54086 (15.0) https://github.com/odoo/enterprise/pull/55268 (16.0) https://github.com/odoo/enterprise/pull/55274 (saas-16.3) https://github.com/odoo/enterprise/pull/55279 (17.0) https://github.com/odoo/enterprise/pull/55280 (17.1)
Fixed an issue where email marketing messages could fail to send when a template contained social media icons or buttons without a web link. This helps users send standard marketing templates reliably without hidden errors blocking delivery.
Original PR description
Currently, an exception is generated when the user sends a template to a mailing that contains icons like Facebook, LinkedIn, etc. Steps to produce an exception: 1. Create a database without demo…
Currently, an exception is generated when the user sends a template to a mailing that contains icons like Facebook, LinkedIn, etc. Steps to produce an exception: 1. Create a database without demo data > install 'Email Marketing'. 2. Go to Email Marketing > Create New > Select the `Welcome Message` template. 3. Click 'Send' >> An error will occur in the log, and there is nothing to send. Error: `AttributeError: 'NoneType' object has no attribute 'startswith'` This is because at [1], we don't have `href` in 'link_node', so we receive `False` in 'original_url', and as a result, it generates an error while accessing 'original_url.startswith'. With the recently refactored code with commit https://github.com/odoo/odoo/commit/6349051e5e4442cfabc899520c5708081dc0be31, line [1] was added. Before this change, Line [2] was filtering out elements from `html` that did not have 'href'. This commit will fix the above issue by not processing to find the absolute URL if we do not have `original_url`. [1]- https://github.com/odoo/odoo/blob/b6629bbdb53d9a4bacee2032190e30a848bb6d6d/addons/link_tracker/tools/html.py#L25 [2]- https://github.com/odoo/odoo/blob/c9644a086b294e69b69e52e8ccfd5292bde815da/addons/link_tracker/models/mail_render_mixin.py#L39 sentry-5140192785