Skip to content

[18.0][FIX] purchase_order_line_sequence: avoid one onchange per line on reorder - #3317

Open
ROBBYHOOD9 wants to merge 1 commit into
OCA:18.0from
ecosoft-odoo:18.0-fix-purchase_order_line_sequence-reorder-onchange
Open

ROBBYHOOD9 wants to merge 1 commit into
OCA:18.0from
ecosoft-odoo:18.0-fix-purchase_order_line_sequence-reorder-onchange

Conversation

@ROBBYHOOD9

Copy link
Copy Markdown
Contributor

visible_sequence depends on sequence, so dragging a line sends one onchange
per line at once. On large orders requests get reset ("Connection lost").

Drop the sequence dependency and recompute in write() instead.

Assisted-by: Claude Code (Claude Opus 5.5)

@OCA-git-bot OCA-git-bot added series:18.0 mod:purchase_order_line_sequence Module purchase_order_line_sequence labels Nov 20, 2026
…order

visible_sequence depended on sequence, so reordering lines by drag and
drop sent one onchange per line. On large orders this floods the server
and requests are reset (Connection lost). Recompute it in write instead.
@ROBBYHOOD9
ROBBYHOOD9 force-pushed the 18.0-fix-purchase_order_line_sequence-reorder-onchange branch from 1cbe13c to 592734b Compare November 20, 2026 09:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mod:purchase_order_line_sequence Module purchase_order_line_sequence series:18.0

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants