Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Re: Sale Order packaging without specify products
    Update: 

    Forgive me I have mistaken "packaging" and "package" business logic.

    I think that if I want to provide this feature and keep a decent level of scalability/extensibility I need to:

    1 - make possible for backend user to generate n° stock.quant.package objects from a sale order (simply adding a one2many relation with stock.quant.package, in Sale Order)

    2 - use stock_quant_package_dimension to allow setting dimensions and automatic volume calculation from the Sale Order as well

    3 - when the outgoing picking is generated by confirming order (as I previously said we have a really simplified picking process but this part will still probably be a bit tricky in case of picking and/or order cancel)
       3a) all sale order packages will be automatically attached to the outgoing picking by setting them on "picking.package_ids"
       3b) all the products will automatically be put in a single pack, the other packs will be "fake packs" in the sense that they will not store any products but still has dimensions

    This will not provide huge advantages by itself, but definitely better than having separate model to manage "shipping packs" delivery rate and tracking. Tracking will not be really accurate as it doesn't target products, but the rate we need to get is always based on taxable weight, so it should be a decent solution. I'm still not sure if it's worth to manage "package_id" on stock.quant.package, if I am not wrong that's needed in order to print shipping label.

    If you have any kind of suggestions that comes from experience in developing similar workflows (TLDR generating packages from sale order without having to specify the pack content) it will be helpful for sure.

    Thanks,

    Francesco Ballerini


    Privo di virus.www.avast.com

    Il giorno dom 10 dic 2023 alle ore 23:27 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:
    Hello, 

    TLTR 

    I am searching (for Odoo v14) a module which add a one2many on sale order, linking SO with multiple product packaging objects.

    More details

    Long time ago I've been asked to make implementations for a workflow when we need to define product packaging objects in a Sale Order so that we can store packaging dimensions, compute the proper rate and send some info to the carrier. 

    We don't want to define any package on sale order line, or link specific products to a packaging: we just need to define an X number of packaging objects related to the sale order. 
    Also, we want to do it from sale order because we adjust product lines accordingly to the "on hand quantity" directly on sale order, before picking generation, plus we don't manage backorder in the classic Odoo way, so picking is basically only "validate" for us.

    I already have developed the workflow, but it's not properly integrated with some Odoo modules/models so I want to make some refactors and possibly integrate it with some OCA modules like product_packaging_dimension to use already implemented features when possible.

    But I did not find anything covering this, possibly did I miss it?

    Thanks

    Francesco Ballerini

    Privo di virus.www.avast.com
    by Francesco Ballerini - 09:04 - 12 Dec 2023
  • Re: Packaging

    HI Jairo,

    thanks for your reply.

    Unfortunatly this does not cover the needs. When you enter a product to the sales order it only adds the packaging if the quantity of the product divided by the number of products inlcuded is an integer value. For example… a package with 6 is defined.

    In SO if you add 6 or 12 or 18 it adds the packaging. If you add 8 it will not add any packaging. And i want to have the package reusable.

     

    I will do some further testing. But anyway. Thanks for the input!

     

    All the best

    Nils

     

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Inhaber (Owner): Nils Coenen 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

     

    Von: jairo <notifications@odoo-community.org>
    Antworten an: Contributors <contributors@odoo-community.org>
    Datum: Montag, 11. Dezember 2023 um 13:32
    An: Contributors <contributors@odoo-community.org>
    Betreff: Re: Packaging

     

    El vie, 08-12-2023 a las 17:32 +0000, Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT escribió:

    i am looking for a way to attach packaging products (storable, with selling price) to a sales order automatically, when a specific product is selected.

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

    by Nils Coenen - 10:26 - 12 Dec 2023
  • Re: Packaging
    El vie, 08-12-2023 a las 17:32 +0000, Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT escribió:

    i am looking for a way to attach packaging products (storable, with selling price) to a sales order automatically, when a specific product is selected.

    by Jairo Llopis - 01:30 - 11 Dec 2023
  • Sale Order packaging without specify products
    Hello, 

    TLTR 

    I am searching (for Odoo v14) a module which add a one2many on sale order, linking SO with multiple product packaging objects.

    More details

    Long time ago I've been asked to make implementations for a workflow when we need to define product packaging objects in a Sale Order so that we can store packaging dimensions, compute the proper rate and send some info to the carrier. 

    We don't want to define any package on sale order line, or link specific products to a packaging: we just need to define an X number of packaging objects related to the sale order. 
    Also, we want to do it from sale order because we adjust product lines accordingly to the "on hand quantity" directly on sale order, before picking generation, plus we don't manage backorder in the classic Odoo way, so picking is basically only "validate" for us.

    I already have developed the workflow, but it's not properly integrated with some Odoo modules/models so I want to make some refactors and possibly integrate it with some OCA modules like product_packaging_dimension to use already implemented features when possible.

    But I did not find anything covering this, possibly did I miss it?

    Thanks

    Francesco Ballerini

    Privo di virus.www.avast.com
    by Francesco Ballerini - 12:24 - 11 Dec 2023
  • Packaging

    Dear OCA’ers,

    i am looking for a way to attach packaging products (storable, with selling price) to a sales order automatically, when a specific product is selected.

    I already checked the sale_attach_product of the sales_workflow repo, but this doesnt seem to cover the needs in this case. It adds the same quantity of the parent product.

     

    I also checked the product-pack repo. But the flow seems to be the opposite way. You can select a pack in the sales order, which adds the pack components to the SO.

     

    What i want to achieve… Add a product „Product 1“ to sales order (e.g. quantity of 20).

    Automatic addition of the packaging product „Packaging Product“ to the sales order (quantity = quantity of Product 1 / variable then round up, so in this case e.g. 20/6=3,33 -> 4).

    Ideally this is related only to selected delivery methods or route. So for example: When the delivery is done by the company itself, the packaging product should be apllied to the sales order. If the delivery is performed by a shipping provider, the mechanism should not apply.

     

    I will go ahead checking the stock-logistics-warehouse repo. But if there is something helpful crossing your minds, feel free to share these thoughts…

     

    Cheerio

    Nils

     

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 
    Ust.-Idnr. (VAT-ID): DE341437044 

     

    by Nils Coenen - 06:31 - 8 Dec 2023
  • RE: New way to create repositories and add maintainers

    Thank you Enric! Thank you, Simone!

     

    Denis questions is interesting, should we know be subscribed in the repo for all requests?

     

    Thanks again!

     

    Best Regards,

    Rafael

     

     

    De: Roussel, Denis <notifications@odoo-community.org>
    Enviado el: viernes, 17 de noviembre de 2023 8:58
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: New way to create repositories and add maintainers

     

    Thanks for this.

     

    Question: is it scheduled to have a mechanism to warn current PSC members of new members application?

     

    Thanks

     

    Le jeu. 16 nov. 2023, 22:58, Enric Tobella Alomar <notifications@odoo-community.org> a écrit :

    Hello Community,

     

    On the last weeks, Simone and myself have been working on a new tool that can be used to create repositoires and add maintainers. Right now, everything will be managed inside Github: https://github.com/OCA/repo-maintainer-conf/

     

    So, if you want to add yourself as a PSC, you just need to find the PSC team on https://github.com/OCA/repo-maintainer-conf/tree/master/conf/psc and add your github token with a Pull Request. Once it is merged, you will be added as PSC.

     

    Also, you can ask for the creation of a new repo and even change the default branch of the repo there. For example: https://github.com/OCA/repo-maintainer-conf/blob/master/conf/repo/account.yml#L1-L18

     

    This will improve the transparency and clean-up the management of it.

     

    I hope you all enjoy the changes.

     

    Kind regards,

     

    --

    Enric Tobella Alomar

    CEO & Founder

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

    by "Rafael Blasco" <rblasco@rbnpro.com> - 05:28 - 2 Dec 2023
  • Re: Suggesting Samuel Macias to various PSC
    Maybe. He has been reviewing mostly and delegating migration efforts to V17 to 2 of our interns.

    MAXIME CHAMBREUIL
    DIRECTOR GENERAL LATAM
    Calendario
    T:     +52 (800) 953-2012 #5200
    M: +52 (442) 114-9164 | WhatsApp
    C: MChambreuil@OpenSourceIntegrators.com
    Av. Antea 1032, Piso 4 Local 8, Colonia Jurica
    Santiago de Querétaro, Querétaro, 76100, México

    Analizar. Optimizar. Automatizar. Transicionar.



    On Wed, Nov 29, 2023 at 2:00 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
    I still do not see too many pull requests from him in the commented repositories. Don't you think it's a bit soon to propose it?

    Regards.

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

    by Maxime Chambreuil - 09:25 - 29 Nov 2023
  • Re: Suggesting Samuel Macias to various PSC
    I still do not see too many pull requests from him in the commented repositories. Don't you think it's a bit soon to propose it?

    Regards.
    by Pedro M. Baeza - 09:00 - 29 Nov 2023
  • Re: Suggesting Samuel Macias to various PSC
    Hi, in order to do that, he should open a PR on repo-maintainer-conf adding himself on the righf psc teams he will find in the conf folder

    PSC approval is managed there

    On Wed, 29 Nov 2023, 19:51 Maxime Chambreuil, <notifications@odoo-community.org> wrote:
    Hello OCA Contributors,

    I would like to recommend my colleague Samuel Macias to the following PSC:
    Thank you!

    MAXIME CHAMBREUIL
    DIRECTOR GENERAL LATAM
    Calendario
    T:     +52 (800) 953-2012 #5200
    M: +52 (442) 114-9164 | WhatsApp
    C: MChambreuil@OpenSourceIntegrators.com
    Av. Antea 1032, Piso 4 Local 8, Colonia Jurica
    Santiago de Querétaro, Querétaro, 76100, México

    Analizar. Optimizar. Automatizar. Transicionar.

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

    by Enric Tobella Alomar - 07:56 - 29 Nov 2023
  • Suggesting Samuel Macias to various PSC
    Hello OCA Contributors,

    I would like to recommend my colleague Samuel Macias to the following PSC:
    Thank you!

    MAXIME CHAMBREUIL
    DIRECTOR GENERAL LATAM
    Calendario
    T:     +52 (800) 953-2012 #5200
    M: +52 (442) 114-9164 | WhatsApp
    C: MChambreuil@OpenSourceIntegrators.com
    Av. Antea 1032, Piso 4 Local 8, Colonia Jurica
    Santiago de Querétaro, Querétaro, 76100, México

    Analizar. Optimizar. Automatizar. Transicionar.

    by Maxime Chambreuil - 07:51 - 29 Nov 2023
  • Re: Odoo Test framework and rollback issue
    Thank you all for your feedback.

    So I will (when possible) try to split my tests and re-arrange their content so that the exception assertions are (is) processed at the very end.
    Anyway, I will always add the self.cr.savepoint() in the with context (looking at the Odoo 14.0 code, clear_upon_failure is automatically called by assertRaises).

    --
    Yann PAPOUIN


    Le ven. 17 nov. 2023 à 13:42, Pedro M. Baeza <notifications@odoo-community.org> a écrit :
    Holger Brunn has pointed to me that there's a way to recover properly in SavepointCase tests after a raise:


    You have to add the reset_on_failure to your `with` statement. And it seems that since v15, the savepoint is enough.

    Anyway, think twice about piling a lot of asserts in the same test, being raise or not, as having an early failure makes you to iterate several times until having a pass one, although testing flows is usual to have that sequential asserts.

    Thanks for the extra insights, Holger!

    Regards.

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

    by Yann Papouin - 02:51 - 23 Nov 2023
  • Re: [SPAM] Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
    Hi Pedro,

    I did not get your suggestion either, I’ll move it to open upgrade as you suggest, thanks ! 

    Robin Keunen 
    Coop IT Easy 
    robin@coopiteasy.be 
    +32 488 86 57 40
    On 22 Nov 2023, 16:04 +0100, Francesco Foresti <notifications@odoo-community.org>, wrote:
    @Pedro I didn't receive the email as well. Sometimes newsletter skips some replies (maybe even questions?) and that's not really ideal as there's no feedback on that...

    Maybe it could be a good reason to switch to https://github.com/orgs/OCA/discussions ? Not to hijack this thread :)

    Cheers

    Il giorno mer 22 nov 2023 alle ore 15:47 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
    Did you receive my mail stating the regular procedure?

    > Add the merge of the module in OpenUpgrade, and include the migration script there.

    Regards.

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



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

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

    by Robin Keunen - 04:25 - 22 Nov 2023
  • Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
    @Pedro I didn't receive the email as well. Sometimes newsletter skips some replies (maybe even questions?) and that's not really ideal as there's no feedback on that...

    Maybe it could be a good reason to switch to https://github.com/orgs/OCA/discussions ? Not to hijack this thread :)

    Cheers

    Il giorno mer 22 nov 2023 alle ore 15:47 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
    Did you receive my mail stating the regular procedure?

    > Add the merge of the module in OpenUpgrade, and include the migration script there.

    Regards.

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



    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 04:04 - 22 Nov 2023
  • Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
    Did you receive my mail stating the regular procedure?

    > Add the merge of the module in OpenUpgrade, and include the migration script there.

    Regards.
    by Pedro M. Baeza - 03:45 - 22 Nov 2023
  • Re: [SPAM] Re: Porting a module from the OCA whose feature is now in Odoo CE
    Thanks for the suggestion. I ended up doing that but for version 13 (PR) since the Responsible field was introduced in that version.

    Robin Keunen 
    Coop IT Easy 
    robin@coopiteasy.be 
    +32 488 86 57 40
    On 21 Nov 2023, 23:12 +0100, Adam Heinz <notifications@odoo-community.org>, wrote:
    It certainly seems to me that you'll need a migration script to reshape the data from OCA v15 into Odoo CE v16. I don't see how that would contribute to clutter as the module could simply never exist for OCA v17+.

    On Tue, Nov 21, 2023 at 1:02 PM Robin Keunen <notifications@odoo-community.org> wrote:
    Hi community,

    The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?

    My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.

    What do you people think ?

    All the best,

    * more detail :
    responsible_id is a many2one to a res.partner in stock_picking_responsible
    responsible_id is a many2one to a res.users in stock

    Robin Keunen 
    Coop IT Easy 
    +32 488 86 57 40

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

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

    by Robin Keunen - 03:35 - 22 Nov 2023
  • Re: Porting a module from the OCA whose feature is now in Odoo CE
    It certainly seems to me that you'll need a migration script to reshape the data from OCA v15 into Odoo CE v16. I don't see how that would contribute to clutter as the module could simply never exist for OCA v17+.

    On Tue, Nov 21, 2023 at 1:02 PM Robin Keunen <notifications@odoo-community.org> wrote:
    Hi community,

    The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?

    My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.

    What do you people think ?

    All the best,

    * more detail :
    responsible_id is a many2one to a res.partner in stock_picking_responsible
    responsible_id is a many2one to a res.users in stock

    Robin Keunen 
    Coop IT Easy 
    +32 488 86 57 40

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

    by Adam Heinz - 11:10 - 21 Nov 2023
  • Porting a module from the OCA whose feature is now in Odoo CE
    Hi community,

    The functionality of module stock_picking_responsible in v12 is now part of Odoo CE in v16 but it still needs a migration script* : what should I do in this case ?

    My intuition is to port stock_picking_responsible to v16 and only leave the migration script in the module. I'm afraid this would clutter the oca repository with empty repositories.

    What do you people think ?

    All the best,

    * more detail :
    responsible_id is a many2one to a res.partner in stock_picking_responsible
    responsible_id is a many2one to a res.users in stock

    Robin Keunen 
    Coop IT Easy 
    robin@coopiteasy.be 
    +32 488 86 57 40
    by Robin Keunen - 07:01 - 21 Nov 2023
  • Re: runboat update
    Thank you very much Stéphane!


    El lun., 20 nov. 2023 22:47, Stéphane Bidoul <notifications@odoo-community.org> escribió:
    Hello again,

    By popular demand [1], I tweaked it so each runboat build now has two databases: one with all modules of the repo installed (if that succeeded), and one with only base installed (which should always succeed).

    Enjoy,

    -sbi


    On Sun, Nov 19, 2023 at 4:35 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi everyone,

    I just deployed a runboat update to address the issue of modules that conflict at installation in the same repo.

    When installation fails for any reason, runboat now initializes a database with the base module only. This way, users can select which addons to install.

    This is only an imperfect workaround, though, and in general we should continue to refrain from having modules that conflict at install time in the same repository.

    Best regards,

    -Stéphane

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

    by Rafael Blasco (Moduon) - 10:56 - 20 Nov 2023
  • Re: runboat update
    Hello again,

    By popular demand [1], I tweaked it so each runboat build now has two databases: one with all modules of the repo installed (if that succeeded), and one with only base installed (which should always succeed).

    Enjoy,

    -sbi


    On Sun, Nov 19, 2023 at 4:35 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
    Hi everyone,

    I just deployed a runboat update to address the issue of modules that conflict at installation in the same repo.

    When installation fails for any reason, runboat now initializes a database with the base module only. This way, users can select which addons to install.

    This is only an imperfect workaround, though, and in general we should continue to refrain from having modules that conflict at install time in the same repository.

    Best regards,

    -Stéphane

    by Stéphane Bidoul - 10:46 - 20 Nov 2023
  • Re: Purchase / Procurement Teams?
    The module procurement_purchase_no_grouping has also split by category, so almost there!

    Regards.
    by Pedro M. Baeza - 07:46 - 20 Nov 2023