Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • 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

    3 replies 3 replies

  • 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

    5 replies 5 replies

  • Purchase / Procurement Teams? 
    Hello,

for a future project I am looking for something like Sales Teams (or procurist 
specialization) but for Purchase. The split between teams/people should be 
based on category of the products being purchased. For example in a 
construction company someone purchases base materials, someone else 
insulation, ... Couldn't find anything even remotely similar.

Any help / pointers are welcome.

Best regards,

        Radovan Skolnik
    by Radovan Skolnik - 06:21 - 20 Nov 2023

    3 replies 3 replies

    • 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
    • Re: Purchase / Procurement Teams? 
      You/OCA is unbelievable! I wouldn't have been looking under this name but here it is. Does not cover all I need but still a huge step forward.

The missing pieces would be:
*) splitting incoming RfQ into segments (something along the lines of procurement_purchase_no_grouping)
*) assigning these partial RfQs to appropriate Representatives (any idea of something similar?)

But as always: OCA is great source of great modules. I'm proud to be part of it. Thanks Pedro.

Best regards,

	Radovan

On pondelok 20. novembra 2023 18:27:23 CET Pedro M. Baeza wrote:

> We have your back covered ;)

> https://github.com/OCA/purchase-workflow/pull/1921 [1]

> Regards.

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 [2]

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]

> 

> 

> 

> [1] https://github.com/OCA/purchase-workflow/pull/1921

> [2] https://odoo-community.org/groups/contributors-15

> [3] https://odoo-community.org/groups?unsubscribe
      by Radovan Skolnik - 07:35 - 20 Nov 2023
    • Re: Purchase / Procurement Teams?
      We have your back covered ;)


      Regards.
      by Pedro M. Baeza - 06:26 - 20 Nov 2023
  • Porting sale_order_type to 17 
    Hi guys
i'm trying to port sale_order_type module to Odoo 17
(i'm not a python developer)

I've done almost everything and now the module install properly (and
seems to work properly too)
But there are two things i don't know how to solve:

1. group_display_incoterm was removed from sale_stock and thus the
actually views used by sale_order_type doens't install properly. I've
removed the reference to ' groups="sale_stock.group_display_incoterm"
' but I don't know if this is correct or has to be replaced with
something else

2. `states` are deprecated in 17. How can I replace these ?
https://github.com/OCA/sale-workflow/blob/16.0/sale_order_type/models/sale.py#L20-L23

Tnx
    by gandalf.corvotempesta - 06:57 - 19 Nov 2023

    2 replies 2 replies

    • Re: Porting sale_order_type to 17 
      Il giorno dom 19 nov 2023 alle ore 23:16 Francesco Ballerini
<notifications@odoo-community.org> ha scritto:

> although in Odoo17 I think this expression has to be changed into something like

>

> <field

>     name="type_id"

>     readonly="state not in ['sale', 'done', 'cancel']"

> />

>

> as a consequence of this commit.

Great idea, thank you
      by gandalf.corvotempesta - 09:06 - 20 Nov 2023
    • Re: Porting sale_order_type to 17
      Hi Gandalf Corvotempesta I appreciate your name : )

      1 - In the context of a porting I think it's correct to simply remove "groups" attribute from fields in order to resolve the missing xml_id, as the group has been completely removed from the source code
      2 - about this case I'm not sure because I don't know if it's possible in odoo17, to avoid the usage of deprecated python argument "states" while keeping the "readonly" condition in python. If you don't find a way to keep this in python, I think there is no problem on defining the "readonly" conditions on XML. Until odoo16 you could have parsed type_id readonly states into XML by adding "attrs" attribute on field like the following code

      <field
          name="type_id"
          attrs="{'readonly': [('state', 'in', ['sale', 'done', 'cancel'])]}"
      />
      although in Odoo17 I think this expression has to be changed into something like
      <field
          name="type_id"
          readonly="state not in ['sale', 'done', 'cancel']"
      />
      as a consequence of this commit.

      Best regards
      --
      Francesco Ballerini

      Il giorno dom 19 nov 2023 alle ore 18:57 Gandalf Corvotempesta <notifications@odoo-community.org> ha scritto:
      Hi guys
i'm trying to port sale_order_type module to Odoo 17
(i'm not a python developer)

I've done almost everything and now the module install properly (and
seems to work properly too)
But there are two things i don't know how to solve:

1. group_display_incoterm was removed from sale_stock and thus the
actually views used by sale_order_type doens't install properly. I've
removed the reference to ' groups="sale_stock.group_display_incoterm"
' but I don't know if this is correct or has to be replaced with
something else

2. `states` are deprecated in 17. How can I replace these ?
https://github.com/OCA/sale-workflow/blob/16.0/sale_order_type/models/sale.py#L20-L23

Tnx

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

      by Francesco Ballerini - 11:16 - 19 Nov 2023
  • runboat update
    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 - 05:16 - 19 Nov 2023

    4 replies 4 replies

    • 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: runboat update
      Really thanks Stephane,

      Bonne journée

      David BEAL
      Consultant ERP Odoo


      Le dim. 19 nov. 2023 à 18:40, Pedro M. Baeza <notifications@odoo-community.org> a écrit :
      Welcome addition, thanks!

      El dom., 19 nov. 2023 17:16, Stéphane Bidoul <notifications@odoo-community.org> escribió:
      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

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

      by David BEAL - 09:50 - 20 Nov 2023
    • Re: runboat update
      Welcome addition, thanks!

      El dom., 19 nov. 2023 17:16, Stéphane Bidoul <notifications@odoo-community.org> escribió:
      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 Pedro M. Baeza - 06:18 - 19 Nov 2023
  • Operating unit
    Hi 
    I have installed 

    account_operating_unit , operating_unit and product_operating_unit
    The description of the modules says "Product and customer independence of OU." 
    Yes
    I can see the independence of the products: if an OU1 user created a product, an OU2 user will not see it.

    But the same is not happening with the Customers, it seems customers are global over OUs. If an OU1 user created a customer, an OU2 user can see it.
    How to achieve the independence of customers?

    Regards

    by Ahmed - 11:52 - 16 Nov 2023

    1 replies 1 replies

  • New way to create repositories and add maintainers
    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

    by Enric Tobella Alomar - 10:57 - 16 Nov 2023

    7 replies 7 replies

  • emergency maintenance on OCA server 
    Hello everyone,

We have a faulty disk on the OCA server. I opened a support issue to get 
it replaced in the datacenter. This will result in a downtime of the 
server, and possibly some degraded performance while the RAID arrays get 
rebuild.

Impacted services:

* our Odoo instance
* our webite
* the translation platform
* the OCA gitbot

I'll keep you posted when we have more information about the time of the 
intervention.

We thank you for your understanding.



-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
    by Alexandre Fayolle - 01:01 - 16 Nov 2023

    9 replies 9 replies

    • Re: emergency maintenance on OCA server 
      Oups... Thanks Stéphane

On 17/11/2023 10:31, Stéphane Bidoul wrote:

> Thank you Alex for handling this yesterday during the night.

> 

> I did a quick check this morning and restarted the services that had 

> failed since (runboat, oca-github-bot, simpleindex).

> 

> Everything should be back to normal, now.

> 

> Best regards,

> 

> -sbi

> 

> 

> On Fri, Nov 17, 2023 at 10:18 AM Simone Orsi 

> <notifications@odoo-community.org 

> <mailto:notifications@odoo-community.org>> wrote:

> 

>     I think we have a problem w/ https://wheelhouse.odoo-community.org

>     <https://wheelhouse.odoo-community.org> for the builds

> 

>     On Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza

>     <notifications@odoo-community.org

>     <mailto:notifications@odoo-community.org>> wrote:

> 

>         Thank you very much for the work, Alexandre.

> 

>         It seems that runboat and the OCA bot still have some problems.

>         Can you please check?

> 

>         Regards.

> 

>         _______________________________________________

>         Mailing-List: https://odoo-community.org/groups/contributors-15

>         <https://odoo-community.org/groups/contributors-15>

>         Post to: mailto:contributors@odoo-community.org

>         <mailto:contributors@odoo-community.org>

>         Unsubscribe: https://odoo-community.org/groups?unsubscribe

>         <https://odoo-community.org/groups?unsubscribe>

> 

> 

> 

>     -- 

>     Simone Orsi

> 

>     Full stack Python web developer, Odoo specialist, Odoo Community

>     Board Member, in love with open source.

> 

>     _______________________________________________

>     Mailing-List: https://odoo-community.org/groups/contributors-15

>     <https://odoo-community.org/groups/contributors-15>

>     Post to: mailto:contributors@odoo-community.org

>     <mailto:contributors@odoo-community.org>

>     Unsubscribe: https://odoo-community.org/groups?unsubscribe

>     <https://odoo-community.org/groups?unsubscribe>

> 

> _______________________________________________

> Mailing-List: https://odoo-community.org/groups/contributors-15 

> <https://odoo-community.org/groups/contributors-15>

> Post to: mailto:contributors@odoo-community.org

> Unsubscribe: https://odoo-community.org/groups?unsubscribe 

> <https://odoo-community.org/groups?unsubscribe>

> 


-- 
Alexandre Fayolle
Senior Software Engineer
Tel : +33 4 58 48 20 30

Camptocamp France SAS
18 rue du Lac Saint André
73 370 Le Bourget-du-Lac
France

http://www.camptocamp.com
      by Alexandre Fayolle - 01:56 - 17 Nov 2023
    • Re: emergency maintenance on OCA server
      Everything seems to be working now, thanks!

      Regards.
      by Pedro M. Baeza - 11:35 - 17 Nov 2023
    • Re: emergency maintenance on OCA server
      Thanks to Alex and Stéphane, the OCA owes you a lot for maintaining our essential tools!
      And have a great weekend, everyone!
      --
      Virginie
      +32 477 64 17 20
      Info : 2j/semaine sont dédiés à Chaf et 3j/semaine sont dédiés à Coop IT Easy

      -----Original Message-----
      From: Stéphane Bidoul <notifications@odoo-community.org>
      Reply-To: Contributors <contributors@odoo-community.org>
      Subject: Re: emergency maintenance on OCA server
      Date: Fri, 17 Nov 2023 09:31:53 -0000

      Thank you Alex for handling this yesterday during the night.

      I did a quick check this morning and restarted the services that had failed since (runboat, oca-github-bot, simpleindex).

      Everything should be back to normal, now.

      Best regards,

      -sbi


      On Fri, Nov 17, 2023 at 10:18 AM Simone Orsi <notifications@odoo-community.org> wrote:
      I think we have a problem w/ https://wheelhouse.odoo-community.org for the builds

      On Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      Thank you very much for the work, Alexandre.

      It seems that runboat and the OCA bot still have some problems. Can you please check?

      Regards.

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

      _______________________________________________
      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 Virginie Dewulf. - 10:40 - 17 Nov 2023
    • Re: emergency maintenance on OCA server
      Thank you Alex for handling this yesterday during the night.

      I did a quick check this morning and restarted the services that had failed since (runboat, oca-github-bot, simpleindex).

      Everything should be back to normal, now.

      Best regards,

      -sbi


      On Fri, Nov 17, 2023 at 10:18 AM Simone Orsi <notifications@odoo-community.org> wrote:
      I think we have a problem w/ https://wheelhouse.odoo-community.org for the builds

      On Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      Thank you very much for the work, Alexandre.

      It seems that runboat and the OCA bot still have some problems. Can you please check?

      Regards.

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

      by Stéphane Bidoul - 10:30 - 17 Nov 2023
    • Re: emergency maintenance on OCA server
      I think we have a problem w/ https://wheelhouse.odoo-community.org for the builds

      On Fri, Nov 17, 2023 at 9:02 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      Thank you very much for the work, Alexandre.

      It seems that runboat and the OCA bot still have some problems. Can you please check?

      Regards.

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi - 10:16 - 17 Nov 2023

  • Manual Currency Conversion Bank Transaction
    Hi everyone,

    I have the case of a client who wants that when importing a bank statement, in the reconciliation of movements thanks to the `account_reconciliation_widget` module, he can determine the rate that he agreed with his bank and not the one offered by Odoo.

    I'm surprised that there is no module for this, since it is very common.

    I am trying to develop the functionality, but it is a bit complex to avoid the odoo rate and make everything add up in the end, since the rate calculation is repeated in several places.

    Any ideas or suggestions?

    Greetings and thank you very much,

    /Lansana Barry




    by Lansana Barry - 09:25 - 16 Nov 2023

    1 replies 1 replies

  • Odoo Test framework and rollback issue
    Hi everyone,

    I'm currently developing on 14.0 a test for one of my module and I'm having a headache trying to understand why an action is not properly rolled back after the exception is raised.

    My code sample:
    class TestSoftwareLicensePass(TransactionCase):
        def test_activation(self):
            ...
            self.assertEqual(pass_lic1.get_remaining_activation(), 1)
            with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
                pass_lic1.activate("device_uuid_4/3")
            self.assertEqual(pass_lic1.get_remaining_activation(), 1)
            with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
                pass_lic1.activate("device_uuid_4/3")

    The second assertEqual statement FAILS because get_remaining_activation() returns 0, but since the exception has been correctly captured by the  with self.assertRaisesRegex statement, this part should have been rolled back by the odoo framework.
    (and no cr.commit in the activate function)

    Looking in other tests, I can see that a lot of with self.assert statements have a self.cr.savepoint() at their side (like this code sample in odoo/odoo/addons/base/tests/test_views.py):

    class TestViewInheritance(ViewCase):   
        def test_no_recursion(self):
            r1 = self.makeView('R1')
            with self.assertRaises(ValidationError), self.cr.savepoint():
                r1.write({'inherit_id': r1.id})

    Is this related to the TransactionCase class ? (Probably not, I made a test with SavepointCase and same issue)
    Should I always append self.cr.savepoint() ?

    Yann.
    by Yann Papouin - 06:16 - 15 Nov 2023

    4 replies 4 replies

    • 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: Odoo Test framework and rollback issue
      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.
      by Pedro M. Baeza - 01:41 - 17 Nov 2023
    • Re: Odoo Test framework and rollback issue
      Hi,

      In Odoo 14, you should append self.cr.savepoint() when you want to add additional tests after the assertRaises. It's required to restore the db cursor, the environment and the cache at the state prior to the exception. You should also question why you want to add additional tests after this assertion? Maybe they can be put into another specific test method. In Odoo 16 (at least), odoo overrides the assertRaises method to add the call to the savepoint and ensures a cleanup of the environment. https://github.com/odoo/odoo/blob/16.0/odoo/tests/common.py#L367

      Regards,

      lmi

      On Wed, Nov 15, 2023 at 6:24 PM Yann Papouin <notifications@odoo-community.org> wrote:
      Hi everyone,

      I'm currently developing on 14.0 a test for one of my module and I'm having a headache trying to understand why an action is not properly rolled back after the exception is raised.

      My code sample:
      class TestSoftwareLicensePass(TransactionCase):
          def test_activation(self):
              ...
              self.assertEqual(pass_lic1.get_remaining_activation(), 1)
              with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
                  pass_lic1.activate("device_uuid_4/3")
              self.assertEqual(pass_lic1.get_remaining_activation(), 1)
              with self.assertRaisesRegex(ValidationError, r"Max activation reached"):
                  pass_lic1.activate("device_uuid_4/3")

      The second assertEqual statement FAILS because get_remaining_activation() returns 0, but since the exception has been correctly captured by the  with self.assertRaisesRegex statement, this part should have been rolled back by the odoo framework.
      (and no cr.commit in the activate function)

      Looking in other tests, I can see that a lot of with self.assert statements have a self.cr.savepoint() at their side (like this code sample in odoo/odoo/addons/base/tests/test_views.py):

      class TestViewInheritance(ViewCase):   
          def test_no_recursion(self):
              r1 = self.makeView('R1')
              with self.assertRaises(ValidationError), self.cr.savepoint():
                  r1.write({'inherit_id': r1.id})

      Is this related to the TransactionCase class ? (Probably not, I made a test with SavepointCase and same issue)
      Should I always append self.cr.savepoint() ?

      Yann.

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

      by Laurent Mignon - 08:51 - 16 Nov 2023
    • Re: Odoo Test framework and rollback issue
      It's just a problem with how Odoo handles rollbacks and savepoints in tests. The thumb rule is to not do anything more after testing a raise. Do it in another test method.

      Regards.
      by Pedro M. Baeza - 07:47 - 15 Nov 2023
  • Sale/invoice report break page
    Dear community,

    One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.

    Do you know any existing modules to do that ?

    As sections are table rows it's not as easy to add a page-break-inside: avoid; on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.

    This probably ends up with 3 modules:

    base_breakpage in oca/reporting-engine
    sale_report_breakpage in oca/sale-reporting
    account_invoice_report_breakpage in oca/account-invoice-reporting

    Any hints on that ?
    regards

    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Linkedin: pierre-verkest
    by Pierre Verkest - 11:36 - 15 Nov 2023

    2 replies 2 replies

    • Re: Sale/invoice report break page
      Hi there,

      tl;dr: 3 new PRs to reviews to get more control on page breaks in sales/invoices PDF report

      * report_qweb_table_pagebreak: https://github.com/OCA/reporting-engine/pull/826:
        Control Page Breaks in `<table>`'s within QWeb Reports

        The primary objective of this module is to prevent tables
        from being split arbitrarily and to provide better control
        over page breaks within tables.

        Avoid break page inside sections on sale PDF report

        Avoid break page inside sections on invoice PDF report

      On the way to create those modules I got few challenges to I change a bit the behaviour on this first version

      * `page-break-[before|afeter|inside]` only applies on block elements which `<tr>` aren't by default, that why
         the first PR `report_qweb_table_pagebreak` is splitting table and manage page break at <table> level
      * adding new kind of line (like note or section) on sale order line or account move line would be the best
         behaviour I would implement as expected behaviour for end user but I'm a bit scared about the impact
         on existing code to ignore those lines so I forgot that idea (I haven't test to be honest)
      * adding a boolean field on sale order line is pretty straightforward except for section where we should implement
        a widget to allow to manage the attribute from the form view

      So I end up with this first solution which will try to avoid breaking pages inside each section which could be improved
      later to give even more control.


      Cheers,

      Le mer. 15 nov. 2023 à 19:52, Tom Blauwendraat <notifications@odoo-community.org> a écrit :

      Hey Pierre,

      only thing I know is that it's possible to manually add "page-break-before: always;" to certain elements. So once you know how many rows fit on a page, you could adjust the QWEB generation to add page breaks at the right places. This doesn't take into account page margins however, so probably your way is better.

      -Tom

      On 11/15/23 11:38, Pierre Verkest wrote:
      Dear community,

      One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.

      Do you know any existing modules to do that ?

      As sections are table rows it's not as easy to add a page-break-inside: avoid; on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.

      This probably ends up with 3 modules:

      base_breakpage in oca/reporting-engine
      sale_report_breakpage in oca/sale-reporting
      account_invoice_report_breakpage in oca/account-invoice-reporting

      Any hints on that ?
      regards

      --
      Pierre Verkest
      06 81 12 25 20
      Github: petrus-v - Linkedin: pierre-verkest

      _______________________________________________
      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



      --
      Pierre
      by Pierre Verkest - 06:11 - 13 Dec 2023
    • Re: Sale/invoice report break page

      Hey Pierre,

      only thing I know is that it's possible to manually add "page-break-before: always;" to certain elements. So once you know how many rows fit on a page, you could adjust the QWEB generation to add page breaks at the right places. This doesn't take into account page margins however, so probably your way is better.

      -Tom

      On 11/15/23 11:38, Pierre Verkest wrote:
      Dear community,

      One of my customers using odoo 14.0 needs to get the control where page breaks appear in pdf reports on quotations and invoice documents.

      Do you know any existing modules to do that ?

      As sections are table rows it's not as easy to add a page-break-inside: avoid; on a html block and would not fit all corner cases. So I'm going to add a link button (such as the add section) that will add a new kind of row to manage the break page in reports.

      This probably ends up with 3 modules:

      base_breakpage in oca/reporting-engine
      sale_report_breakpage in oca/sale-reporting
      account_invoice_report_breakpage in oca/account-invoice-reporting

      Any hints on that ?
      regards

      --
      Pierre Verkest
      06 81 12 25 20
      Github: petrus-v - Linkedin: pierre-verkest

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

      by Tom Blauwendraat - 07:47 - 15 Nov 2023
  • unit price precision based on product UOM category selected
    Hi,
    Is there a module that can help me with the following?

    use case: change the unit price precision based on the selected product's uom (or product category's uom)

    I add to a SO, invoice, PO:
    - a 1st line with an article with a UOM of type "energy" and this would allow me to specify the unit price with 4 digits
    - a 2nd line with an article with a UOM of type "unit" and this would allow me to specify the unit price with default 2 digits.

    Thank you
     --
    Yves Goldberg
    --

    by Yves Goldberg - 09:21 - 15 Nov 2023

    1 replies 1 replies

  • Info Server VPS 
    Ciao Lorenzo,
come da comunicazione con Fabrizio, faccio un elendo dei task da
completare ed il relativo costo.

- creazione server virtuale 15 EUR
- installazione e configurazione backend 25 EUR
	* tomcat
	* php-fpm
	* postgresql
	* mariadb (mysql)

- Installazione Wordpress e wp-cli 15 EUR
- Installazione e configurazione letsencrypt 15 EUR
- Migrazione sito web Wordpress 25 EUR
- Migrazione applicazione in Java 25 EUR
- Migrazione DNS e SSL per il dominio booking 25 EUR
- Migrazione DNS e SSL per il sito web wordpress 25 EUR
- Creazione soluzione di backup in gdrive 75 EUR
- Migrazione database (postgresql, e mysql) 30 EUR
- Backup una tantum 25 EUR

In totale 300 EUR

Per il backup di postgres ci pensa Fabrizio, per il sito web avete
bisogno di backup?

Inoltre per la quota mensile posso fare 120 EUR con pagamento
anticipato trimestrale che include assistenza e monitoring, manutenzione
e aggiornamento del server con test di ripristino backup mensile.

Inoltre c'è un servizio opzionale di hardening del server, per la messa
in sicurezza.

Attendo tue,
Salvatore De Paolis
    by Salvatore - 06:55 - 14 Nov 2023
  • intercompany transfer
    dear all

    i have issue with inter company 
    i have to companies A&B
    both company sell and purchase from them
    when make this process between them i have in inventory tow delivery order or tow Receipts for one sales order or purchase 
    please i need help to solve it

    --
    Best Regards
    Samir Mahmoud
    00201062648111


    by Samir Mahmoud Hassan - 03:30 - 14 Nov 2023

    1 replies 1 replies

  • Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
    Dear community,

    I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

    I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

    I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

    If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to take or the process involved.

    Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

    Best regards,

    Compassion Switzerland
    by "Emanuel Cino" <emanuel@compassion.ch> - 12:29 - 13 Nov 2023

    3 replies 3 replies

    • Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
      Well, you just need to create a Pull request and add yourself on the following file:


      Once the PR is merged by someone on the board, you will receive the notification :D

      El lun, 20 nov 2023 a las 11:42, Cino, Emanuel (<notifications@odoo-community.org>) escribió:
      Thank you Yannick,

      What are the next steps for fulfilling my application? Please let me know and I will take the necessary steps.

      Have a great week!


      Emanuel Cino 


      Le mar. 14 nov. 2023 à 15:01, Yannick Payot <notifications@odoo-community.org> a écrit :
      Hello Emanuel,

      +1 for your application

      I will gladly welcome you as a PSC member.
      Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.

      To synchronize it's important to keep the "Migration to XX" github issues up to date:

      All the best,
      Yannick

      On Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:
      Dear community,

      I hope this email finds y ou well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

      I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

      I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

      If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.

      Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

      Best regards,

      Compassion Switzerland

      _______________________________________________
      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

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



      --
      Enric Tobella Alomar
      CEO & Founder

      by Enric Tobella Alomar - 11:47 - 20 Nov 2023
    • Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
      Thank you Yannick,

      What are the next steps for fulfilling my application? Please let me know and I will take the necessary steps.

      Have a great week!


      Emanuel Cino 


      Le mar. 14 nov. 2023 à 15:01, Yannick Payot <notifications@odoo-community.org> a écrit :
      Hello Emanuel,

      +1 for your application

      I will gladly welcome you as a PSC member.
      Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.

      To synchronize it's important to keep the "Migration to XX" github issues up to date:

      All the best,
      Yannick

      On Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:
      Dear community,

      I hope this email finds y ou well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

      I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

      I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

      If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.

      Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

      Best regards,

      Compassion Switzerland

      _______________________________________________
      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 "Cino, Emanuel" <emanuel@compassion.ch> - 11:42 - 20 Nov 2023
    • Re: Expression of Interest in Becoming Maintainer for l10n-switzerland Repository
      Hello Emanuel,

      +1 for your application

      I will gladly welcome you as a PSC member.
      Most of the historical modules that Camptocamp helped to maintain have been included or replicated in the core thus becoming obsolete. Thus, for the latest versions there has been very few activitiy.

      To synchronize it's important to keep the "Migration to XX" github issues up to date:

      All the best,
      Yannick

      On Mon, 13 Nov 2023 at 12:29, Emanuel Cino <notifications@odoo-community.org> wrote:
      Dear community,

      I hope this email finds you well. My name is Emanuel, and I am writing to express my interest in the l10n-switzerland repository. I recently noticed that the repository appears to be inactive, and as someone passionate about its purpose, I am eager to contribute to its revitalization.

      I am writing to inquire about the current maintainers of the l10n-switzerland repository and to express my willingness to take on a role as a maintainer. The project's objectives align closely with my interests and skills, and I believe that by actively participating in its development, we can work together to ensure its continued growth and success.

      I have successfully contributed to various OCA repositories in the past, and I am committed to dedicating time and effort to this project to help bring it back to life.

      If the opportunity to become a maintainer is available, I would appreciate any guidance on the steps I need to ta ke or the process involved.

      Thank you for considering my request, and I look forward to your guidance on how I can assist in reviving this valuable open-source initiative.

      Best regards,

      Compassion Switzerland

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

      by Yannick Payot - 03:00 - 14 Nov 2023
  • 17.0 branches
    Hi everyone,

    The 17.0 branches are being created in all OCA repos as I'm writing this.

    There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

    • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
    • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
    • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
    • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
    The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

    In case of problem, let us know of any problem by creating an issue in the repo template project [3]

    Best regards,

    [1] https://docs.astral.sh/ruff/rules/

    --
    Stéphane Bidoul
    http://acsone.eu/

    by Stéphane Bidoul - 04:18 - 12 Nov 2023

    10 replies 10 replies

    • Re: 17.0 branches
      Thanks a lot Stéphane for all these evolutions.

      Some of them have a really good impact on the environment, double thanks for that.

      David BEAL
      Consultant ERP Odoo


      Le lun. 13 nov. 2023 à 15:52, Juan José Scarafía <notifications@odoo-community.org> a écrit :
      Great, thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia



      El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:
      Hi everyone,

      The 17.0 branches are being created in all OCA repos as I'm writing this.

      There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

      • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
      • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
      • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
      • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
      The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

      In case of problem, let us know of any problem by creating an issue in the repo template project [3]

      Best regards,

      [1] https://docs.astral.sh/ruff/rules/

      --
      Stéphane Bidoul
      http://acsone.eu/

      _______________________________________________
      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 David BEAL - 07:25 - 13 Nov 2023
    • Re: 17.0 branches
      Great, thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia



      El dom, 12 nov 2023 a la(s) 13:25, Stéphane Bidoul (notifications@odoo-community.org) escribió:
      Hi everyone,

      The 17.0 branches are being created in all OCA repos as I'm writing this.

      There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

      • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
      • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
      • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
      • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
      The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

      In case of problem, let us know of any problem by creating an issue in the repo template project [3]

      Best regards,

      [1] https://docs.astral.sh/ruff/rules/

      --
      Stéphane Bidoul
      http://acsone.eu/

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

      by Juan José Scarafía - 03:51 - 13 Nov 2023
    • Re: 17.0 branches
      It can be decided per branch answering the copier question.

      Regards.
      by Pedro M. Baeza - 03:36 - 13 Nov 2023
    • Re: 17.0 branches
      Will Ruff also be used on earlier branches or will it only be used for 17.0+?

      Il giorno dom 12 nov 2023 alle ore 17:25 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:
      Hi everyone,

      The 17.0 branches are being created in all OCA repos as I'm writing this.

      There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

      • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
      • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
      • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
      • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
      The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

      In case of problem, let us know of any problem by creating an issue in the repo template project [3]

      Best regards,

      [1] https://docs.astral.sh/ruff/rules/

      --
      Stéphane Bidoul
      http://acsone.eu/

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



      --

      Francesco Apruzzese

      Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

      Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
      This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

      Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
      by Francesco Apruzzese - 03:31 - 13 Nov 2023
    • Re: 17.0 branches
      Thanks Stéphane

      On Sun, Nov 12, 2023 at 7:55 PM Stéphane Bidoul <notifications@odoo-community.org> wrote:
      Hi everyone,

      The 17.0 branches are being created in all OCA repos as I'm writing this.

      There are few news and improvements compared to previous branches, mainly in the pre-commit configuration:

      • It uses ruff and ruff-format instead of flake8, autoflakes, isort, pyupgrade and black. This will improve the performance of pre-commit runs. Note that if some PSC want to be stricter by enabling additional ruff rules [1], it is possible by re-running "copier update --trust" and answering the corresponding question.
      • The readme fragments are converted to markdown. This makes it easier for non-technical contributors, and is also more robust (wrt subtitles formats, for instance). This is already reflected in the OCA module template [2]
      • pre-commit creates a pyproject.toml file at the root of each addon, in place of setup.py in the separate setup/ directory. This is more intuitive (each addon is a little python project) and standards based. It is also more robust as some recent version of setuptools break our setup.py (and Odoo's) editable mode in some circumstances.
      • pre-commit generates README.rst and index.hml. This is for easier review of the module descriptions in runboat.
      The migration issues had been created last week. Don't forget to announce yourself when you start migrating a module.

      In case of problem, let us know of any problem by creating an issue in the repo template project [3]

      Best regards,

      [1] https://docs.astral.sh/ruff/rules/

      --
      Stéphane Bidoul
      http://acsone.eu/

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

      by Mostafa Barmshory - 03:28 - 13 Nov 2023

  • Ledger for the individual related to a company
    Hi 

    If the customer is an individual without a related company, I would find the entries in the partner ledger. the same if it is a company.
    But if the customer is an individual (or a contact) related to a company, all records appear only in the partner ledger of the company itself but the individual contact ledger will be empty

    Is there an OCA module that shows whose contact this amount is for? in the partner ledger ?
    I mean a module that makes the entry appear in the contact-partner also, if he is chosen while invoicing or while creating a payment.

    Thanks alot


    by Ahmed - 10:01 - 10 Nov 2023

    1 replies 1 replies

    • RE: Ledger for the individual related to a company

      Dear,

       

      You have to create a partner for you customer as an individual and create your sales order and invoice on this partner and not on the company with the person as a contact. Of course, when the order / invoice is recorded on the company, it is in the company ledger. The contact person is there only as extra information. When the order is intended for the private person and has to be paid by this person, you must assign this private person as the partner.

       

      With kind regards,

       

      Van Hirtum Johan

       

      Van: Ahmed Ragab [mailto:notifications@odoo-community.org]
      Verzonden: vrijdag 10 november 2023 22:02
      Aan: Contributors
      Onderwerp: Ledger for the individual related to a company

       

      Hi 

       

      If the customer is an individual without a related company, I would find the entries in the partner ledger. the same if it is a company.

      But if the customer is an individual (or a contact) related to a company, all records appear only in the partner ledger of the company itself but the individual contact ledger will be empty

       

      Is there an OCA module that shows whose contact this amount is for? in the partner ledger ?

      I mean a module that makes the entry appear in the contact-partner also, if he is chosen while invoicing or while creating a payment.

       

      Thanks alot

       

       

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

      by johan - 09:36 - 13 Nov 2023
  • Looking for a module
    Hi, 

    use case: in SO field "Delivery Address" user can select only contacts related to partner set in "Customer".

    is there a module doing this to your knowledge?

    Thanks!

    Francesco

    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790
    by Francesco Foresti - 11:01 - 10 Nov 2023

    2 replies 2 replies

  • e-commerce category with images
    Dear contributors,

    I've been asked for a way to render categories in e-commerce pretty much like brands in https://github.com/OCA/e-commerce/tree/14.0/website_sale_product_brand 

    Do we have a module for this?

    Thanks

    --
    Francesco Ballerini
    by Francesco Ballerini - 11:00 - 8 Nov 2023

    2 replies 2 replies

  • Benchmark of deployment / maintenance solutions

    Dear contributors,

    I would like to propose a benchmark of deployment and maintenance solutions being used by OCA users.
    Please contribute to this discussion if you would like your solution to be part of the benchmark: https://github.com/orgs/OCA/discussions/123

    Best regards,
    Théo.

    by Théo Chapy - 03:16 - 7 Nov 2023