Tuesday, June 18, 2024
6 changes · saas-17.3
Resolved issues and error corrections
This change adds a missing way for the spreadsheet app to identify Odoo pivot tables. It helps pivot-related actions work correctly, reducing errors when users interact with pivot data in spreadsheets.
Original PR description
In order to fix an issue with the odoo pivot actions, we need to add a new getter to get the odoo pivot ids. Task: 3992325 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
Point of Sale tests now use USD consistently instead of depending on each company's configured currency. This prevents false test failures in environments using a different currency, helping keep releases stable without changing customer-facing behavior.
Original PR description
The tests were failing when the company currency was not USD, because the tests were using the company currency to create the products and the pricelists. This commit changes the tests to always use USD as the company currency. Runbot errors ids: 64677,64676,64675,64674,64673,64672,64671,64670,64669,64668,64667,64666,64665,64664,64663,64662,64661,64660,64659,64658,64657,64656,64655,64654,64653,64652,64651,64650,64649,64648,64647,64646,64645,64644,64643,64642,64641,64640,64639,64638,64637,64636,64635,64634,64633,64632,64631,64630,64629,64628,64627,64626,64625,64624,64623,64622
Disabled icon buttons in the course content list no longer show an unintended border. This removes a visual glitch and makes course navigation look cleaner and more consistent for learners.
Original PR description
## Issue In Course List, After v17.3 + There a topless border in icons where button is disabled. Which looks weird and doesn't make sense as we don't need any border there. ## Technical This issue came from this commit odoo@7d66dcb , where `disabled="1"` was added inside the button. The default `btn.disabled` has button border in [bootstrap](https://github.com/odoo/odoo/blob/51af11c9180fe48ba3492ffd3402a22bde211318/addons/web/static/lib/bootstrap/dist/css/bootstrap.css#L3048-L3053) code. That's why the border is appearing there. ## After this PR There will be no borders where icon buttons are disabled. Task-3975450
The DIAN support document button on Colombian vendor bills now appears only when the related journal is properly configured for it. This helps prevent users from trying to send documents through an unsupported or incomplete setup.
Original PR description
The "Send Support Document to DIAN" button was displayed on vendor bills even when the associated journal was not set up for it (the field "Resolución de Facturación" was not set up for that move's journal). The button is now invisible if the correct conditions are not met. task-3990920
This fix stabilizes an automated test for the Gantt view around daylight saving time changes. It helps keep release validation reliable and reduces false test failures without changing user-facing behavior.
Original PR description
We forgot to fix the non deterministic test "date grid and dst winterToSummer (1 cell part)" in https://github.com/odoo/enterprise/pull/64541. We finish the job here. Runbot issue: 67941
Users creating a signature request will no longer see a confusing validation error simply because they switch browser tabs after choosing a template. The required signer information is still checked when they actually try to send the request, keeping safeguards in place while reducing unnecessary interruptions.
Original PR description
Before this commit, when you started creating a signature request through the pop-up, added a template and changed your browser tab, a validation error would be triggered telling you that you didn't insert the partners for the signing roles. This is counter intuitive because the user didn't even try to create the sign request through the button, it just moved to another tab. After this commit, we removed this validation error. It was not needed because if the user tried to send the signature request without any inserted partners, the action would already be blocked by another validation error asking to add the partner for each sign role. task-3961814