Skip to Content
Menu
This question has been flagged
1 Reply
1588 Views

We are using Odoo 16 Community Version where there is a requirement that will greatly requires a lot of modification in stock.picking model (mainly in "Receipt" part). And we are just new to the framework by the way.


We are considering an option to create another model (header and line) that will contain all our application logic and workflows but once it is posted (after the complicated workflows) then it will transfer the data going to the Odoo default model. In this case, in the application side, the user will not see the original Odoo module but they will only see the custom module via the access groups.


Our end goal is not to break how the Odoo handles the stock movements and adding only our complicated workflow on the top of it and just pass the data from custom module to Odoo default module.


Custom Model Header -> Odoo Default Model Header

Custom Model Line -> Odoo Default Model Line


Appreciate any advise or suggestion regarding this matter. Thanks in advance.

Avatar
Discard
Author

Thanks for your advise Niyas! I think we will go with the inheritance approach.

Best Answer

Hi,

In Odoo there is delegation inheritance, which you can learn more about it from here:  odoo delegation inheritance

But in this case, instead of creating a separate model, will be good to go with original model. Just modify the existing model as per the need and you can make changes on top of it.

Thanks

Avatar
Discard
Related Posts Replies Views Activity
0
Jul 19
2195
1
Aug 24
428
2
Nov 24
762
1
Aug 24
298
3
Oct 23
13197