Thursday, June 27, 2024
18 changes · 17.0
New functionality added to Odoo
Odoo now validates Uruguayan RUT/RUC tax identification numbers when entered on contacts. This helps businesses catch incorrect customer or supplier tax IDs earlier and improves data quality for invoicing and compliance.
Original PR description
--- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Enhancements to existing features
The Uruguay localization now includes DGI codes for generic document types. This helps ensure customer or partner identification data maps correctly for local tax reporting and compliance processes.
Original PR description
Related to https://github.com/odoo/enterprise/pull/51266 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Resolved issues and error corrections
This fixes the layout of Chilean invoice PDFs by moving transferable sections back to the right side below the totals. The change makes better use of blank space and restores a cleaner, more readable invoice presentation while preserving support for future factoring-related document versions.
Original PR description
Description of the issue/feature this PR addresses: In commit https://github.com/odoo/odoo/commit/7ee07bc8c8573ab879b1d6995b3443271fe20149 the stamp, transferable-table, and transferable-legend divs were relocated to all go on the left side. Previously, they had a width of col-4 which allowed them to fit in the same row side by side using 1/3 of the page's width each. Current behavior before PR: After that change they were positioned on the left side on top of each other. Desired behavior after PR is merged: This commit moves both transferable divs to the right half of the page below the invoice's totals to use the blank space better. It is relevant to keep in mind that these divs are inserted in the invoice to allow for easy inheritance and a future implementation of the factoring version of the pdf (cedible). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Miscellaneous changes
Steps to reproduce: - Install "Subscriptions" - Go to "Configuration" -> "Alerts" - Create a new alert: - Add a name for the alert - Action: Create next activty - Trigger On: Modification - Activtiy: To Do - Add a summary - Add a note - Due Date In: 1 - Due Date type: Put it blank Issues: When triggered the action will result in a traceback due to `activity_date_deadline_range_type`. https://github.com/odoo/odoo/blob/9a62d0c82cdc47718181aed36cad763499b4a51d/addo
Original PR description
Steps to reproduce: - Install "Subscriptions" - Go to "Configuration" -> "Alerts" - Create a new alert: - Add a name for the alert - Action: Create next activty - Trigger On: Modification - Activtiy: To Do - Add a summary - Add a note - Due Date In: 1 - Due Date type: Put it blank Issues: When triggered the action will result in a traceback due to `activity_date_deadline_range_type`. https://github.com/odoo/odoo/blob/9a62d0c82cdc47718181aed36cad763499b4a51d/addons/mail/models/ir_actions_server.py#L123-L124 [Linked PR](https://github.com/odoo/enterprise/pull/63816) opw-3946293 Forward-Port-Of: odoo/odoo#168043
When users open a calendar event and then use the breadcrumb to return, the calendar now restores the week they were viewing instead of jumping back to the current week. This keeps navigation predictable and avoids users losing their place while editing or reviewing events.
Original PR description
Steps to reproduce: - Install Calendar - Go to next week for example - Click on an event -> edit - In the breadcrumb return to the calendar view Issues: The calendar show the current week and not the previous one. Even though we export the state we don't restore the date from the previous ones. opw-3946022
This change prevents an installation error when updating hardware drivers for Egypt ETA integrations. It helps ensure the affected driver override can be installed without failing due to an incompatible trace setting.
Original PR description
enableTrace() got an unexpected keyword argument 'level' Description of the issue/feature this PR addresses: need to update Drivers For EG ETA Current behavior before PR: Raise Error on install the override to change the driver used Desired behavior after PR is merged: nothing --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Because of translation of code. Odoo doesn't work if language is set to Swedish before doing the installation. The problem is in the translation in onboarding module.
Original PR description
Because of translation of code. Odoo doesn't work if language is set to Swedish before doing the installation. The problem is in the translation in onboarding module.
The appointment calendar schedule was adjusted to remove an unintended gap between morning and afternoon availability. This helps ensure customers can see and book valid appointment slots that were previously hidden.
Original PR description
Fix the gap between mornings and afternoons of the resource calendar `appointment_default_resource_calendar` which was leading to slot not been available. task-3858736
The Marketing Automation template form was displaying a duplicate button that wasn't functional or needed. This update removes that button from the interface, cleaning up the user experience and reducing confusion about available actions.
Original PR description
Before this PR: In Marketing Automation, upon opening a template form view, a duplicate button is displayed which won't be used. After this PR: Duplicate button is now hidden. Task - 3994775
Steps to reproduce the bug: - Go to the "/partners" page. - Click on the first partner to go to their page. - Enter "edit mode". - Drag and drop a "Dynamic products" snippet into the right column of the page. - Save the page. - Bug: the "Dynamic products" snippet is not visible on the page. The problem is not specific to the "Dynamic products" snippet. The issue occurs with all snippets. When the "website description" field is saved, all HTML attributes are removed (except the "cla
Original PR description
Steps to reproduce the bug: - Go to the "/partners" page. - Click on the first partner to go to their page. - Enter "edit mode". - Drag and drop a "Dynamic products" snippet into the right column of…
Steps to reproduce the bug: - Go to the "/partners" page. - Click on the first partner to go to their page. - Enter "edit mode". - Drag and drop a "Dynamic products" snippet into the right column of the page. - Save the page. - Bug: the "Dynamic products" snippet is not visible on the page. The problem is not specific to the "Dynamic products" snippet. The issue occurs with all snippets. When the "website description" field is saved, all HTML attributes are removed (except the "class" attribute). This causes many bugs, which vary depending on the snippets dropped into the field. This commit adds the parameter "sanitize_overridable=True" to the "website_description" field of "website_partner". It means that the description can now be properly edited as an user with enough rights, while keeping the same level of protection for other users editing this field. Still buggy, below version 15.0, for a restricted editor editing that description but should be rare. opw-3908218 Forward-Port-Of: odoo/odoo#165482
In Switzerland's demo data, the BIC is from a Belgian bank which is wrong. Removing BIC in this case as it's useless. task-3961609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167726
Original PR description
In Switzerland's demo data, the BIC is from a Belgian bank which is wrong. Removing BIC in this case as it's useless. task-3961609 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167726
Steps to reproduce the bug: - Create a storable product “P1” with BoM - Operation: OP1, OP2 - OP2 blocked by OP1 - Navigate to Mrp > Configuration > Operations - Select OP1 and select another BoM - Return to the BoM of “P1” Problem: The OP2 is still linked to OP1, And a traceback when attempting to duplicate the BoM. Solution: Remove the link between OP2 and OP1 opw-3948817 Forward-Port-Of: odoo/odoo#169511 Forward-Port-Of: odoo/odoo#169417
Original PR description
Steps to reproduce the bug: - Create a storable product “P1” with BoM - Operation: OP1, OP2 - OP2 blocked by OP1 - Navigate to Mrp > Configuration > Operations - Select OP1 and select another BoM - Return to the BoM of “P1” Problem: The OP2 is still linked to OP1, And a traceback when attempting to duplicate the BoM. Solution: Remove the link between OP2 and OP1 opw-3948817 Forward-Port-Of: odoo/odoo#169511 Forward-Port-Of: odoo/odoo#169417
**Steps to reproduce the bug:** - Parent company: CompanyA with a purchase tax of “15%” - Create a branch from Company - select only the brunch as current company - Create a storable product P1: - Add vendor: Azure Interior, price: $10 per unit - Create a recording rule: - Trigger: Manual - Route: Buy - Minimum quantity: 10 - save - Click on order **Problem**: A purchase order is created with Azure Interior as the vendor and 10 units
Original PR description
**Steps to reproduce the bug:**
- Parent company: CompanyA with a purchase tax of “15%”
- Create a branch from Company
- select only the brunch as current company
- Create a storable product P1:
- Add vendor: Azure Interior, price: $10 per unit
- Create a recording rule:
- Trigger: Manual
- Route: Buy
- Minimum quantity: 10
- save
- Click on order
**Problem**:
A purchase order is created with Azure Interior as the vendor and 10 units of P1, but the tax is not set. This happens because when the PO line values are prepared, the tax is retrieved from the supplier tax, but it is filtered by the current company, So only the branch taxes. However, it should also check in the parent company.
opw-3937178
Forward-Port-Of: odoo/odoo#169635Prior to this PR, if the words inside the grid were too long (ex: german), they were overflowing under the other elements of the grid. In worst cases scenario, words may be truncated. task-3815487 **Before**  **After**  --- I confir
Original PR description
Prior to this PR, if the words inside the grid were too long (ex: german), they were overflowing under the other elements of the grid. In worst cases scenario, words may be truncated. task-3815487 **Before**  **After**  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#158066
With restriction imposed by Colombian EDI, the PoS is not 100% compatible and usable as such features are not adapted for such restrictions. --- Description of the issue this commit addresses: When trying to issue a credit note via the POS (refund with invoice) and the colombian EDI module is installed, a traceback shows up as it is required to have a description code on the the credit note invoice but nothing in the UI makes it possible to add such data. --- Steps to reproduce:
Original PR description
With restriction imposed by Colombian EDI, the PoS is not 100% compatible and usable as such features are not adapted for such restrictions. --- Description of the issue this commit addresses: When…
With restriction imposed by Colombian EDI, the PoS is not 100% compatible and usable as such features are not adapted for such restrictions. --- Description of the issue this commit addresses: When trying to issue a credit note via the POS (refund with invoice) and the colombian EDI module is installed, a traceback shows up as it is required to have a description code on the the credit note invoice but nothing in the UI makes it possible to add such data. --- Steps to reproduce: 1-Install l10n_co_pos and l10n_co_edi 2-Setup all the fun stuff for the edi to work (credentials, VAT, journals, ...) 3-Go in the POS and post an order 4-Now refund that order and make sure to make an invoice with that refund, post 5-An error message shows up to inform that some data is missing. --- Desired behavior after the commit is merged: This commit makes it so that when a credit note is created from the PoS, if it is linked to Colombia, the description code is set to 1 if no code is already set. --- Note on the fix: It is currently not possible to already have a description code when the invoice is created so the default could be replaced by an assignation but I figured that if we add the possibility in the future, it would be great not to override it. --- task-3977188 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#170867 Forward-Port-Of: odoo/odoo#170739
Before this commit it was possible to remove employees with ongoing contracts. This commit adds a check to prevent this case. task: 3930155 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#169803 Forward-Port-Of: odoo/odoo#166338
Original PR description
Before this commit it was possible to remove employees with ongoing contracts. This commit adds a check to prevent this case. task: 3930155 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#169803 Forward-Port-Of: odoo/odoo#166338
-Before this commit, when user has no expense at all and in mobile view of expense, it will display term "Or" alongside with "Snap pictures of your receipts..." -After this commit, remove term "Or". Description of the issue/feature this PR addresses: Current behavior before PR:  Desired behavior after PR is merged:  Desired behavior after PR is merged:  --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#170460
This data is possible to be modified by users. Marking it as noupdate also avoids possible errors during upgrades, as if some values get updated (eg: product.product.type) it can [trigger validation errors](https://github.com/odoo/odoo/blob/16.0/addons/stock/models/product.py#L890). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#169623
Original PR description
This data is possible to be modified by users. Marking it as noupdate also avoids possible errors during upgrades, as if some values get updated (eg: product.product.type) it can [trigger validation errors](https://github.com/odoo/odoo/blob/16.0/addons/stock/models/product.py#L890). --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#169623