Daily updates from Odoo
Wednesday, September 25, 2024
21 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
11 changes
Resolved issues and error corrections
This fix prevents an error when calculating allocated hours for open planning shifts that do not yet have a resource assigned. It improves stability for scheduling workflows by checking that a resource exists before using its flexibility settings.
Original PR description
Before this commit, the compute of the allocated hours could be raised a traceback if the shift is an open one because we check if the resource is flexible before checking if there is a resource set on the shift. This commit makes sure a resource exists on the shift before checking if the resource is flexible or not. task-4206945
Users editing Kanban views in Studio can now successfully turn bold formatting on or off for fields. This fixes a formatting issue so cards display as configured, improving consistency for teams customizing their workflows.
The demo setup for restaurant table bookings now shows the appointment name as “Table” instead of “Table Booking.” This avoids confusing or redundant wording on the customer-facing booking page.
Original PR description
**How to reproduce:** 1) Create a Table Booking appointment from the Action helper. 2) Go to the booking page for that appointment it looks like this - https://tinyurl.com/29q2ktjb **After this PR** Now that appointment name will be Table instead of Table Booking. Task-4210749
Payment method names in expense extraction views are adjusted so the journal name only appears where it is useful, such as grouped reporting views. This avoids clutter or confusing labels in other screens while preserving the added context where users need it.
Original PR description
In this pr: https://github.com/odoo/odoo/pull/174537 we have change the display name of the payment method line by adding the name of the journal. But it has changed every view where the payment method line are available. Since we want to have the journal on the groupby of some view, we added a context key to be added when we want to hide the journal. no task id community: https://github.com/odoo/odoo/pull/181340
Residual amounts in foreign currency are now shown only when multi-currency support is enabled. This avoids unnecessary or confusing currency fields for businesses that operate in a single currency.
Original PR description
Ensures that the different residual in currency fields are only visible when base.group_multi_currency is enabled.
Users can now customize the final part of an appointment sharing link instead of being blocked by a read-only field. This makes shared links easier to personalize and manage when sending appointment invitations.
Original PR description
How to reproduce: 1. Create a share link. 2. Try to change the last part. 3. It's read-only. Technical Reason: The last part of the link 'short_code' is set to 'readonly'. After this commit: The link can be edited. Task-4194229
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
The Partner Ledger filter now shows individual partners without a parent company, not just company records. This helps users find and report on all relevant partners more accurately from the dropdown.
Original PR description
Steps to reproduce: - Go to Partner Ledger report - Open partner filtering dropdown list Current behaviour: - Show company partners only Expected behaviour: - Should show indiviual partners without parent as well X-original-commit: de5b10f
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
This fixes the label used for the financial budget action after it was previously changed incorrectly. Users will see the proper budget action name, reducing confusion when navigating budget reports.
Original PR description
The aim of this commit is renaming the financial budget action name properly. In this commit [[1]], we wrongly change the action name for analytic budget, it was wrong. no task id [1]: https://github.com/odoo/enterprise/commit/6ccc3030a57bc1218ad327280804c2e95dee0a59
3 changes
Resolved issues and error corrections
Creating a discussion thread from a message now displays the message text cleanly instead of showing raw HTML tags such as <p>. This improves readability for users, especially when network conditions are slow and message loading timing varies.
Original PR description
Before this commit, creating a thread from a message was sometimes showing the html tags of the message in text content.
Steps to reproduce:
- Open general channel
- Post a message
- Set "slow 4g" network performance
- Create a thread from the message => It opens the sub channel with the message, but the
message and thread name title shows HTML tags like `<p>`
This happens due to missing of `store.insert({ html: true })`, which this commit fixes.
Task-4207900
Before
After
Creating a discussion thread from a message now displays the message text and thread title cleanly instead of showing raw HTML tags like <p>. This improves readability in Mail discussions, especially when the interface loads slowly on poor network connections.
Original PR description
Before this commit, creating a thread from a message was sometimes showing the html tags of the message in text content.
Steps to reproduce:
- Open general channel
- Post a message
- Set "slow 4g" network performance
- Create a thread from the message => It opens the sub channel with the message, but the
message and thread name title shows HTML tags like `<p>`
This happens due to missing of `store.insert({ html: true })`, which this commit fixes.
Task-4207900
Before
After
Fixes several issues with the document extraction status header so it displays correctly on smaller screens, updates reliably when switching or refreshing documents, and prevents duplicate actions while loading. This helps users see accurate extraction progress across invoices, bank statements, expenses, and recruitment documents.
Original PR description
Fixes for multiple things related to extract status header: - Fix split translation string by choosing a generic term - On smaller displays, the header was not taking up the full width - Added check_status_loading to disable button when rpc is loading - Remove header in expense when the user refreshes a extracted document - Sync record props when switching between documents or manually requesting extraction
5 changes
Resolved issues and error corrections
This update fixes a display issue on mobile devices where two important alerts were overlapping each other on the map view. Now, the setup token alert will only appear after the address locating process is complete, providing a cleaner and more user-friendly experience on mobile devices.
Original PR description
before this commit: On mobile devices, the `Locating new addresses` and `Set up token` Bootstrap alerts are overlapping. after this commit: On mobile devices, the `Set up token` alert only becomes visible after the `Locating new addresses` process has been completed. Task-3928322 Forward-Port-Of: odoo/enterprise#70526 Forward-Port-Of: odoo/enterprise#69822
A previous update accidentally removed access control restrictions from a sensitive field in the Dutch tax reporting module. This fix restores the proper access group settings to ensure only authorized users can view or modify this field, maintaining data security and compliance.
Original PR description
The PR https://github.com/odoo/enterprise/pull/67874 wrongly removed a group parameter on a sensitive field. This adds it back. Forward-Port-Of: odoo/enterprise#70575
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
This fix adds the missing UNSPSC (United Nations Standard Products and Services Code) classifications for "Square meter" and "Square foot" units of measure. These codes are now properly assigned in the Surface category, ensuring accurate product classification for purchasing and compliance purposes.
Original PR description
Problem: The UNSPSC codes for "Square meter" and "Square foot" were not created for the corresponding units of measure. Steps to reproduce: - Navigate to Purchase > Configuration > UoM Categories > Surface. - There is no UNSPSC category assigned by default for these units of measure. opw-4103838 Forward-Port-Of: odoo/enterprise#70102
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