Daily updates from Odoo
Monday, October 28, 2024
14 changes · 17.0
New functionality added to Odoo
This update enables the creation of Factura B invoices for customers located outside Argentina. This is required to comply with Argentinian tax regulations for international sales, ensuring our system supports businesses operating in the Latin American market. The change leverages existing logic for foreign sales to streamline the process.
Original PR description
### Description of the issue/feature this PR addresses: It is needed to be able to create Factura B for a foreign customer. Legal reference: Here is some useful documentation : https://servicioscf.afip.gob.ar/publico/abc/ABCpaso2.aspx?id=8555970 https://www.afip.gob.ar/EspaciosdeDialogoInstitucional/documentos/Acta-15-Espacio-de-Dialogo-AFIP-Camaras-Empresariales-14-11.pdf ### Current behavior before PR: It is not possible to create Factura B for a foreign customer. ### Desired behavior after PR is merged: It is possible to create Factura B for a foreign customer. Task Adhoc side: 30008 Task latam side: 913 Forward-Port-Of: odoo/enterprise#71562
Resolved issues and error corrections
This update fixes a translation issue within the Spreadsheet Edition of Odoo, ensuring breadcrumb tooltips are accurately displayed in multiple languages. This improves the user experience for international users and maintains consistent branding across different locales. The change addresses a minor usability concern.
Original PR description
opw-4160838 Community: https://github.com/odoo/odoo/pull/184555
This update resolves a bug where the mail-chatter dropzone remained open after dragging a document to a folder. The fix removes a technical restriction that was preventing the dropzone from closing, improving the user experience when moving documents.
Original PR description
Steps to reproduce: 1. select a document 2. open chatter 3. drag(preview part) and drop to the others folder 4. the mail-chatter-dropzone remains open Technical Reason: Removing the unnecessary stop propagation on the search panel's document drop event as it was preventing it from being caught by the window keeping the chatter drop zone open. After this commit: The mail-chatter-dropzone will be closed after being moved to drag documents to the folders. Task-4268738
This update fixes an issue where timesheet hour calculations were inaccurate due to using UTC time zones. By adjusting the calculation to reflect the user's local calendar time zone, the system now correctly determines under/overtime hours, ensuring accurate timesheet reporting. This improves the reliability of timesheet data.
Original PR description
Steps ----- - Install timesheet_grid - Set monday as the first day of the week in the language settings - Set the timezone of the user's working schedule to a more advanced timezone, e.g. UTC+10 - Go to Timesheets and add some hours on monday -> The under/over time is calculated relative to a lower number of hours than the real number of working hours for that day. Cause ----- `get_daily_working_hours` uses UTC's start/end of day for the start and end of the period, causing some working hours near the start/end of the period to be missed. opw-4163183
This update resolves a bug in the Balance Sheet report where a previously set threshold for prefix groups was incorrectly restored when opening variants. This prevented the report from calculating correctly with certain configurations. The fix ensures the threshold is always initialized from the appropriate field, improving report accuracy.
Original PR description
To reproduce the issue: 1) Set a prefix group threshold of 2000 on the Generic Balance Sheet 2) Modify the groupby of the Receivable line of that report so that it does account_id,id 3) Duplicate the…
To reproduce the issue:
1) Set a prefix group threshold of 2000 on the Generic Balance Sheet 2) Modify the groupby of the Receivable line of that report so that it does account_id,id 3) Duplicate the report ; modify the duplicate to:
- Make it a variant of the Generic BS
- Set its prefix group threshold to 3 4) Ensure at least 3 move lines exist in the same period for the Receivable account 5) Open the Balance Sheet. By default, the Generic one will be shown 6) Switch to the duplicate you made in 3).
7) Unfold both levels of the Receivable line.
====> Prefix groups aren't used, while the number of move lines reaches the threshold value.
This happens because the variant is opened from the Generic BS. So, options have first been generated and kept in the session for the Generic BS. When openin the variant, it receives the previously generated options as previous_options, and restores the threshold originally defined on the Generic BS.
We don't want to restore the threshold for previous options, so we just remove that code and now always initialize it to the value contained in the apporpriate field when computing the options.A recent change in Belgium's time zone rules caused a test to fail. This fix ensures the test consistently uses UTC time, eliminating discrepancies caused by timezone offsets. This prevents inaccurate test results and ensures the reliability of our project management features.
Original PR description
Before this commit, the test `test_editing_task_planned_date` was written by using the belgium timezone but this test starts failing after the end of the summer time in belgium timezone since inside that test, the timezone used is the one used of the current calendar set on the company and/or the timezone set on the current user, that is the belgium one. And so, due to the change of the hours in belgium timezone to now use "winter time" the offset between the `datetime.now` with belgium timezone and the one using utc timezone is no longer 2 hours but 1 hour. Because of that the assets are totally wrong because the expected results are fixed and do not take into account the offset could change. This commit makes sure the test uses only utc as timezone to avoid using offset between 2 timezones since the asserts are fixed and not dynamic according to the offset between 2 timezones. runbot-104873
This update corrects a visual issue in the Odoo Studio application where the 'previous' button in the navigation bar was incorrectly positioned. This ensures a consistent and user-friendly experience when creating new applications within Studio. The fix improves the overall usability of the Studio interface.
Original PR description
Before this commit currently when creating a new app using Studio the previous button icon in the navbar appears in the wrong direction After this commit The previous button icon should appear in the right direction Task - 3845561 Forward-Port-Of: odoo/enterprise#61835
This update resolves an issue where a line was incomplete when creating applications using the Odoo Studio. The commit ensures that all necessary fields are correctly populated during app creation, improving the user experience and preventing data inconsistencies. This change was part of a larger effort to enhance the Studio's functionality.
Original PR description
Before this commit: while creating the app for the 'Suggested features for your new model' title the line is not completed. After this commit: the line should be completed. Task:-3845561 Forward-Port-Of: odoo/enterprise#61824
This update resolves an issue where delivery chatter was incorrectly posted to multiple pickings after a sale order was validated with a new delivery. The fix ensures chatter is only logged on the picking that was successfully validated, improving order tracking accuracy. This prevents confusion and ensures data consistency.
Original PR description
**Current behavior:** Using the DHL delivery shipping module, if you complete a sale order's delivery and then add new product to the order and, again, validate the new delivery, the shipping chatter…
**Current behavior:** Using the DHL delivery shipping module, if you complete a sale order's delivery and then add new product to the order and, again, validate the new delivery, the shipping chatter will be posted in all of the sale order's pickings. **Expected behavior:** The chatter should only be posted in the picking which was actually validated. **Steps to reproduce:** *Install delivery_dhl and l10n_be_hr_payroll* *Swap to My Belgian Company* *Duplicate the My Belgian Company partner record, giving it new unique values where necessary (VAT, address, etc.)* 1. Create a new sale order to the copied Belgian company 2. Add some storable product and add DHL EU shipping to the order (only DHL connector working) 3. Confirm the order, and validate the delivery 4. Back on the sale order, add another order line and save 5. Validate the new delivery, see that the delivery chatter is posted on both deliveries **Cause of the issue:** The message is currently logged on `sale_id.picking_ids`. **Fix:** Change the line in question to only log the message on the currently iterated over picking, as well as any relevant, previously created ones (e.g., in a multistep route context). opw-4059145 Forward-Port-Of: odoo/enterprise#71441
This update fixes a potential issue where communication text after processing could incorrectly include a forward slash. The code has been reorganized to improve reusability and testability, and the function is now used across multiple payment modules. Deprecated functions have been removed to streamline the system.
Original PR description
This commit aims to fix an issue in the sanitize_communication function and move its logic to the account_batch_payment module to improve reusability and testability. The function trims the communication text after removing the '/' characters. However, if the communication text contains '/' and is truncated, the '/' could end up at the end of the string (see tests for more examples). The solution is to remove the '/' after truncating the text. Additionally, the sanitize_communication function has been moved to the account_batch_payment module, since this module is a dependency for both account_sepa and account_sepa_direct_debit, these two modules can now use it as well. The functions sanitize_communication and _sanitize_communication have been marked as deprecated and will be removed in the master branch. opw-4220421 Forward-Port-Of: odoo/enterprise#71552
This update resolves a technical issue that caused tracebacks when creating GST return periods without specifying a month or quarter. The system now gracefully handles missing month/quarter data, preventing errors and ensuring smoother GST return period creation. This improves the reliability of the Odoo Enterprise system for Invoicing reports.
Original PR description
Before this commit: - Creating a GST return period with a quarterly periodicity without selecting a quarter will raise a traceback. - Creating a GST return period with a monthly periodicity without…
Before this commit: - Creating a GST return period with a quarterly periodicity without selecting a quarter will raise a traceback. - Creating a GST return period with a monthly periodicity without selecting a month will raise a traceback. Reason: - While calculating the start_date and end_date of the quarterly return period: `period_start = fields.Date.context_today(self).replace(day=1, month=int(record.month), year=int(record.year))` If there is no month, then int(record.month) will return 0 and The month should be between 1 and 12, so it will raise an error. - While calculating the start_date and end_date of the monthly return period: `period_start = fields.Date.context_today(self).replace(day=1, month=int(record.quarter), year=int(record.year))` If there is no quarter, then int(record.quarter) will return 0 and The month should be between 1 and 12, so it will raise an error. After this commit: - The start_date and end_date will not be calculated if a month or quarter is not defined for the monthly or quarterly return periods. Traceback - https://pastebin.com/LyKUDrH5 Task-4243468 Forward-Port-Of: odoo/enterprise#71883
This update resolves a bug on mobile devices where the document inspector was unexpectedly opening repeatedly when navigating between documents. The fix corrects a logic error in the code that caused the inspector to open unnecessarily, ensuring a smoother document viewing experience.
Original PR description
Steps to reproduce: 1. Go to documents on mobile 2. Click on doc thumbnail 3. The inspector open where preview should open When the preview is open, click on an arrow to see the previous or the next doc 1. The inspector opens again where the previous or next should Technical Reason: In 'documents_inspector.js' file, a condition set only open the inspector if there is only one selected element, so every time it get executed and opens the inspector. After this commit: 1. Click on a doc thumbnail, the preview will open. 2. When the preview is open, click on an arrow to see the previous or the next doc will not open the inspector. Task-3919285 Forward-Port-Of: odoo/enterprise#62957
This update resolves a minor typo in the Japanese accounting module (l10n_jp_zengin). The fix ensures that all messages displayed to users are grammatically correct and professional, improving the overall user experience. This change has no impact on core functionality.
Original PR description
X-original-commit: 698b81c
Accounting reports now properly translate filter options into different languages. Previously, filter labels like "Only Show Unreconciled Entries" were not being translated when users switched to languages like Danish. This fix ensures all filter options display in the user's selected language in both screen reports and PDF exports.
Original PR description
The problem: In the accounting reports, filter options were not being translated. Steps to reproduce: 1. Install and change to the Danish language. 2. Navigate to Accounting > Reporting > Partner ledger (Kontoudtog) 3. Activate the filter "Only Show Unreconciled Entries" (Vis kun ikke udlignede posteringer) 4. Generate the PDF report. Why it was happening: The array `extra_options` was built dynamically by concatenating raw python strings to it. Those raw strings will not be translated. The fix: Now, we create local variables for each string, using the syntax `<t t-set="label_raw_string">Raw String</t>` which makes the string `label_raw_string` translatable, then we append it to `extra_options`. opw-4213562