Friday, March 15, 2024
4 changes · saas-17.1
Resolved issues and error corrections
This update resolves an issue where the reconciliation widget incorrectly selected a partner when multiple partners shared the same name. Previously, the last created partner was always used, even if the payment originated from a different partner. Now, the system avoids selecting a partner when names are identical, ensuring accurate reconciliation reporting.
Original PR description
In a single database, you could have two partners who are called John Doe. Before this commit, any statement line where the partner_name was set with 'John Doe' would return the last one being…
In a single database, you could have two partners who are called John Doe. Before this commit, any statement line where the partner_name was set with 'John Doe' would return the last one being created, due to the _order attribute on res.partner model, even if the statement line was generated from a payment of the other 'John Doe' (ie first one created). With this commit, we ensure that the wrong partner is not selected, in case we cannot differentiate one from the other. Description of the issue/feature this PR addresses: In case you have two partners with the same name in your DB, and you import a bank statement having a payment from the first created partner, the reconciliation widget will display a filter matching invoices of the last created partn. Current behavior before PR: Last partner created is selected for the filter. Desired behavior after PR is merged: No partner is selected for the filter if we have multiple ones sharing the same name. Enterprise test PR: odoo/enterprise#57846 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157470 Forward-Port-Of: odoo/odoo#155986
This update allows users to register payments against multiple invoices using the payment wizard. Previously, the wizard was limited to single invoices and specific payment types. Now, users can select any bank journal, even when processing payments for multiple invoices, improving payment flexibility.
Original PR description
Create an invoice to partner A, confirm Create an invoice to partner B, confirm From Invoice list view, select just one invoice and hit register payment It will be possible to only select journals having inbound payment method Now select both invoices and hit register payment It will be possible to select any Bank journal, even if both invoice payment should be incoming opw-3757686 Forward-Port-Of: odoo/odoo#157665 Forward-Port-Of: odoo/odoo#156578
This update addresses several critical issues within the Odoo spreadsheet component, ensuring smoother operation and data integrity. Specifically, it resolves problems with chart resizing, sheet deletion, and renaming sheets in read-only mode. This improves the overall user experience and stability of the spreadsheet functionality.
Original PR description
### Contains the following commits: https://github.com/odoo/o-spreadsheet/commit/bd0c9e005 [REL] 17.1.8 https://github.com/odoo/o-spreadsheet/commit/66c66a61d [FIX] figures: deleting a sheet will remove all figures https://github.com/odoo/o-spreadsheet/commit/3ceba1d93 [FIX] sheet_interactive: rename sheet in readonly mode https://github.com/odoo/o-spreadsheet/commit/c1bd3c971 [FIX] FiguresContainer: chart resizing broken
This update ensures that UTM tracking codes are correctly saved in cookies after a user accepts the website cookie bar. Previously, the cookie bar deactivated cookies, preventing UTM data from being captured. This fix resolves issues with tracking website traffic and accurately attributing sales through UTM links, especially when users navigate from marketing campaigns.
Original PR description
Current behavior: --- When the cookie bar is activated, the cookies are deactivated by default, unless you click on I agree. This prevents UTMs from being set in the cookies Steps to reproduce: ---…
Current behavior: --- When the cookie bar is activated, the cookies are deactivated by default, unless you click on I agree. This prevents UTMs from being set in the cookies Steps to reproduce: --- 1. Install website_sale and sale_management 2. Go to Settings/Website 3. Activate Cookies Bar 4. Go to Link Tracker 5. Create a new link 6. Set the url as .../shop and Medium as LinkedIn 7. Open a private tab 8. Go to the tracked URL 9. Click on I agree on the cookie bar 10. Buy a product 11. Go back to Sales 12. Find the last public user quotation 13. Go to other info 14. Medium is empty Cause of the issue: --- UTMs are read from the cookies. When you activate the cookie bar, the cookies are deactivated by default. So when you go to the tracked url, and it redirects you to the page, it doesn't put the info from the url in the cookies. Clicking on I agree doesn't resolve the issue because it doesn't reload the page. Fix: --- When closing the cookie bar, forcing the info in the URL to be stored in the cookies if the key is a UTM. opw-3681927 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#157711 Forward-Port-Of: odoo/odoo#154924