Navigate
Branch
Saturday, August 17, 2024
14 changes
2 changes
Miscellaneous changes
**Steps to reproduce:** (Require credentials) - Install l10n_eg_edi_eta - Switch to an Egyptian company - Configure the Egyption localization - Create an invoice and post it to ETA - Go to ETA portal and reject the invoice - From invoice in Odoo, request EDI cancellation **Issue:** The following error is displayed: { 'code': 'ValidationError', 'message': None, 'target': 'Update Document Status', 'details': [{ 'code': None, 'target': 'Document.UUID
Original PR description
**Steps to reproduce:** (Require credentials)
- Install l10n_eg_edi_eta
- Switch to an Egyptian company
- Configure the Egyption localization
- Create an invoice and post it to ETA
- Go to ETA portal and reject the invoice
- From invoice in Odoo, request EDI cancellation
**Issue:**
The following error is displayed:
{
'code': 'ValidationError',
'message': None,
'target': 'Update Document Status',
'details': [{
'code': None,
'target': 'Document.UUID',
'message': 'Provided Status is invalid, based on the current document status.'
}]
}
**Solution:**
Before cancelling an invoice, check submission status.
If it's cancelled or rejected, do not send the cancellation EDI request and responds to the method with a success.
opw-3884519
---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Forward-Port-Of: odoo/odoo#170406**Steps to reproduce:** - Install Accounting, l10n_eu_oss and l10n_es_edi_tbai - Switch to a Spanish company (e.g. ES Company) - Create an invoice for a Portugese customer: * Customer: [a Portugese customer] * Invoice Lines: [a line with OSS tax "23.0% PT VAT (Goods)"] - Confirm the invoice - Process the invoice by E-invoicing service: TicketBAI (ES) - Check the generated EDI document **Issue:** The value of "ClaveRegimenIvaOpTrascendencia" is "01". It should be "17" for OSS oper
Original PR description
**Steps to reproduce:** - Install Accounting, l10n_eu_oss and l10n_es_edi_tbai - Switch to a Spanish company (e.g. ES Company) - Create an invoice for a Portugese customer: * Customer: [a Portugese customer] * Invoice Lines: [a line with OSS tax "23.0% PT VAT (Goods)"] - Confirm the invoice - Process the invoice by E-invoicing service: TicketBAI (ES) - Check the generated EDI document **Issue:** The value of "ClaveRegimenIvaOpTrascendencia" is "01". It should be "17" for OSS operations. **Solution:** Check if a tax from "l10n_eu_oss" module is used in one of the invoice lines. If it is the case, set "ClaveRegimenIvaOpTrascendencia" to "17". opw-4034659 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#176780 Forward-Port-Of: odoo/odoo#176564
11 changes
Enhancements to existing features
Restaurants can now launch the self-ordering kiosk experience on one or more IoT Boxes directly from the Point of Sale app. IoT Box screens can also be rotated from the device form when a display and input device are available, making kiosk setup easier in different physical layouts.
Original PR description
- Added support for screen rotation from IoT form if IoT has a display and a keyboard (touchscreen is detected as a keyboard), - Updated "open kiosk" popup to open Kiosk on multiple IoT Boxes at once from PoS app, Community PR: [https://github.com/odoo/odoo/pull/174009](https://github.com/odoo/odoo/pull/174009) Task: 3598744
Code cleanup and technical improvements
The enterprise Discuss performance tests were updated to use lower expected counters after recent internal optimizations. This helps the team spot future performance regressions more accurately, with no direct change for end users.
Original PR description
To reflect improvements done recently in particular optimizations with using Store, and to better detect changes in counters of future commits. https://github.com/odoo/odoo/pull/176980
Miscellaneous changes
- Age group, brand and manufecturer attributes are created, if not available and set their visibility. - The price provided by BarcodeLookup is properly set according to the price received is with or without tax included. - Extra information is saved in internal note section. - The color attribute will be created only if the value exists. - Making sure that weight and volumes are saved after converted to the company uom. Related: https://github.com/odoo/odoo/pull/174027 task- 3965079 F
Original PR description
- Age group, brand and manufecturer attributes are created, if not available and set their visibility. - The price provided by BarcodeLookup is properly set according to the price received is with or without tax included. - Extra information is saved in internal note section. - The color attribute will be created only if the value exists. - Making sure that weight and volumes are saved after converted to the company uom. Related: https://github.com/odoo/odoo/pull/174027 task- 3965079 Forward-Port-Of: odoo/enterprise#68413 Forward-Port-Of: odoo/enterprise#63740
Before this commit: - If the budget type is an expense it is considering only analytic lines with the category vendor_bill. - If the budget type is revenue it is considering only analytic lines with the category invoice. - It will consider analytic lines with both categories if the budget type is both. After this commit: - If an analytic line has a negative value, it should be considered as an expense. - If it has a positive value, it should be considered as revenue. - The budget must
Original PR description
Before this commit: - If the budget type is an expense it is considering only analytic lines with the category vendor_bill. - If the budget type is revenue it is considering only analytic lines with the category invoice. - It will consider analytic lines with both categories if the budget type is both. After this commit: - If an analytic line has a negative value, it should be considered as an expense. - If it has a positive value, it should be considered as revenue. - The budget must include all analytic items, without filtering based on category. - The committed amount is now calculated correctly for budget types set to "both." Task-4108958 Forward-Port-Of: odoo/enterprise#68289
Before this commit: - When updating the quantity or unit price on a purchase order line, red lines would appear even if it was not overcommitted. - The budget amount was calculated by adding the committed amount from the budget line and the subtotal of the line item multiplied by the (ordered quantity - invoiced quantity). - If the invoiced quantity is 0, the calculation would multiply the ordered quantity by the line item’s subtotal, leading to an incorrect calculation. After this commit:
Original PR description
Before this commit: - When updating the quantity or unit price on a purchase order line, red lines would appear even if it was not overcommitted. - The budget amount was calculated by adding the committed amount from the budget line and the subtotal of the line item multiplied by the (ordered quantity - invoiced quantity). - If the invoiced quantity is 0, the calculation would multiply the ordered quantity by the line item’s subtotal, leading to an incorrect calculation. After this commit: - The is_over_budget check will be calculated based on the latest budget line committed amount by using flush_model in the `_compute_all` method. Task-4112959 Forward-Port-Of: odoo/enterprise#68410
Automatically close the print dialog after the user confirms the print job. This enhancement improves user experience by eliminating the need for users to manually close the dialog, streamlining the printing process. Initially, we considered keeping the modal open until all print operations completed successfully. If any printer encountered an error, the modal would remain open. However, this approach doesn't assist users in resolving the issue, as they would still need to close the modal to
Original PR description
Automatically close the print dialog after the user confirms the print job. This enhancement improves user experience by eliminating the need for users to manually close the dialog, streamlining the printing process. Initially, we considered keeping the modal open until all print operations completed successfully. If any printer encountered an error, the modal would remain open. However, this approach doesn't assist users in resolving the issue, as they would still need to close the modal to correct the problem. Therefore, it is more user-friendly to automatically close the modal after user confirmation. https://github.com/user-attachments/assets/659d971e-25c8-487f-8c02-cf0f5461a920 Forward-Port-Of: odoo/enterprise#68256 Forward-Port-Of: odoo/enterprise#68195
Steps to reproduce ================== - Enable debug mode - Go to Accounting > Bank - Click on New => TypeError at describeType Cause of the issue ================== The props of the BankRecQuickCreate were not properly declared. - An Object.fromEntries call was missing - The quickCreateView prop was redeclared - The globalState prop was missing opw-4107812 Forward-Port-Of: odoo/enterprise#68451
Original PR description
Steps to reproduce ================== - Enable debug mode - Go to Accounting > Bank - Click on New => TypeError at describeType Cause of the issue ================== The props of the BankRecQuickCreate were not properly declared. - An Object.fromEntries call was missing - The quickCreateView prop was redeclared - The globalState prop was missing opw-4107812 Forward-Port-Of: odoo/enterprise#68451
1. Add a button in the dashboard to view the number of drafts SODA entries for the CodaBox Soda journal. This button opens the SODA draft entries 2. Add a new non-stored field on the validation wizard to verify that the user has correctly copied the Accounting Firm password. If not, the 'Validate connection' button will be disabled 3. Add a link to the documentation in the connection wizard task-id 4008140 Forward-Port-Of: odoo/enterprise#68324 Forward-Port-Of: odoo/enterprise#65440
Original PR description
1. Add a button in the dashboard to view the number of drafts SODA entries for the CodaBox Soda journal. This button opens the SODA draft entries 2. Add a new non-stored field on the validation wizard to verify that the user has correctly copied the Accounting Firm password. If not, the 'Validate connection' button will be disabled 3. Add a link to the documentation in the connection wizard task-id 4008140 Forward-Port-Of: odoo/enterprise#68324 Forward-Port-Of: odoo/enterprise#65440
## Issue: - changing the next invoice date to a future date in the subscription app incorrectly changes the subscription status to "To be invoiced" ## Steps To Reproduce: - create subscription, and confirm it - Run the scheduled action: 'Sale Subscription: generate recurring invoices and payments' - change the 'Date of Next Invoice' on the subscription. - Notice that the related quotation invoice status is `To invoice` ## Solution: - Changing next_invoice_date or last_invoice_date sh
Original PR description
## Issue: - changing the next invoice date to a future date in the subscription app incorrectly changes the subscription status to "To be invoiced" ## Steps To Reproduce: - create subscription, and confirm it - Run the scheduled action: 'Sale Subscription: generate recurring invoices and payments' - change the 'Date of Next Invoice' on the subscription. - Notice that the related quotation invoice status is `To invoice` ## Solution: - Changing next_invoice_date or last_invoice_date should not impact the quantity invoiced, as invoiced amounts should remain unchanged. - Therefore, I removed `order_id.next_invoice_date` and `order_id.last_invoice_date` from the dependencies of `_compute_qty_invoiced`. opw-3932847 Forward-Port-Of: odoo/enterprise#65203
Issue: When we have multiple companies and we create different folders for each other, if we are working in a folder from let's say company A and then we switch to Company B, we will run the same link to this folder but from the Company B rights point of view, and since this folder is not accesible from this company it will throw a traceback and break the page until refresh to another url. Steps to reproduce: 1. Install Documents. 2. Have atleast 2 companies. 3. Create a new folder that
Original PR description
Issue: When we have multiple companies and we create different folders for each other, if we are working in a folder from let's say company A and then we switch to Company B, we will run the same…
Issue: When we have multiple companies and we create different folders for each other, if we are working in a folder from let's say company A and then we switch to Company B, we will run the same link to this folder but from the Company B rights point of view, and since this folder is not accesible from this company it will throw a traceback and break the page until refresh to another url. Steps to reproduce: 1. Install Documents. 2. Have atleast 2 companies. 3. Create a new folder that belongs to the current company. 4. While having this folder selected, change to the 2nd company. Solution: The issue is triggered within the load funcion for the DocumentsSearchModel, since we get the folderId that's in the url, and we also get the list of the folder we have access to, we could filter out if the current folder we are trying to access is within this list before calling toggleCategoryValue, and If it's not we could just call it on `folderId = false;` as default (which is the "All" section of folders). This way we avoid calling `category.values.get(...)` later on for undefined (we don't have access to this folder). opw-3971935 Forward-Port-Of: odoo/enterprise#68409 Forward-Port-Of: odoo/enterprise#64513
Display a notification to the user when a document starts printing and again when the printing process is complete. Each notification include the name of the printer being used, so the user is informed about the status of their print job and the specific printer involved. This enhances the overall experience by providing clear feedback. Currently, the user is only notified when the print job is failed. Forward-Port-Of: odoo/enterprise#68282 Forward-Port-Of: odoo/enterprise#68102
Original PR description
Display a notification to the user when a document starts printing and again when the printing process is complete. Each notification include the name of the printer being used, so the user is informed about the status of their print job and the specific printer involved. This enhances the overall experience by providing clear feedback. Currently, the user is only notified when the print job is failed. Forward-Port-Of: odoo/enterprise#68282 Forward-Port-Of: odoo/enterprise#68102
1 change
New functionality added to Odoo
This update adds new inventory tracking reports required by Peruvian tax authorities (PLE 12.1 and PLE 13.1 records). These reports track inventory movements in physical units and monetary values, with mandatory monthly reporting and submission deadlines of October 1st and April 1st each year. This ensures Peruvian businesses can comply with local tax regulations directly within Odoo.
Original PR description
Added PLE 12.1 and PLE 13.1 records for detailed inventory tracking. PLE 12.1 tracks inventory in physical units, while PLE 13.1 includes both physical and monetary values. Both records are updated semi-annually and reported monthly, with submission deadlines of October 1st and April 1st, per Superintendent Resolution 169-2015.