Wednesday, September 18, 2024
22 changes · saas-17.2
Miscellaneous changes
Problem was we try to get partner from `order.partner` instead of `order.partner_id` Steps to reproduce: - Install l10n_cl - Select the CL Company - Go to POS - Select products - Change the client to Blanco Martin & Asociados EIRL (has all the information for l10n_cl) - Click on "payment" - Select any payment method - Select the option "Invoice" - Validate - Console error opw-4180894 Forward-Port-Of: odoo/enterprise#70239
Original PR description
Problem was we try to get partner from `order.partner` instead of `order.partner_id` Steps to reproduce: - Install l10n_cl - Select the CL Company - Go to POS - Select products - Change the client to Blanco Martin & Asociados EIRL (has all the information for l10n_cl) - Click on "payment" - Select any payment method - Select the option "Invoice" - Validate - Console error opw-4180894 Forward-Port-Of: odoo/enterprise#70239
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the 1st account, select 'Account Receivable' (e.g., 121000 Account Receivable). - Set the Partner field to "0h3n-abcdefg@yahoo.example.com" and the label field to "Online transfer reced agst INV-00171, Dt:01.08.2024". - For the 2nd account, set it to any other type, such as "101401 Bank". - Add
Original PR description
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the…
Steps to reproduce ================== - In the accounting app, go to 'Journal Entries'. - Create a new entry. - Set the 'reference' field to 'Receipt'. - Add 2 accounts in Journal Items. - For the 1st account, select 'Account Receivable' (e.g., 121000 Account Receivable). - Set the Partner field to "0h3n-abcdefg@yahoo.example.com" and the label field to "Online transfer reced agst INV-00171, Dt:01.08.2024". - For the 2nd account, set it to any other type, such as "101401 Bank". - Add a credit amount in the 'Account Receivable' and the same amount in the 2nd account. - Save and post the transaction. - Navigate to the general ledger. - Ensure you expand the list of this newly created account move under the 121000 Account Receivable to observe overlapping text. - Click on 'PDF' and print the report. - Notice the overlapping text.  Cause of the issue ================== The o_overflow_value class is only applied when the cell value length is longer than 65 chars Solution =======  Here are the differences, only the following lines are pushed down  opw-4130917 Forward-Port-Of: odoo/enterprise#70141
Steps to reproduce (on IOS): ------------------- With Safari browser: - Install `Meeting Rooms` app - Go to Meeting Rooms -> Rooms and open any room - Copy the `Room Booking URL` and open it in a new tab - Click on the menu, then on `Add to Home Screen` - Open the room booking from the home screen Issue: ------ The URL and browser buttons are visible at the top of the screen. Solution: --------- Add the meta tags `mobile-web-app-capable` and `apple-mobile-web-app-capable`
Original PR description
Steps to reproduce (on IOS): ------------------- With Safari browser: - Install `Meeting Rooms` app - Go to Meeting Rooms -> Rooms and open any room - Copy the `Room Booking URL` and open it in a new tab - Click on the menu, then on `Add to Home Screen` - Open the room booking from the home screen Issue: ------ The URL and browser buttons are visible at the top of the screen. Solution: --------- Add the meta tags `mobile-web-app-capable` and `apple-mobile-web-app-capable` to the room template. opw-3639196 Forward-Port-Of: odoo/enterprise#67944
Before this commit: whenever user clicked on `Checkout our tutorial` broken url on GSTR report a new page with 404 Not Found opened After this commit: We fix the `Checkout our tutorial` broken url, now when user clicks on the page it redirects user to Odoo documentation of GSTR filing Forward-Port-Of: odoo/enterprise#70129
Original PR description
Before this commit: whenever user clicked on `Checkout our tutorial` broken url on GSTR report a new page with 404 Not Found opened After this commit: We fix the `Checkout our tutorial` broken url, now when user clicks on the page it redirects user to Odoo documentation of GSTR filing Forward-Port-Of: odoo/enterprise#70129
Reproduce Steps: ---------- 1. Install the Planning module. 2. Navigate to My Planning. 3. Open the Repeat Shift section. 4. Click the Delete button. 5. Click on a radio button label, such as 'This and Following Shifts'. Fixed an issue where clicking the shift option labels did not select the corresponding value. The problem was addressed by setting the `id` attribute on the input element and properly associating it with the label. task-3978567 Forward-Port-Of: odoo/enterprise#
Original PR description
Reproduce Steps: ---------- 1. Install the Planning module. 2. Navigate to My Planning. 3. Open the Repeat Shift section. 4. Click the Delete button. 5. Click on a radio button label, such as 'This and Following Shifts'. Fixed an issue where clicking the shift option labels did not select the corresponding value. The problem was addressed by setting the `id` attribute on the input element and properly associating it with the label. task-3978567 Forward-Port-Of: odoo/enterprise#68220
Since the fiscal position is added in data with the xml, the others companies than the current ones don't have it. So this commit will allow: - When installing the Avatax modules, create the fiscal position in all US companies at the same time - When creating a new US company with the Avatax module installed, setup the fiscal position in the new company at the same time task: 4100725 Forward-Port-Of: odoo/enterprise#69204
Original PR description
Since the fiscal position is added in data with the xml, the others companies than the current ones don't have it. So this commit will allow: - When installing the Avatax modules, create the fiscal position in all US companies at the same time - When creating a new US company with the Avatax module installed, setup the fiscal position in the new company at the same time task: 4100725 Forward-Port-Of: odoo/enterprise#69204
A new dependency has been introduced by mistake. Even if it still makes sense from a functional point of view, this modification wasn't respecting our stable policy and thus should be reverted. Error introduced at https://github.com/odoo/enterprise/pull/63481 Forward-Port-Of: odoo/enterprise#70173
Original PR description
A new dependency has been introduced by mistake. Even if it still makes sense from a functional point of view, this modification wasn't respecting our stable policy and thus should be reverted. Error introduced at https://github.com/odoo/enterprise/pull/63481 Forward-Port-Of: odoo/enterprise#70173
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the original implementation only expects a single event. That then led to the status getting repeatedly checked and logging "list indices must be integers or slices, not str" when done through a cron. This fix supports both the single and multiple event scenario. The l10n_cl_claim field is not display
Original PR description
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the…
When parsing a claim status from the SII, the list of events in the response can either be a single event or a list of events. If a list was returned this would fail with a parsing error because the original implementation only expects a single event. That then led to the status getting repeatedly checked and logging "list indices must be integers or slices, not str" when done through a cron. This fix supports both the single and multiple event scenario. The l10n_cl_claim field is not displayed anywhere by default and is only used to check if the claim status still needs to be logged in the chatter or not. Since multiple response codes are possible, in theory it should be a list instead of a single value, but that would be more appropriate for a change in master. A boolean flag would also suffice if the response code doesn't need to be displayed separately. We currently just set the last code that was returned. The responses observed in the customer database include the code NCA, which isn't expected by Odoo. This code was added as a valid one. opw-3920273 Forward-Port-Of: odoo/enterprise#70167 Forward-Port-Of: odoo/enterprise#66498
This commit will set the deferred accounts for spain template. task: 4181499 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180004
Original PR description
This commit will set the deferred accounts for spain template. task: 4181499 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180004
Do not use the purchase description in dropshipping pickings Example use case: - Create a dropshipping product and set a purchase description - Create a sales order with the product and confirm - Purchase order will have the purchase description - Confirm the purchase order - Go to dropshipping picking - Print Delivery slip Current behavior: - Product name and purchase description is displayed Expected behavior: - Purchase description should not be displayed @Tecnativa TT5067
Original PR description
Do not use the purchase description in dropshipping pickings Example use case: - Create a dropshipping product and set a purchase description - Create a sales order with the product and confirm - Purchase order will have the purchase description - Confirm the purchase order - Go to dropshipping picking - Print Delivery slip Current behavior: - Product name and purchase description is displayed Expected behavior: - Purchase description should not be displayed @Tecnativa TT50677 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180111 Forward-Port-Of: odoo/odoo#179104
The custom stock.move.line's x2many field computes a domain automatically for the SML that can be selected from the stock.move records (e.g. when trying to find a specific lot, etc. to fulfill a demand). This commit makes it possible to include the domain defined on the field in the final constructed domain, making it possible to somewhat customize this behaviour without the need for a js override. Task-4116000 ----------- Example of customization made possible with this: Have a com
Original PR description
The custom stock.move.line's x2many field computes a domain automatically for the SML that can be selected from the stock.move records (e.g. when trying to find a specific lot, etc. to fulfill a demand).
This commit makes it possible to include the domain defined on the field in the final constructed domain, making it possible to somewhat customize this behaviour without the need for a js override.
Task-4116000
-----------
Example of customization made possible with this:
Have a computed field `x_allowed_lot_ids` on the stock.move and restrict the selection of the lots to this domain by modifying the view `stock.view_stock_move_operations`:
```xml
<field name="move_line_ids" domain="[('lot_id', 'in', x_allowed_lot_ids)]" [...] widget="sml_x2_many"/>
```
without this commit, the `domain` attribute set on the field is simply ignored and it would require a more complex js custo (we could live with it)
Forward-Port-Of: odoo/odoo#180421With this commit we extend the account_tax model to add tax category code and tax exemption reason, that will be used when generating peppol xml. Without that we can only do some incomplete computation leading to missing informations in peppol xml. opw-4061329 Forward-Port-Of: odoo/odoo#180309 Forward-Port-Of: odoo/odoo#176221
Original PR description
With this commit we extend the account_tax model to add tax category code and tax exemption reason, that will be used when generating peppol xml. Without that we can only do some incomplete computation leading to missing informations in peppol xml. opw-4061329 Forward-Port-Of: odoo/odoo#180309 Forward-Port-Of: odoo/odoo#176221
When uploading a bill via xml, if the file does not contain the node 'Name` in accounting parties informations, we don't set the partner at all on the bill. With this commit, if the node `Name` is missing, we fallback to the node `RegistrationName`. opw-4154071 Forward-Port-Of: odoo/odoo#180308 Forward-Port-Of: odoo/odoo#180056
Original PR description
When uploading a bill via xml, if the file does not contain the node 'Name` in accounting parties informations, we don't set the partner at all on the bill. With this commit, if the node `Name` is missing, we fallback to the node `RegistrationName`. opw-4154071 Forward-Port-Of: odoo/odoo#180308 Forward-Port-Of: odoo/odoo#180056
On accounts from 14... to 19..., there are current liabilities while they should be non-current libialities. Manual forward-port of #178373 opw-4134510 Forward-Port-Of: odoo/odoo#180446
Original PR description
On accounts from 14... to 19..., there are current liabilities while they should be non-current libialities. Manual forward-port of #178373 opw-4134510 Forward-Port-Of: odoo/odoo#180446
Before this commit, when importing multiple leaves for different employee, the last employee in the list will be set as a follower on all the created leaves. This commit fixes this behavior by checking for the employee assigned to each leave and using its ID when adding the follower. opw-4023073 Forward-Port-Of: odoo/odoo#179872 Forward-Port-Of: odoo/odoo#178994
Original PR description
Before this commit, when importing multiple leaves for different employee, the last employee in the list will be set as a follower on all the created leaves. This commit fixes this behavior by checking for the employee assigned to each leave and using its ID when adding the follower. opw-4023073 Forward-Port-Of: odoo/odoo#179872 Forward-Port-Of: odoo/odoo#178994
When the message in the chatwindow is too long, the textarea in the chatwindow is constantly showing the scorllbar. This causes the chatwindow to flicker when the user is typing a message. This commit fixes the issue by setting excatly the right class for the fake textarea in the chatwindow so that it can get the real height of the textarea. Current behavior before PR:  Desired behavior after PR is mer
Original PR description
When the message in the chatwindow is too long, the textarea in the chatwindow is constantly showing the scorllbar. This causes the chatwindow to flicker when the user is typing a message. This commit fixes the issue by setting excatly the right class for the fake textarea in the chatwindow so that it can get the real height of the textarea. 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 Forward-Port-Of: odoo/odoo#180483
When returning a purchase/sale order, we can not create accrued entry for the returned order Steps: - Create a purchase order - Receive product - Create and confirm bill - Set received quantity to 0 - From the action menu, select "Accrued Expense Entry" -> There is no line, it should be a line for the vendor credit not This is because we filter the order lines to get only the lines that have a positive quantity to invoice, in that case the quantity to invoice is negative and should be taken i
Original PR description
When returning a purchase/sale order, we can not create accrued entry for the returned order Steps: - Create a purchase order - Receive product - Create and confirm bill - Set received quantity to 0 - From the action menu, select "Accrued Expense Entry" -> There is no line, it should be a line for the vendor credit not This is because we filter the order lines to get only the lines that have a positive quantity to invoice, in that case the quantity to invoice is negative and should be taken into account opw-4176706 Forward-Port-Of: odoo/odoo#180299
**Steps to reproduce this issue:** - Go to views (Settings -> Technical -> User Interface -> Views). - Edit something and click the Save/Discard button. - Notice that the Save and Discard buttons remain visible. **Current behavior before PR:** The state `fieldIsDirty` remains true after clicking the Save/Discard button because the `FIELD_IS_DIRTY` event defined in the `useBus` hook is not triggered in `commitChanges`. **Desired behavior after PR is merged:** The Save and Discard
Original PR description
**Steps to reproduce this issue:** - Go to views (Settings -> Technical -> User Interface -> Views). - Edit something and click the Save/Discard button. - Notice that the Save and Discard buttons remain visible. **Current behavior before PR:** The state `fieldIsDirty` remains true after clicking the Save/Discard button because the `FIELD_IS_DIRTY` event defined in the `useBus` hook is not triggered in `commitChanges`. **Desired behavior after PR is merged:** The Save and Discard buttons hide successfully when not needed. task-3948043 Forward-Port-Of: odoo/odoo#174187
Description of the issue/feature this PR addresses: The date format in Lao contain a typo: `%d/%m/y` should be `%d/%m/%Y` Desired behavior after PR is merged: The date format should be `%d/%m/%Y` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180481
Original PR description
Description of the issue/feature this PR addresses: The date format in Lao contain a typo: `%d/%m/y` should be `%d/%m/%Y` Desired behavior after PR is merged: The date format should be `%d/%m/%Y` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180481
Description of the issue/feature this PR addresses: Add translation for the default content Note: I tried adding `_()` within the field, but it didn't work, so I moved it to the default function `_get_default_job_details` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179688 Forward-Port-Of: odoo/odoo#178484
Original PR description
Description of the issue/feature this PR addresses: Add translation for the default content Note: I tried adding `_()` within the field, but it didn't work, so I moved it to the default function `_get_default_job_details` --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#179688 Forward-Port-Of: odoo/odoo#178484
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase order with the oldest date_order field. The last_purchase_date field should be set using the purchase order with the most recent date_order field. Purpose: By ordering the purchase orders by date_order desc we will get the purchase order with the most recent date_order field. This will cause the supp
Original PR description
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase…
Problem: When viewing the replenishment information for a product, the last purchase date is set to the date from the oldest purchase order. The last_purchase_date field is set using the purchase order with the oldest date_order field. The last_purchase_date field should be set using the purchase order with the most recent date_order field. Purpose: By ordering the purchase orders by date_order desc we will get the purchase order with the most recent date_order field. This will cause the supplier’s last purchase date to be the most recent one instead of the oldest one. Steps to Reproduce on Runbot: 1. Create a storable product and create a reordering rule for this product 2. Create a purchase order for this product and set the Order Deadline to a date in the past and then confirm it 3. Create a purchase order for this product and set the Order Deadline to the current date and the confirm it 4. Navigate to this product’s replenishment information 5. Observe that the Last Purchase date is the earlier of the two dates from the purchase orders opw-4113810 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#180500 Forward-Port-Of: odoo/odoo#177306
Versions: 17.0, saas-17.1, saas-17.2 Issue: The tax totals company currency table displays repetitive information. Purpose of this PR: To remove the repetitive tax totals table. Steps to Reproduce: - Install l10n_cl_edi - Set up a currency rate for any active foreign currency (different from CLP) (Using USD for the example) - Create an invoice using a foreign currency (USD in the example) opw-4127839 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.
Original PR description
Versions: 17.0, saas-17.1, saas-17.2 Issue: The tax totals company currency table displays repetitive information. Purpose of this PR: To remove the repetitive tax totals table. Steps to Reproduce: - Install l10n_cl_edi - Set up a currency rate for any active foreign currency (different from CLP) (Using USD for the example) - Create an invoice using a foreign currency (USD in the example) opw-4127839 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#178265