odoo/odoo#247232
Created by Jérôme Belpaire (beje)
Statuses:
- legal/cla: Contributor License Agreement check
- ci/runbot: Odoo Test Suite
- ci/upgrade_enterprise: Test upgrades for enterprise master
- ci/style: Optional style check. Ignore it only if strictly necessary.
- ci/security: Required security check. Can only be ignored by security team.
- label
- odoo-dev:master-imp-documents-accounting-improve-server-actions-and-demo-documents-beje
- head
- 320891a2d03511cb64c25f73887650257821d702
- merged
- 1 day ago by SM Learn, Stéphane Debauche (std)
| odoo/odoo | odoo/enterprise | odoo/upgrade | |
|---|---|---|---|
| master | #247232 | #97362 | #9044 |
[FIX] base: match server actions visual sort with execution
Currently, the server actions Kanban view implicitly sorts records by sequence and then by ID. This behavior is triggered automatically by the web client when a field with the 'handle' widget is present and no default order is specified in the view.
However, the backend execution logic for multi-actions (ir.actions.server) processes actions based on 'sequence' and then 'name' (alphabetical).
This creates a discrepancy when multiple actions share the same sequence number: the user sees them sorted by creation order (ID) in the interface, but they are executed alphabetically. This leads to confusion as the visual hierarchy does not accurately represent the flow of operations.
This commit ensures the view aligns with the backend model's sorting logic, so that the visual order in the frontend matches the actual execution order.