Tuesday, October 8, 2024
3 changes · saas-17.2
Resolved issues and error corrections
Reloading an import records page now keeps the selected business object, so users are returned to the correct import screen instead of seeing an error or being redirected. This makes record imports more reliable when users refresh the browser or change interface settings during the process.
Original PR description
- In any APP (We would use CRM for the example); - On a multi-record view (Kanban, List, or other); - Click the action menu; - Click on “Import records” dropdown; - Reload the view (either reload the browser, or activate the debug, or change to dark mode on the user menu). Before this commit, an exception was raised, and the default multi-record view was loaded. This occurs because, the client action base import required a model (found in the context) that was lost when reloading. Now, the model is put in the query string of the URL (as active_model), in that way, when reloading, the client action base import will have the needed model. Note that, this is also the behavior of the stock TraceabilityReport client action [1]. opw-3959254 [1] : https://github.com/odoo/odoo/commit/8b3deab679bfee844ccd84c7f4f6f831921365d3
Reloading an import screen now keeps users on the same import page instead of briefly showing an error and sending them back to the list or kanban view. This preserves the user's workflow and prevents confusion during record imports.
Original PR description
- Go to CRM app - Click on the action menu --> Import records --> Import screen will appear - Reload the page a traceback will occur which will disappear quickly (you can see it in console) - It redirects you back to the kanban view which is not correct Before this commit, on reloading the import screen page a traceback was occuring which redirects back to the kanban/list view. This occurs because the ImportAction lost the current model at reload (resModel). Now, the ImportAction will update the state of action using updateActionState prop, to add the resModel to the url (as a query param), and be able to restore the full state at reload. Task-3959254 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Pivot table header menus now close again after choosing a grouping option. This prevents users from adding multiple groupings from a stale menu state, which could lead to incorrect pivot table results.
Original PR description
Before https://github.com/odoo/odoo/pull/137691, select a groupby in the dropdown of a pivot header would close the dropdown. Now the dropdown stays open and it is possible to add several row/col groupbys at the same time but the pivot model is not updated correctly because the update of the model is based on the groupId of the header for which the dropdown was opened. The simpler/best solution to that problem is to restore the previous behavior. Task ID: 3985217