Thursday, October 24, 2024
29 changes
Resolved issues and error corrections
This update resolves an issue where users were blocked from synchronizing their online accounts due to a persistent error status. The solution resets the fetching status automatically when transactions are retrieved or through a new button in the online account list view, ensuring smoother synchronization and uninterrupted access to updated financial data.
Original PR description
The field fetching status is used to check if we need to call the synchronization. In case there is an error during the synchronization, the user would be block with his connection. The solution is to reset the fetching status when fetching the transaction or use the new reset button on the list view of the online accounts. task:4262788
This update resolves an issue where clicking 'Insert in spreadsheet' in pivot views incorrectly redirected users to the dashboard without saving. The fix, implemented starting with saas-17.4, completely removes the 'Dashboards' tab from the pivot view, eliminating the error. This ensures users can properly access spreadsheet functionality.
Original PR description
Steps to reproduce: - install Documents and CRM - login as Marc Demo - go to any pivot view - click on "Insert in spreadsheet" - select the Dashboards tab and confirm => boom In this version, the fix is sub-optimal. The user will be redirected to the dashboard, but nothing happens. It's fixed properly starting with saas-17.4 because the code changed and it's mush easier and safer to fix. The Dashboard tab won't appear at all. Task: 4273554
This update fixes an issue where Purchase Orders and Sales Orders generated between companies didn't consistently use the expected arrival or commitment dates. Now, the system will accurately reflect the specified delivery dates when creating counterpart orders in the other company, improving order scheduling and fulfillment accuracy.
Original PR description
When generating either a PO or SO from one company to another, currently the commitment date of a Sale Order or the Expected Arrival of a Purchase Order are not used to generate their counter-part in the other company. This means that if you set the expected arrival of the PO in Company A to 10 days in the future, the SO generated in Company B will still try to deliver it as soon as possible, regardless of the date set. Forward-Port-Of: odoo/enterprise#72586
This update resolves a problem preventing the Social Marketing tour from functioning correctly. The fix addresses an issue with accessing a key input field and updates the tour's triggering mechanism for compatibility across Odoo versions. This ensures a smoother onboarding experience for new users.
Original PR description
Fixed onboarding Social Marketing tour which is not working properly. Reason ====== We're not getting this `'textarea[name="message"]` for some reasons, & there is no `name` attribute in textarea. Also, we removed `extra_tringger` in later version, and we can use `run: 'edit` instead so removed that & used common classes that works on all version. Task-4210376 Forward-Port-Of: odoo/enterprise#71016