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] sale_import_base: backport from v16 #94

Draft
wants to merge 20 commits into
base: 14.0
Choose a base branch
from

Conversation

clementmbr
Copy link
Member

@clementmbr clementmbr commented Jan 22, 2025

As I want to make a sale_import_amazon module for v14 but using the work I did on v16, I need a v14 of sale_import_base that is closer to the version 16 of the module.

So in this PR I added all the v16 commits from the branch that is currently being pushed to OCA/sale-channel, and also @hparfr 's last commit.

I made also the necessary backport commits to be able to use this v16 version in a v14 Odoo.

As sale_import_base depends on sale_channel, sale_channel_partner and queue_job_chunk, it's important to note that this module's version is based on :

sebastienbeau and others added 19 commits January 22, 2025 13:08
…make sale.import.service.sale an Abstract Model
…erge and always have 2 distinct addresses

In case you want to update the delivery adresse after the creation of the sale order, it is easier to already have distinct addresses between delivery and invoicing.
Else one should create a new address, update the sale order, update the delivery order...
In the future, it  could become an option on channel or company instead of this hook that require an override to change the behavior
code is renamed ref in v16
but there is also a code in the same table in v16
this code prevent an openupgrade failing because of already
existing column (code)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants