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

[13] sale_order_line_chained_move duplicate field #1974

Closed
PedroInfo13 opened this issue Apr 8, 2022 · 5 comments
Closed

[13] sale_order_line_chained_move duplicate field #1974

PedroInfo13 opened this issue Apr 8, 2022 · 5 comments
Labels
question stale PR/Issue without recent activity, it'll be soon closed automatically.
Milestone

Comments

@PedroInfo13
Copy link

Hello @rousseldenis

There is a duplicate field.
You create field related_sale_line_id on module stock.move. But in this module have a field sale_line_id.

I don't know why you do this.

I apreciate if you could explain it to me.

Thanks

@PedroInfo13 PedroInfo13 added the bug label Apr 8, 2022
@rousseldenis
Copy link
Sponsor Contributor

Hello @rousseldenis

There is a duplicate field. You create field related_sale_line_id on module stock.move. But in this module have a field sale_line_id.

I don't know why you do this.

I apreciate if you could explain it to me.

Thanks

In Odoo, indeed there is a sale_line_id. But this is filled in only with the move from out > Customers (the one generated at sale confirmation).

But in case of several operations (two or three steps delivery), the sale_line_id is not filled in.

This module allows to have the full chain of moves generated through the original move with the sale line reference.

I hope this is clear 😃

@rousseldenis rousseldenis added question and removed bug labels Apr 8, 2022
@rousseldenis rousseldenis added this to the 13.0 milestone Apr 8, 2022
@rousseldenis
Copy link
Sponsor Contributor

Note: I didn't want to reuse the sale_line_id field as it should break other processes.

@elvise
Copy link

elvise commented Sep 19, 2023

Hello @rousseldenis
There is a duplicate field. You create field related_sale_line_id on module stock.move. But in this module have a field sale_line_id.
I don't know why you do this.
I apreciate if you could explain it to me.
Thanks

In Odoo, indeed there is a sale_line_id. But this is filled in only with the move from out > Customers (the one generated at sale confirmation).

But in case of several operations (two or three steps delivery), the sale_line_id is not filled in.

This module allows to have the full chain of moves generated through the original move with the sale line reference.

I hope this is clear 😃

Hey @rousseldenis !

As i understood this module mantain the same lines from SO to all chained moves
If it's correct then looks it doesen't work.

I'm testing it in the runbot v14, please che this video:
https://drive.google.com/file/d/1KNsdpCzH8jm7L5S3m00AAm4Q56Yt76h5/view

Please let me know if i'm doing wrong something
Thanks for patience.

@sbouillon
Copy link

Hello @rousseldenis
There is a duplicate field. You create field related_sale_line_id on module stock.move. But in this module have a field sale_line_id.
I don't know why you do this.
I apreciate if you could explain it to me.
Thanks

In Odoo, indeed there is a sale_line_id. But this is filled in only with the move from out > Customers (the one generated at sale confirmation).
But in case of several operations (two or three steps delivery), the sale_line_id is not filled in.
This module allows to have the full chain of moves generated through the original move with the sale line reference.
I hope this is clear 😃

Hey @rousseldenis !

As i understood this module mantain the same lines from SO to all chained moves If it's correct then looks it doesen't work.

I'm testing it in the runbot v14, please che this video: https://drive.google.com/file/d/1KNsdpCzH8jm7L5S3m00AAm4Q56Yt76h5/view

Please let me know if i'm doing wrong something Thanks for patience.

This works in Odoo 13, 14, 15 and 16.

The intent of the module is to record the sale_line_id on the stock.move model. There are no views included in this module so the screen recording doesn't help much but it's definitely recording the sale_line_id on each move line.

image

Copy link

There hasn't been any activity on this issue in the past 6 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 issue 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 Apr 14, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

4 participants