Skip to Content
  2. Mailing Lists
  3. Contributors
  4. Re: RFC: Manual ordering of pickings in Shipment Advice (One2many)

Archives

Re: RFC: Manual ordering of pickings in Shipment Advice (One2many)

Hello rrebollo,

As you created an issue, here is the link for anyone that would like to comment on this


kr
J-E

Le mer. 14 janv. 2026 à 14:52, Rolando Pérez Rebollo <notifications@odoo-community.org> a écrit :

Hello OCA contributors,

We are using shipment_advice, an OCA addon from stock-logistics-transport, which groups stock.picking records via a One2many relation.

Constraints

  • One Shipment Advice → many pickings

  • Each picking belongs to exactly one Shipment Advice

  • The One2many relation is core to the addon and cannot be changed

Problem
We need to implement a manual, user-defined ordering of pickings within a Shipment Advice.

  • Order is arbitrary

  • Not derived from existing fields (dates, priority, state, etc.)

  • Must be persistent and respected in views and business logic

  • Native One2many does not support manual ordering

RFC
What is the recommended Odoo/OCA pattern to:

  • Persist a manual order per Shipment Advice

  • While keeping the existing One2many relation untouched

Feel free to challenge any of the assumptions or constraints above if you see a better approach.

Thanks,

\rrebollo


_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Jacques-Etienne Baudoux - 03:41 - 14 Jan 2026

Reference

  • RFC: Manual ordering of pickings in Shipment Advice (One2many)

    Hello OCA contributors,

    We are using shipment_advice, an OCA addon from stock-logistics-transport, which groups stock.picking records via a One2many relation.

    Constraints

    • One Shipment Advice → many pickings

    • Each picking belongs to exactly one Shipment Advice

    • The One2many relation is core to the addon and cannot be changed

    Problem
    We need to implement a manual, user-defined ordering of pickings within a Shipment Advice.

    • Order is arbitrary

    • Not derived from existing fields (dates, priority, state, etc.)

    • Must be persistent and respected in views and business logic

    • Native One2many does not support manual ordering

    RFC
    What is the recommended Odoo/OCA pattern to:

    • Persist a manual order per Shipment Advice

    • While keeping the existing One2many relation untouched

    Feel free to challenge any of the assumptions or constraints above if you see a better approach.

    Thanks,

    \rrebollo


    by Ing. Rolando Pérez Rebollo - 02:50 - 14 Jan 2026