Daily updates from Odoo
Wednesday, September 25, 2024
13 changes
2 changes
Resolved issues and error corrections
Intercompany sales and dropship orders now route goods through the Inter-Company Transit location as intended, instead of incorrectly treating the end customer as the internal destination. This helps companies avoid inventory routing errors and keeps cross-company deliveries aligned with the expected business flow.
Original PR description
Since #156437, the moves can have a final location representing their final endpoint. This causes some issues for inter-company transactions, as they are meant to deliver to/pick from the 'Inter-Company Transit' location. This means that for sale orders meant to other companies, they are always supposed to deliver their goods there: - Normal delivery: CompA/Stock -> ICT, ICT -> CompB/Stock - Dropship: CompA/Stock -> ICT, ICT -> Customer But this opens a few issues, as the compA SO's `partner_shipping_id` is the customer itself, meaning that the final location would end up as Customers, which we want to avoid. Also, to accomodate both these cases, we need to add a bit complexity computation of the location_dest of a move. We consider that if the location_dest is Customers but its final is ICT, then we apply the ICT. opw-4163612 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
This fixes a Point of Sale issue where product information could fail to open after refreshing a session that uses employee login. The system now reads the cashier role from the correct place, preventing an error for users with administrator PoS access.
Original PR description
Problem: The `role` attribute is being retrieved from the `raw` field, but when the page is refreshed, all attributes (including `role`) are set in the `cashier` object, not in `raw`. Steps to reproduce: - Set up a PoS session with the "Log in with Employees" setting enabled. - Use a User/Employee with Administrator PoS access (e.g., Mitchell Admin). - Start a PoS session. - Refresh the page. - Click the "i" icon to see more information about a product. - A traceback occurs. opw-4120414 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
8 changes
Enhancements to existing features
Studio approval workflows now let authorized users revoke approvals made at lower notification levels, giving teams better control over multi-step approvals. The update also fixes a mobile debug crash in the approval dropdown and refreshes records after approval actions so related discussions stay current.
New Odoo databases now show polished sample dashboards instead of blank charts and tables when there is no business data yet. This helps users understand the value and expected layout of dashboard apps during onboarding, before real records are created.
Original PR description
Prior to this commit, when an Odoo database had no records, the dashboards were empty and ugly. This commit alleviates this problem by introducing dashboards with dummy data displayed in the background with low opacity when there are no records for the main model that is supposed to be displayed in the main dashboard sheet. Task: 3947773 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Colombian electronic invoice emails now include a ZIP file with both the PDF and the legally required XML document. This helps businesses comply with DIAN requirements by including the invoice details and the official DIAN status response in the emailed document package.
Original PR description
Due to legal reasons, we need to send a zip containing the PDF and the xml. The xml is an UBL `AttachedDocument` containing both the initial xml representing the invoice and the `ApplicationResponse` returned when calling the GetStatus webservice of DIAN. The `ApplicationResponse` is an xml representing the state of the invoice on the DIAN server. task-4133688
Payroll work entry types can now be linked to a specific country, helping companies manage local payroll rules more accurately. This also improves multi-company setups by showing work entry types based on each company's country and updates localized payroll data accordingly.
Original PR description
added country field in hr work entry type added multi company rule for work entry type based on countries added country for every l10n with work entry type task-3978261
Radio button options added to documents in Odoo Sign now appear immediately instead of waiting for the next periodic refresh. This makes template editing feel faster and reduces delays for users preparing documents for signature.
Original PR description
Before this commit: rendering of new radio items was slow. This happened due to the `refreshSignItems` being called each 2 seconds normally. which is responsible for making the sign items visible. In this commit: `refreshSignItems` is called after adding new radio items. Task: 4208037
Resolved issues and error corrections
WhatsApp conversations in Discuss now reactivate as soon as a new message arrives from a WhatsApp contact. This prevents teams from missing the first incoming message on previously deactivated channels and keeps customer follow-up timely.
Original PR description
This commit [1] introduces a bug where WA channel doesn't get re-activated after first new message from WA Partner. Steps to reproduce: 1. Keep a de-activated channel open in Discuss. 2. Send a message from WA Partner. 3. Channel doesn't get activated. 4. Send another message. 5. Channel gets activated. This commit fixes the issue. [1]: 4eafd01620b48cd79c4fd319237003d8d39cb217
Budget committed amounts now stay accurate when a purchase order has a draft vendor bill. Draft bills no longer reduce the committed amount until they are posted, preventing budgets from appearing under-committed too early.
Original PR description
When calculating the commited amount of a budget, if a draft bill is available for a PO, the commited amount will be 0. This is due to the fact that qty_invoiced is set even when the bill is not posted. To ensure that the commited amount stays consistent, we will only take into account the qty_invoiced when the related bill is posted.
Odoo Studio now preserves compatibility for older Kanban views after a template naming change. This prevents legacy Kanban menus from breaking, helping users continue editing and using existing views reliably.
Original PR description
Commit [1] renamed `kanban-card` and `kanban-menu` template names into `card` and `menu`. This was meant to be done on kanban views using the new API (i.e. defining a `kanban-card` template instead of `kanban-box`), to keep backward compatibility. However, the renaming for the menu impacted both old and new API kanban views (as they both share the same template name), thus breaking legacy ones. This commit fixes the issue. [1] odoo/odoo@233f03da5ae9c269618e6e28c775a123c0afca79
3 changes
Enhancements to existing features
This improvement extends the fiscal folio display feature to vendor invoices and payment records in list views. Previously, this important Mexican tax identification number was only visible for customer invoices. Now users can see the fiscal folio across all relevant transaction types, improving visibility and compliance tracking for Mexican operations.
Original PR description
Allow viewing the fiscal folio for vendor invoices and all payments in the tree view, as it currently only displays for customer invoices.
Resolved issues and error corrections
Fixed a bug where users could incorrectly select expense accounts from different companies when creating assets in a multi-company environment. This prevents data integrity issues and ensures assets only use accounts from their own company.
Original PR description
To reproduce: Be in multicompany, with several companies selected. Create an asset Click on the Expense Account field Select accounts from a different company than the asset's We should not show these. Even worse, in ulterior version, you can save the asset. (computing depreciations would still be prevented) The issue is that we define a custom domain, so it should include it. no-task Forward-Port-Of: odoo/enterprise#68699
Fixed an issue that prevented non-administrator users from sending and printing Mexican invoices (CFDI). The system now properly handles certificate access during invoice processing without requiring administrative rights. This allows regular users to complete their invoicing tasks independently.
Original PR description
### Steps to reproduce issue: 1. Install Mexican localization 2. Make sure Demo User has no administration right 3. As Demo User, create and confirm Invoice for Mexican customer - Make sure Products of the Invoice have an UNSPSC Category (Accounting tab) 5. Send and print Invoice for CFDI 6. An Access Error is raised: > You are not allowed to access 'SAT Digital Sail' (l10n_mx_edi.certificate) records. > > This operation is allowed for the floowing groups: > - Administration/Settings ### Explanation: During the operation, the user will retrieve the certificates of the company in `_send_api`. Those certificates can only be accessed by people with `group_system` access rights. ### Fix reasoning: Since the issue only concerns the retrieval of the certificates, we will enter superuser mode when executing this operation. opw-4205612