Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[14.0][IMP] rma_sale: improve onchange methods #335

Open
wants to merge 1 commit into
base: 14.0
Choose a base branch
from

Conversation

mt-software-de
Copy link
Contributor

@mt-software-de mt-software-de commented Dec 20, 2022

Changes:

_onchange_partner_id:
Before the order_id was always set to False
Now it's only set to False
if there is no partner selected or
the selected order_id.partner_id is not a child of the current selected partner_id.commercial_partner_id

_onchange_order_id:
if the order_id is set the corresponding partner_fields are getting set

New onchange methods:

_onchange_order_id_product_id:
if the order_id and the product_id is set
it tries to set the move_id with the latest shipped move with the same product_id
as well as the picking_id

_onchange_picking_id:
if the picking and product ist
tries to set the move by selecting the corresponding move

@OCA-git-bot
Copy link
Contributor

Hi @ernestotejeda,
some modules you are maintaining are being modified, check this out!

@mt-software-de mt-software-de force-pushed the 14.0-rma-sale-improments branch 5 times, most recently from adcad0c to b6b2bda Compare December 23, 2022 12:04
@rousseldenis rousseldenis added this to the 14.0 milestone Feb 14, 2023
@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 18, 2023
@github-actions github-actions bot closed this Aug 6, 2023
@mt-software-de
Copy link
Contributor Author

@rousseldenis could you please open this PR again?

@rvalyi rvalyi reopened this Aug 7, 2023
@OCA-git-bot
Copy link
Contributor

Hi @chienandalu, @ernestotejeda,
some modules you are maintaining are being modified, check this out!

@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 13, 2023
- Onchange partner: Unset the order_id
  only if the new partner is not a child of the orders commercial partner
- Onchange order: Set partner fields and procurement group
- Onchange order and product: Change move and picking
- Onchange picking: Change move
@mt-software-de
Copy link
Contributor Author

ping @chienandalu do you have time for a review?

@pedrobaeza
Copy link
Member

You should check how it's done in 16.0, and backport it here, as that's a better way to go IMO.

@mt-software-de
Copy link
Contributor Author

You should check how it's done in 16.0, and backport it here, as that's a better way to go IMO.

Thx. But i can not see any change which i can backport and matching my changes.
Could you be maybe more specific one what you mean?

@pedrobaeza
Copy link
Member

I mean the conversion to computed writable fields.

@pedrobaeza
Copy link
Member

See 54e08e8

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jun 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement needs review stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants