Daily updates from Odoo
Friday, September 13, 2024
14 changes
3 changes
Resolved issues and error corrections
Performance test expectations for appointment scheduling were adjusted to match recent user settings changes. This keeps internal quality checks accurate without changing how users book or manage appointments.
Original PR description
This commits updates three query counter checks adding three extra queries in order to adapt them to the addition of 1. a new sub query in 'calendar.event' which refers to the 'res.users.settings' table, 2. the fetching of the Default User Template in the 'res.users' model and 3. the search of the current user's 'res_users_settings_id' configuration. related-to: odoo/odoo#162467 task-3850837
Some pages were generating incorrect links after the move to newer, user-friendly URLs. This update corrects the template errors so appointment and appraisal survey links lead users to the right destinations.
Original PR description
Since the migration from the old URLs to the new user-friendly URLs, some typos were introduced in the templates. The syntax of the parameters of the Qweb dynamic attributes was not respected. This leads to incorrectly generated URLs. task-id 3820230
Odoo now converts Serbian Latin locale information into a format that browser-based features can understand. This prevents unexpected errors in affected apps when users work with the Serbian Latin language setting.
Original PR description
Serbian is a rare example of "synchronic digraphia", meaning that it has two writing systems that coexist and are used interchangeably by its speakers: Cyrillic and Latin. To handle this feature of Serbian in Odoo, we use a locale with a special modifier to specify the script to use: sr@latin. Problem: This locale is not recognized by the JavaScript APIs that implement the BCP 47 format, which leads to errors when trying to use them with the sr@latin locale. This commit adapts the code to use the properly formatted locale, thus avoiding unexpected crashes. *: sale_timesheet_enterprise, spreadsheet_edition, web_studio Task-4014022 Community: https://github.com/odoo/odoo/pull/172453 Forward-Port-Of: odoo/enterprise#66287 Forward-Port-Of: odoo/enterprise#66061
11 changes
Resolved issues and error corrections
This fix prevents Odoo-generated spreadsheet files from being automatically deleted by the system's cleanup process. When users upload certain file types, Odoo converts them to spreadsheet format, but these converted files were being incorrectly removed after 24 hours. This update ensures converted spreadsheets are preserved and not lost.
Original PR description
Problem: Auto-vacuum is incorrectly archiving reformatted spreadsheet documents that were generated from unsupported file uploads. Specifically, when an .xlsx file is uploaded, Odoo creates a new, compatible spreadsheet document. However, this newly generated document is mistakenly deleted during the auto-vacuum process if it is older than 24 hours. Purpose: Add a domain to prevent Odoo created spreadsheets from uploads being caught by autocron vacuum from improvement to 17.0 last year Steps to reproduce bug: 1.) Upload an xlsx file 2.) Click on the xlsx file 3.) It will generate an Odoo file of the same type 4.) Set the date of the new file to older than 24 hours 5.) The formatted file will be deleted when the autocron hits opw-4087851
This update reorders how information appears on Swiss payslips to improve readability and visual presentation. The gross salary amount now displays before deductions, making it easier for employees to understand their earnings at a glance.
Original PR description
Gross should come before deductions for aesthetic purposes on the payslip
This fix resolves an issue where PDF attachments were not being included when exporting financial data to Datev format from the general ledger. The system now correctly selects and includes the main attachment from invoices in the exported zip file, ensuring all necessary documents are available for accounting purposes.
Original PR description
Take a demo invoice, print it. Go to general ledger, print Datev ATCH, the pdf is not attached. We should select the message_main_attachment_id, as it's the one we want to have in the zip anyway. opw-4162604
This fix corrects how subscription orders display their invoice status. Previously, subscription orders were incorrectly showing as "fully invoiced" even when there were future invoices still pending. The system now properly checks the next invoice date to accurately reflect whether there are more invoices to generate, ensuring users have the correct visibility into their subscription billing status.
Original PR description
Versions -------- - 17.0+ Steps ----- 1. Create a subscription SO w/ a subscription product; 2. set recurrence to monthly; 3. set start date to 3+ months ago; 4. confirm & create invoice. Issue ----- In the Other Info tab, the Invoice Status is displayed as fully invoiced, despite there still being several months to invoice. Cause ----- The `_compute_invoice_status` method doesn't doesn't check `next_invoice_date` to decide whether a line's status should be `invoiced` or `to invoice`. Solution -------- Modify the override for `_compute_invoice_status` in sale_subscription, to change the `invoice_status` from `invoiced` to `to invoice` if the `next_invoice_date` is today or earlier. Also change compute dependency from `order_id.is_subscription` to `order_id.next_invoice_date`. This maintains a transitive dependency to `order_id.is_subscription`. opw-3849059
Fixed an issue where the bank reconnection button was not appearing when a bank connection's expiration date was set for today. This fix ensures users can promptly reconnect their bank accounts when needed, improving the user experience for online banking synchronization.
Original PR description
The aim of this commit is fixing the connected until widget to show the reconnect bank button when the expiration date is for today. The right to fix that, is doing the fix in the view but to avoid breaking the stable policy, we decide to make the change in the JS widget. task-4058051
This fix resolves an issue where appointment types that use only resources (instead of staff members) were becoming unbookable. A recent change to allow organizer modifications in Microsoft Calendar was incorrectly requiring the appointment creator to be listed as an attendee, which doesn't apply to resource-based appointments. The fix adds a condition to skip this check for resource-only appointment types, restoring their functionality.
Original PR description
Added condition on a check in microsoft calendar that ensured the organizer was an attendee on the event on create. This was added in a change that allowed the organizer to be changed on the Odoo side. However, this caused issues with the appointments app when creating an appointment that only used resources. The "organizer" who in this case is the creator of the appointment type would not be an attendee and therefore would cause an error and make the appointment type unbookable. Adding this condition allows the appointment to bypass the check if the appointment type uses resources instead of users. This change adds the necessary override in enterprise. See change in community here: https://github.com/odoo/odoo/pull/162927 opw-3841495
This update fixes a bug that was preventing users from closing the share panel in the Knowledge module. A previous change inadvertently broke this functionality, and this fix reverts that problematic change to restore the ability to close the share panel properly.
Original PR description
This reverts commit a80633d9f713884f3bda063de21c080bc062f6af.
This fix resolves an issue where partially completed production orders would create confusing duplicate component lines when creating backorders. Now when you partially complete a production using barcode scanning and then create a backorder, the remaining components will be consolidated into a single line per product, making inventory tracking clearer and more intuitive.
Original PR description
**Current behavior:** If you have a production opened in barcode and consume part of a component line to produce part of the final product, leave the transfer, then re-open it and confirm -> create…
**Current behavior:**
If you have a production opened in barcode and consume part of a
component line to produce part of the final product, leave the
transfer, then re-open it and confirm -> create the backorder,
the resulting backorder will have split the remaining raw moves
in an unintuitive manner.
**Expected behavior:**
The backorder should have one move for the remaining component
quantity.
**Steps to reproduce:**
1. Create a production for 10 of some final product consuming 10
some component -> Confirm
2. Open the production in barcode, add 5 of the final product to
its line and 5 of the component to its line -> exit the
transfer view
3. Reopen the production and validate it -> create backorder
4. Open the backorder to see the odd split of the component
product's moves
**Cause of the issue:**
When creating the backorder we normally expect each component
product to be encapsulated by a single line- so the split that
occurs when we leave the transfer initially without validating
which creates 2 moves for the same product means we get 2 moves
for the component for half of the remaining quantity for that
component.
**Fix:**
Incomplete barcode lines for production transfers should get
split into additional move lines as opposed to moves.
opw-4148050A bug in the UK tax reporting system has been corrected where important data (previous options) was not being properly passed through to the underlying system. This fix ensures tax reports are generated correctly without data loss or unexpected behavior.
Original PR description
Not passing the previous_options can have bad consequences, and was clearly not wanted here. Forward-Port-Of: odoo/enterprise#69913
This fix ensures that invoices from Northern Irish customers are now properly included in the EC Sales Report. Previously, these invoices were being excluded from the report, which could lead to incomplete sales data for businesses operating in Northern Ireland.
Original PR description
### Steps to reproduce * install `account_intrastat` * create and confirm an invoice for a Northern Irish customer * open the EC Sales Report You will see that your invoice is not included in the report opw-4123375 Forward-Port-Of: odoo/enterprise#69501
This update corrects the visual appearance of the dropdown arrow (caret) in the Account Reports dashboard filters when users hover over them. The styling was adjusted to match improvements made to similar dropdown elements across the system, ensuring a consistent and polished user experience.
Original PR description
This commit adapts the Account reports's filters styling, following the fix of the record selector's caret positioning made in community. Community: https://github.com/odoo/odoo/pull/180046