Monday, April 28, 2025
5 changes · 17.0
Resolved issues and error corrections
Vendor bills imported from Mexican CFDI XML files now show the correct SAT status after users run the SAT update. This prevents bills from appearing to have no SAT status even when the underlying validation information is available.
Original PR description
- With l10n_mx_edi, create an invoice and send it to the cfdi. Download the cfdi xml. - Import the xml as a vendor bill. Confirm and click on Update SAT. - The vendor bill list view the l10n_mx_edi_cfdi_sat_state is set to false despite the l10n_mx_edi.document.sat_state being set. https://github.com/odoo/enterprise/commit/b34a4d105c67807628284257be51295e33da6bf0 added the ability to import cfdi xml as vendor bills and updated the selection for l10n_mx_edi.document.state with invoice_received. However the compute _compute_l10n_mx_edi_cfdi_state_and_attachment which depends on l10n_mx_edi.document.state was not updated to take into account that new possible selection. opw-4673134
Creating a planning shift during a non-working period could fail when the shift was not linked to a resource. The update makes timezone lookup handle that case safely, improving reliability for scheduling users.
Original PR description
Before this commit, the user could have a crash when he tries to create a shift in non-working period because the method to search on the right timezone to use does not take into account the shift could be not linked to a resource. This commit makes sure the timezone is correctly found without any issue when we search on a timezone.
Miscellaneous changes
### Steps to reproduce: - Accounting dashboard - Click on the three dots of the "Bank" card - Click "import file" - Try importing a CAMT file with the namespace "camt" - Traceback Other issue: - Try importing a CAMT file with a custom Code in `ns:Domn/ns:Cd` (example: "IC1") - Traceback ### Cause: Namespaces can be used in CAMT files but the way Odoo handled them was incorrect. We were creating a dictionary using `root.nsmap`. It only worked when the file didn't have a namespace ke
Original PR description
### Steps to reproduce: - Accounting dashboard - Click on the three dots of the "Bank" card - Click "import file" - Try importing a CAMT file with the namespace "camt" - Traceback Other issue: - Try…
### Steps to reproduce: - Accounting dashboard - Click on the three dots of the "Bank" card - Click "import file" - Try importing a CAMT file with the namespace "camt" - Traceback Other issue: - Try importing a CAMT file with a custom Code in `ns:Domn/ns:Cd` (example: "IC1") - Traceback ### Cause: Namespaces can be used in CAMT files but the way Odoo handled them was incorrect. We were creating a dictionary using `root.nsmap`. It only worked when the file didn't have a namespace key because if the key was different from 'ns' the `findall` didn't work. Second issue: Some banks use their own codes in the CAMT files. The specification has numerous codes which Odoo added in a dictionary, and it reads from this dictionary to get a description. When there is a custom code, Odoo tries to read a key which doesn't exist explaining the traceback. ### Solution: - Change the way namespace is computed using the tag. - If the code is not in the dictionary, we take the custom code. opw-4553152 Forward-Port-Of: odoo/enterprise#82888
The exception for the second trimester for 2024 has been redone for 2025. task-4734827 Forward-Port-Of: odoo/enterprise#84024
Original PR description
The exception for the second trimester for 2024 has been redone for 2025. task-4734827 Forward-Port-Of: odoo/enterprise#84024
Currently, we have regular (Raspberry Pi) IoT Boxes and Widnows ("Virtual") IoT Boxes The subscription for the Raspberry Pis cost a monthly fee to the users, while Windows IoT is considered to be free for the users. However when sending information about the number of IoT Boxes connected to a database we currently don't make a difference between Windows and Raspberry Pi IoT Boxes. This PR adds a distinction between the two and send the Raspberry Pi IoT Boxes under "IoTBox" message and t
Original PR description
Currently, we have regular (Raspberry Pi) IoT Boxes and Widnows ("Virtual") IoT Boxes
The subscription for the Raspberry Pis cost a monthly fee to the users, while Windows IoT is considered to be free for the users.
However when sending information about the number of IoT Boxes connected to a database we currently don't make a difference between Windows and Raspberry Pi IoT Boxes.
This PR adds a distinction between the two and send the Raspberry Pi IoT Boxes under "IoTBox" message and the Windows ones under "WindowsIoT" message.
This allows us to distinguish the two subscriptions on odoo.com
task-4567313
Forward-Port-Of: odoo/enterprise#78516