Sunday, June 2, 2024
7 changes
6 changes
Miscellaneous changes
Before this commit: The label for Transporter Doc Number and Date was visible but the field was seemed to be hidden After this commit: We fix the above issue, now the field is visible when the mode is selected to `By Road` task-3959862 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 Forward-Port-Of: odoo/odoo#167
Original PR description
Before this commit: The label for Transporter Doc Number and Date was visible but the field was seemed to be hidden After this commit: We fix the above issue, now the field is visible when the mode is selected to `By Road` task-3959862 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 Forward-Port-Of: odoo/odoo#167339
To reproduce: ============= - Install sale_loyalty_delivery - create a loyalty card where customer gets free delivery for 10 points and gets 1 point per 1$ spent - create a sale order with more than 10$ and apply the loyalty card - free delivery line is added - change the price to be less than 10$ -> free delivery line is not removed Problem: ======== we have a logic that prevents deleting the free delivery line, it's not explained why we have this logic, and there is no test for i
Original PR description
To reproduce: ============= - Install sale_loyalty_delivery - create a loyalty card where customer gets free delivery for 10 points and gets 1 point per 1$ spent - create a sale order with more than 10$ and apply the loyalty card - free delivery line is added - change the price to be less than 10$ -> free delivery line is not removed Problem: ======== we have a logic that prevents deleting the free delivery line, it's not explained why we have this logic, and there is no test for it. on the other hand, the use-case on the support ticket is valid, so we should remove this logic. opw-3879945 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166484
Shut down the server to simulate a connection lost when being in a multi record view. Click on a record to open it in form view. As the server is down, the web_read rpc will fail. The error will be caught by the onError in the action service, which will try to restore the previous controller (the multi record view). The server being down, requests for that controller will fail as well, and we'll end up again in the same onError callback. Since [1], we'll indefinitely try to reload the multi r
Original PR description
Shut down the server to simulate a connection lost when being in a multi record view. Click on a record to open it in form view. As the server is down, the web_read rpc will fail. The error will be…
Shut down the server to simulate a connection lost when being in a multi record view. Click on a record to open it in form view. As the server is down, the web_read rpc will fail. The error will be caught by the onError in the action service, which will try to restore the previous controller (the multi record view). The server being down, requests for that controller will fail as well, and we'll end up again in the same onError callback. Since [1], we'll indefinitely try to reload the multi record view, because we removed the check detecting that the error occurs in the controller that is already in the DOM. If that controller fails, there's no point trying to restore it again, instead, we just show the error. This commit simply restores that part of the code as it was before [1]. [1] odoo/odoo@9c954de94148ab6f3b8d02e6a4713a87fe233a28 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 Forward-Port-Of: odoo/odoo#166489 Forward-Port-Of: odoo/odoo#166295
- Before this commit: The system is sending E invoice requests for the Nil, Zero, Exempt, Non GST supply. which is not required by the government, cause of which E-way bill creation for Bill of Supply is not becoming possible. - After this commit: Fix this issue by filtering out invoices that only use Nil, Zero, Exempt, Non GST as their taxes. task - 3957555 Forward-Port-Of: odoo/odoo#167647 Forward-Port-Of: odoo/odoo#167337
Original PR description
- Before this commit: The system is sending E invoice requests for the Nil, Zero, Exempt, Non GST supply. which is not required by the government, cause of which E-way bill creation for Bill of Supply is not becoming possible. - After this commit: Fix this issue by filtering out invoices that only use Nil, Zero, Exempt, Non GST as their taxes. task - 3957555 Forward-Port-Of: odoo/odoo#167647 Forward-Port-Of: odoo/odoo#167337
Before this commit: creating a move line with a product without hsn code and later adding the hsn code on the product. The hsn code on the move line doesn't get updated After this commit: We solve the above issue and add dependency of `product_id.l10n_in_hsn_code` on the compute method task-3958797 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167291
Original PR description
Before this commit: creating a move line with a product without hsn code and later adding the hsn code on the product. The hsn code on the move line doesn't get updated After this commit: We solve the above issue and add dependency of `product_id.l10n_in_hsn_code` on the compute method task-3958797 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#167291
ZATCA updated the VAT exemption reason codes to be provided for 0% taxes. This commit aims to expand the list of existing tax exemption reason codes in odoo to include the new reason: VATEX-SA-OOS Description of the issue/feature this PR addresses: Currently the VAT exemption reasons defined in the l10n_sa_edi module do not include all the reasons listed by ZATCA Current behavior before PR: Current VAT exemption reasons do not include reason VATEX-SA-OOS, i.e: "Not subject to VAT" De
Original PR description
ZATCA updated the VAT exemption reason codes to be provided for 0% taxes. This commit aims to expand the list of existing tax exemption reason codes in odoo to include the new reason: VATEX-SA-OOS Description of the issue/feature this PR addresses: Currently the VAT exemption reasons defined in the l10n_sa_edi module do not include all the reasons listed by ZATCA Current behavior before PR: Current VAT exemption reasons do not include reason VATEX-SA-OOS, i.e: "Not subject to VAT" Desired behavior after PR is merged: Add VAT exemption reason VATEX-SA-OOS --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#166104
1 change
Miscellaneous changes
l10N_my_reports does not depend on account_reports currently while it should. It was made visible with the changes with Invoicing/Accounting modules. runbot-66373 Forward-Port-Of: odoo/enterprise#63560
Original PR description
l10N_my_reports does not depend on account_reports currently while it should. It was made visible with the changes with Invoicing/Accounting modules. runbot-66373 Forward-Port-Of: odoo/enterprise#63560