Wednesday, December 18, 2024
10 changes · 17.0
Enhancements to existing features
This update ensures our LinkedIn integration uses the latest LinkedIn API version (202411). This upgrade maintains compatibility with LinkedIn's platform and improves the reliability of our social media connections. No new features were added, and the changes are focused on updating API headers as documented by LinkedIn.
Original PR description
This commit upgrades the Linkedin's versioned API to the latest available which is `202411`. As no features has been broken, nor is there any new features impacting the parts of the API we use. Only the headers are updated as explained inside their documentation. task-4273179 Forward-Port-Of: odoo/enterprise#74687
Resolved issues and error corrections
This update resolves a bug where deferred tax dates weren't correctly synchronized between invoice and tax lines. The fix ensures that tax line dates are accurately updated when invoice deferred dates are removed, preventing data inconsistencies. This improves the reliability of tax calculations and reporting.
Original PR description
Steps to reproduce: 1) Via Studio, modify the 'Journal Items' tab to add 'Start date' and 'End date' to the list view 2) Create a purchase tax 3) Create a bill with the tax created in the previous…
Steps to reproduce: 1) Via Studio, modify the 'Journal Items' tab to add 'Start date' and 'End date' to the list view 2) Create a purchase tax 3) Create a bill with the tax created in the previous step 4) Select deferred dates in the future 5) Check the journal items (two lines with deferred dates) 6) Go back to the 'Invoice lines' tab, delete the deferred dates and check the journal items again => one line still present the deferred dates!! Reason: When removing the `deferred_start_date` and the `deferred_end_date` from the invoice line, the newly computed `tax_key` for the tax line(s) will not have the `deferred_start_date` and the `deferred_end_date` fields, by [_get_deferred_tax_key](https://github.com/odoo-dev/enterprise/blob/c2c3a8591b3a5dfa402acb981564e46e0ff4ced9/account_accountant/models/account_move.py#L582). However, since when updating the tax line(s), we merge the old values with the new values (obtained in part from the before mentioned updated key), by this code in [_sync_dynamic_line](https://github.com/odoo/odoo/blob/f3d3e0c612392f1a35b9c131d29b4f3bd70a9d36/addons/account/models/account_move.py#L2599-L2602), and since the new key values of the tax line(s) does not have the `deferred_start_date` and the `deferred_end_date` explicitly set to `False`, and since the old key values have those fields set, merging new values with the old values will keep the old `deferred_start_date` and the `deferred_end_date`, resulting in a mismatch between the deferred dates on the invoice line and the tax lines. Fix: Now, `_get_deferred_tax_key` explicitly set `deferred_start_date` and the `deferred_end_date` to `False` when `tax_repartition_line_id ` is defined, to make sure they override any old `deferred_start_date` and the `deferred_end_date` existing in the old keys. opw-4328465
A previous error occurred when creating planning slots due to missing calendar information for resources. This update corrects the code to handle cases where a resource doesn't have a working calendar, preventing a traceback and ensuring planning slots can be created successfully. This improves the reliability of the planning module.
Original PR description
Currently a traceback is occurring when there is no working time (calendar_id) in resource, while creating a planning slot. To reproduce this issue: 1) Install planning 2) Open any planning slot in…
Currently a traceback is occurring when there is no working time (calendar_id) in resource, while creating a planning slot. To reproduce this issue: 1) Install planning 2) Open any planning slot in Gantt view and redirect to resource from the slot 3) Remove the Working Time of that resource 4) Now try to create a new planning slot for that resource from Gantt view Error:- ``` ValueError: Expected singleton: resource.calendar() ``` Here, `calendar_id` is not required in the resource. So, when the user removes the calendar_id from the resource and tries to create a new planning slot, it leads to the above traceback. In the below line, we try to get calendar_d from the resource if it is available. https://github.com/odoo/enterprise/blob/7847510dc6ad8dec73f01470714aacb0c3510769/planning/models/planning.py#L611-L612 We can resolve this issue by taking calendar_id from the company as it is required. If it fails to get the value from the resource. sentry-6150920391
A bug was preventing users from accessing documents after archiving the default 'Projects' workspace. This update prevents archiving of the projects workspace, resolving the error and ensuring proper document access. This change improves the stability and usability of the documents application.
Original PR description
Steps to reproduce ================== - Archive default "Projects" workspace - Create a new Project - Create a task and attach a file - Click on the smart button to view the document - Go back to the home menu and open the documents app => `Cannot read properties of undefined (reading 'id')` Solution ======== Prevent the archiving of the projects workspace opw-4308132
This update resolves a compatibility problem in the Account Accountant module. It addresses an error that occurs when the Account module isn't updated alongside the Account Accountant module. The fix adds a temporary field to ensure proper functionality until the Account module is updated.
Original PR description
Scenario: - install account without commit (eg. before 3 december 2024): odoo/odoo@d413a9895742594d064084cd6dafbf1f2ec97221 - install account_accountant with commit (eg. after 3 december 2024):…
Scenario:
- install account without commit (eg. before 3 december 2024): odoo/odoo@d413a9895742594d064084cd6dafbf1f2ec97221
- install account_accountant with commit (eg. after 3 december 2024): e4111ac8f817f97b3d6128453659a1014b6db00f
=> Traceback with odoo.tools.convert.ParseError: while parsing
account_accountant/views/product_views.xml:3
Field 'is_coa_installed' used in attrs
({'invisible': [('is_coa_installed', '=', False)]}) must be present
in view but is missing.
Cause:
The change in account_accountant
(e4111ac8f817f97b3d6128453659a1014b6db00f) relies on the change in account (odoo/odoo@d413a9895742594d064084cd6dafbf1f2ec97221) but account_accountant can be installed/updated without updating account.
Fix:
Add a duplicate is_coa_installed field in account_accountant useful if account module is not up to date.
opw-4323694
note: only useful up to saas-17.2, in saas-17.4 the field is automatically added if it's necessary for an attribute.
pr note: issue found when working on an unrelated ticket
Forward-Port-Of: odoo/enterprise#75490This update addresses a technical issue preventing the correct generation of TNT manifest PDFs when using Starshipit in Australia. While the core problem isn't fully resolved, the fix allows stock picking to be marked as 'Done' with tracking number and link visibility for users. The manifest PDF itself remains unavailable.
Original PR description
If Starshipit is configured with TNT service (Australia), the API does not return a pdf field for `orders/manifest` endpoint. This causes the transfer validation process to fail in Odoo. This fix does not resolve the core problem, but it will allow the stock picking to be marked as "Done", with tracking number and link available to the user. The downside is that the manifest PDF will not be available Task: 4195503
This update fixes a bug in the Helpdesk app that previously limited the products displayed on tickets to those linked to the customer's sales orders. Now, all products associated with a contact and their parent company will be visible, ensuring a more complete view for support agents. This improvement enhances the accuracy and usability of the Helpdesk system.
Original PR description
Steps to reproduce:
- Install helpdesk_stock and Studio
- Create 3 contacts, 1 company and two child employees
- Create a quotation for each contact with a different product
- Helpdesk app > Create a ticket
- Add the Product ('product_id') field with studio
- (Under 'Existing Fields' search product)
- (View tab > Show invisible elements > Find product field > untick invisible)
The products from contacts linked to the parent company should appear, but only those related to SOs from the contact itself or its parent company are shown (i.e. We should see all 3 products no matter which contact is set as customer).
This is related to https://github.com/odoo/enterprise/pull/73391, which was a step in the right direction but still insufficient. Unlike that fix however this one is relevant up to master.
opw-4285382
Forward-Port-Of: odoo/enterprise#74361This update fixes an issue where inter-company sales and purchase orders didn't automatically assign a fiscal position. The change removes a redundant setting, allowing the system to correctly calculate and apply the appropriate fiscal position when creating these orders. This ensures accurate accounting and reporting for transactions between companies.
Original PR description
When creating a PO/SO with inter-company rules, the related SO/PO has no fiscal position set, unless having one set on the partner. Removing the `fiscal_position_id` from the values dict allows it to be computed directly at the creation of the related SO/PO Steps: - Have 2 companies A and B - Activate inter-company rules and synchronize sale/purchase orders - With A, create a SO for B, confirm - With B, go to PO and select the related PO newy created -> There is no fiscal position opw-4247948 Forward-Port-Of: odoo/enterprise#73392
This update ensures Odoo correctly identifies the company's currency when synchronizing bank accounts. This is crucial for accurate testing and integration with financial institutions, resolving a previous issue that could lead to incorrect account data. It primarily impacts the account synchronization process.
Original PR description
This commit updates the process to pass the company's currency code to the `_get_accounts` route. By doing so, the server can accurately identify the company's currency. This change is particularly important for supporting testing banks. task-4293992 Forward-Port-Of: odoo/enterprise#75372
This update fixes a problem where tax reports generated as PDFs were displaying cropped columns due to limitations in the PDF generation process. The fix removes unnecessary currency display from report headers, ensuring all data from the table view is accurately included in the PDF output. This improves the clarity and completeness of tax reports.
Original PR description
**Issue:** Some tax reports don't display all data. Last columns may be cropped.  **Expected:** The PDF file should contain all data displayed in the Tax Report table view as is. **Steps to reproduce:** - Activate Accounting app; - Install the Argentina localization; - Move to the Argentine company; - Go to `Accounting` > `Reporting` > `Tax Report`; - Change selection to display some lines (or add invoice lines); - Print PDF report. **Cause:** The columns are cropped because of the global width of the report wkhtmltopdf can't handle correctly. **Fix:** Remove useless currencies' display in headers. Backport improvement (https://github.com/odoo/enterprise/commit/5bbdc059045c1a50c8ef1d6f5f8c9cb76d2d85f9).  Ticket link: https://www.odoo.com/odoo/project/967/tasks/4349604 opw-4349604