Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

Contributors

  • Looking for solution partner in the world of Odoo

    Dear Odoo community,

    do you have a general or industry specific solution built on Odoo? 

    We are currently searching for those solutions to make them more visible in the Odoo world and give the opportunity to scale them internationally. The aim is to jointly open up new business opportunities, exploit synergies and further develop best practices within the Odoo community.

    What does this mean in concrete terms? We are looking for solution and industry partners:
    • Solution partners benefit from an extended reach for their Odoo-based solution, additional marketing opportunities and presentation opportunities within the network.
    • Industry partners gain access to a global market, can strategically position themselves in the Odoo ecosystem and benefit from targeted branding and marketing options.
    Further details can be found in the attached flyer or on our website. If you have any questions, please do not hesitate to contact us.

    Thanks and kind regards,

    Tobias Hammeke
    Managing Partner

    +49 172 265 3729



    BOP Logo.png



    		   

    Stronger Together
    emailAddress
    		info@best-odoo-partners.com  
    website
    		www.bop-alliance.com

    		linkedin instagram 
     
     
     
     
     



    This message is exclusively intended for its addressee and may contain information that is confidential and protected by professional privilege. If you are not the intended recipient, you are hereby notified that any dissemination, copy or disclosure of this communication is strictly prohibited by law. If this message has been received by error, please immediately notify us via e-mail and delete it.
    by OBS Holding GmbH - 04:06 - 4 Mar 2025

    2 attachments 2 attachments

    BOP digital Flyer (solution partner).pdf
    C2_signature_boplogo_53e1547a-2721-4b84-948b-f6913dd681b3.png
  • New e-commerce module for product attributes
    Dear OCA community 

    Allow me to introduce this new module for product attribute sets.

    I am happy to hear from you suggestions and ideas and opinions.

    For me it is a good occasion as this is the second day of the holly month Ramadan, and I feel blessings.

    Here is the open pull request of our new module:


    best regards

    Mohamed Alkobrosli 

    by Mohamed Alkobrosly - 07:26 - 2 Mar 2025

    1 replies 1 replies

  • Weblate 5.10
    Hi everyone,

    translation.odoo-community.org has been upgraded to Weblate 5.10.

    Let me know of any issue.

    Best regards,

    -Stéphane

    --
    Stéphane Bidoul
    http://acsone.eu/
    by Stéphane Bidoul - 12:16 - 1 Mar 2025

    4 replies 4 replies

  • Add me in the telegram channel
    by "Shaheedullah khan" <shaheedullahkhan7@gmail.com> - 11:31 - 1 Mar 2025
  • Translations

    Hey OCA,

    I have a kind of „basic“ question I guess, regarding the handling of mail templates and its translations.

     

    If I need to overwrite email templates that are used „hard-coded“ in Odoo core create/write methods, what is the best way to do so.

     

    - 1st: Set the email template noupdate flag to false using the write function, then overwrite the template with your own record and set the noupdate flag back to true.

     

    The new template is now correct using create method of Odoo core. But here I have the problem that I cannot process the translations for the template correctly as they are referred to the Odoo core module. 

     

    - 2nd: Create „my module“-specific mail templates and load the records on module installation in addition to the original Odoo mail templates. This makes things easier concerning the translation po files.

     

    The Problem: as the original core code is using the hard-coded mail templates, I need to rebuild the whole logic from Odoo core in create and writes method in my module and include my adaptions.

     

     

    So in general… what is the better approach… or maybe a totally different one?

     

    Is it possible to override the Core module translations properly when a template is “replaced” by custom module?

     

    All the best

    Nils

    by Nils Coenen - 08:50 - 28 Feb 2025
  • Issue with ir.actions.server in Coverage Report – Curious About Others' Experience

    Dear OCA Community,

    I am using https://github.com/oca/oca-ci to run automated test cases in my GitLab pipeline, and I encountered a strange issue today.

    In one of the modules in my current repository, I am creating a Server Action (ir.actions.server) and executing it via the run method. However, during test execution, coverage.py mistakenly treated ir.actions.server as a file (might be because it is using safe_eval) and attempted to include it in the .coverage report. This resulted in the following error while generating coverage report:

    No source for code: '/builds/GIT_REPO/ir.actions.server(576,)'.

    I was able to resolve this by adding a .coveragerc file with the following configuration:

    [run]
    omit =
        *ir.actions.server*

    While this fix works, I am curious to know if others have encountered a similar issue, how it has been handled in other setups, and whether my solution is the proper way to address it.

    Looking forward to insights!

    BizzAppDev
    Erudite of Business Solutions
    With Kind Regards,
    Ruchir Y Shukla
    Founder & CTO
    BizzAppDev Systems Pvt. Ltd.
    M:
    +91 98 980 78748
    W:
    E:
    ruchir@bizzappdev.com

    Book time to meet with me
    by Ruchir Shukla. - 04:56 - 25 Feb 2025

    2 attachments 2 attachments

    Outlook-dfrr03sc.png
    Outlook-tsvh2lgl.png
  • Tests failure when invoicing is involved after a change in Odoo upstream
    I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


    that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

    This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

    The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


    Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

    The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


    If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


    v17 is not affected for now. Let's hope it continues this way...

    Regards.
    by Pedro M. Baeza - 03:41 - 25 Feb 2025

    7 replies 7 replies

    • Re: Tests failure when invoicing is involved after a change in Odoo upstream
      Well, that only fixes the problem in specific repositories OCA CIs, and you still needed to make some changes in tests. The problem we had was when using the modules in our own Ci, and the proposed patch was a good balance for not disturbing current OCA status and don't fail in our scenario.

      Regards.
      by Pedro M. Baeza - 05:07 - 12 Mar 2025
    • Re: Tests failure when invoicing is involved after a change in Odoo upstream
      While fixing the 16.0 branch for l10n_belgium I have done some more research on this.

      In 16.0, something like `odoo -i l10n_be` gives you two companies with main company without CoA (that's the problem mentioned in OP)

      - Your Company (base.main_company), country=US, no CoA
      - BE Company, country=BE, BE CoA

      In 17.0 and 18.0, the generic CoA is loaded on main_company even though a localization was loaded:

      - Your Company (base.main_company), country=US, Generic CoA
      - BE Company, country=BE, BE CoA

      This is why we only see the problem in 16.

      So I now think pre-loading l10n_generic_coa before running the tests in 16.0 is an easy fix, and also a good solution (and the one I prefer), because it sets up the main company identically to what we get in later versions.

      IMO, tests that really depend on a CoA should use a company initialized with that CoA, and not base.main_company.

      This is what I did in l10n_belgium: https://github.com/OCA/l10n-belgium/pull/243

      Best regards,

      -Stéphane

      On Fri, Feb 28, 2025 at 7:33 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
      I have hit this issue in one of my projects where I run all tests post-install.

      Instead of changing all my tests, I chose to install l10n_generic_coa in CI, which was an easy solution in my specific situation.
      Maybe this can help others hitting the same problem.

      Best regards,

      -Stéphane


      On Wed, Feb 26, 2025 at 4:53 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      Stefan and Denis, the reason for the Odoo patch may be legit, and it is. The problem is that it comes too late for the lifecycle of this version IMO, and more having in version 17 integrated the generic CoA into account for better practices. Anyway, this is just undisclosing a problem that has been hidden in the design of our OCA tests, them not being deterministic and really unit tests, as they are relying on previous state of data for being successful:

      - The company used is the one populated by default instead of using a full set of data including the company. This may be reasonable for execution times, and that's why the decision to just fix this condition installing an existing CoA instead of populating on each test a new company.
      - There's no guarantee a CoA is loaded at the time of performing the tests, but creating an invoice requires it. That's why the post-install thing (and it's also a requirement if inheriting AccountTestInvoicingCommon).


      Inheriting from AccountTestInvoicingCommon, as explained in the commit message I linked in my first message, it's not improving the thing (at least in 16, in 17 it's more ironized), because it still requires `l10n_generic_coa` installed (and installed before the execution of this test), and its setup is very heavy, creating 2 companies (even if you only require one), so this would increase the test execution times a lot in the best case, or skipped without you really noticing in the worst (when generic CoA is not available).

      The added code is NOT boilerplate. It's legit code for making deterministic tests, the same as you may remove currency rates for having a deterministic environment. And it's totally harmless if you don't need it, because starting with, it's in test code, not in business code, and if you keep the previous status quo, the if it's not executed, so it doesn't affect any previous condition. This can only uncover other hidden defects on the modules being executed in post-install, and this is being patched at the same time.

      Replying to other threads answers, I don't think this will reverted, as AFAIK Odoo.sh is auto-installing the modules that hides the problem, and not installing any localization module, but I'm not expert of that platform, so I may be wrong.

      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 Stéphane Bidoul - 04:11 - 12 Mar 2025
    • Re: Tests failure when invoicing is involved after a change in Odoo upstream
      I have hit this issue in one of my projects where I run all tests post-install.

      Instead of changing all my tests, I chose to install l10n_generic_coa in CI, which was an easy solution in my specific situation.
      Maybe this can help others hitting the same problem.

      Best regards,

      -Stéphane


      On Wed, Feb 26, 2025 at 4:53 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
      Stefan and Denis, the reason for the Odoo patch may be legit, and it is. The problem is that it comes too late for the lifecycle of this version IMO, and more having in version 17 integrated the generic CoA into account for better practices. Anyway, this is just undisclosing a problem that has been hidden in the design of our OCA tests, them not being deterministic and really unit tests, as they are relying on previous state of data for being successful:

      - The company used is the one populated by default instead of using a full set of data including the company. This may be reasonable for execution times, and that's why the decision to just fix this condition installing an existing CoA instead of populating on each test a new company.
      - There's no guarantee a CoA is loaded at the time of performing the tests, but creating an invoice requires it. That's why the post-install thing (and it's also a requirement if inheriting AccountTestInvoicingCommon).


      Inheriting from AccountTestInvoicingCommon, as explained in the commit message I linked in my first message, it's not improving the thing (at least in 16, in 17 it's more ironized), because it still requires `l10n_generic_coa` installed (and installed before the execution of this test), and its setup is very heavy, creating 2 companies (even if you only require one), so this would increase the test execution times a lot in the best case, or skipped without you really noticing in the worst (when generic CoA is not available).

      The added code is NOT boilerplate. It's legit code for making deterministic tests, the same as you may remove currency rates for having a deterministic environment. And it's totally harmless if you don't need it, because starting with, it's in test code, not in business code, and if you keep the previous status quo, the if it's not executed, so it doesn't affect any previous condition. This can only uncover other hidden defects on the modules being executed in post-install, and this is being patched at the same time.

      Replying to other threads answers, I don't think this will reverted, as AFAIK Odoo.sh is auto-installing the modules that hides the problem, and not installing any localization module, but I'm not expert of that platform, so I may be wrong.

      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 Stéphane Bidoul - 07:36 - 28 Feb 2025
    • Re: Tests failure when invoicing is involved after a change in Odoo upstream
      Stefan and Denis, the reason for the Odoo patch may be legit, and it is. The problem is that it comes too late for the lifecycle of this version IMO, and more having in version 17 integrated the generic CoA into account for better practices. Anyway, this is just undisclosing a problem that has been hidden in the design of our OCA tests, them not being deterministic and really unit tests, as they are relying on previous state of data for being successful:

      - The company used is the one populated by default instead of using a full set of data including the company. This may be reasonable for execution times, and that's why the decision to just fix this condition installing an existing CoA instead of populating on each test a new company.
      - There's no guarantee a CoA is loaded at the time of performing the tests, but creating an invoice requires it. That's why the post-install thing (and it's also a requirement if inheriting AccountTestInvoicingCommon).


      Inheriting from AccountTestInvoicingCommon, as explained in the commit message I linked in my first message, it's not improving the thing (at least in 16, in 17 it's more ironized), because it still requires `l10n_generic_coa` installed (and installed before the execution of this test), and its setup is very heavy, creating 2 companies (even if you only require one), so this would increase the test execution times a lot in the best case, or skipped without you really noticing in the worst (when generic CoA is not available).

      The added code is NOT boilerplate. It's legit code for making deterministic tests, the same as you may remove currency rates for having a deterministic environment. And it's totally harmless if you don't need it, because starting with, it's in test code, not in business code, and if you keep the previous status quo, the if it's not executed, so it doesn't affect any previous condition. This can only uncover other hidden defects on the modules being executed in post-install, and this is being patched at the same time.

      Replying to other threads answers, I don't think this will reverted, as AFAIK Odoo.sh is auto-installing the modules that hides the problem, and not installing any localization module, but I'm not expert of that platform, so I may be wrong.

      Regards.
      by Pedro M. Baeza - 04:52 - 26 Feb 2025
    • Re: Tests failure when invoicing is involved after a change in Odoo upstream
      Thanks Pedro for pointing that out.

      But as Stefan said, the changes you propose should be applied in particular modules that do pull particular localisation, not every.

      As said also, a lead could be using AccountTestInvoicingCommon.

      Moreover, I think proposing a hook in Odoo's tests should be great to lower the code we need to introduce in our modules, or... What do you think?

      Thanks

      Le mer. 26 févr. 2025, 11:27, Stefan Rijnhart <notifications@odoo-community.org> a écrit :
      Yes, but the reason given by the Odoo devs for this change (https://github.com/odoo/odoo/pull/194799) is that CI can break on other CoAs than the generic one. That implies that it is considered bad practise to encourage it, and maybe we should not be doing this in (potentially, a lot of) OCA modules. Maybe using AccountTestInvoicingCommon is still the best solution?

      Like you say, OCA CI should mostly not be affected because l10n_generic_coa is still installed automatically if you don't depend on a localized chart. Do you really *need* to test these modules on databases with l10n_es? Maybe you can enforce the installation of it on the main company with an extra step in your CI.

      On 25-02-2025 15:42, Pedro M. Baeza wrote:
      I write to inform you that Odoo has performed a change in "stable" 16.0 in this commit:


      that is affecting CIs, specially on those integration ones that OCA implementers perform combining all the modules of a specific instance.

      This change avoids the auto-install of one CoA on the existing demo main company, as it doesn't comply with a country CoA unless you have l10n_us installed. Some tests inheriting from  AccountTestInvoicingCommon won't fail if l10n_generic_coa is installed, but it's also a requirement that can't always be fulfilled.

      The impact of this is huge across OCA, as basically every test creating an invoice is affected. OCA CI may not be red, but use it in other place and you may be doomed.


      Thus, from Tecnativa, we have started a massive pull request campaign fixing most of the common modules with this problem.

      The strategy has been to force a load of the generic CoA or the first existing one into the main company if starting the test, it doesn't have any. Check the minimum example at:


      If you are inheriting from AccountTestInvoicingCommon, the strategy should be different. By default, you won't have a red CI, but the tests are skipped, which is also undesirable. Thus, you have to do the work before calling super. Check an example here:


      v17 is not affected for now. Let's hope it continues this way...

      Regards.

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



      -- 
Opener B.V. - Business solutions driven by open source collaboration

Stefan Rijnhart - Consultant/developer

mail: stefan@opener.amsterdam
tel: +31 (0) 6 1447 8606
web: https://opener.amsterdam

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

      by Denis Roussel - 04:21 - 26 Feb 2025

  • Rotor Live Visitor List

    Rotor Live 2025

    Greetings Exhibitor,

    Reaching out to confirm if you’re interested in the Rotor Live 2025 attendee list.

    The event will be held 08 - 09 Mar 2025 in Rennbahn Iffezheim, Iffezheim, Germany , and the list provides 4,576 registrant records with contact information, roles...


    Thanks & Regards
    Monda Byrd
    by monda.byrd@leadcritics.cloud - 08:41 - 25 Feb 2025
  • What OCA modules to use for a French micro-enterprise 
    Hi,

I don't know if this the right channel, but asking for help on odoo.com 
about OCA modules  just doesn't seem the correct place.

My question is what OCA modules to use for a French micro-enterprise 
running CE.

Looking forward to any and all replies.

Regards,

Jeroen Baten


-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands
    by Jeroen Baten - 05:31 - 24 Feb 2025

    4 replies 4 replies

  • Application for PSC Membership – OCA Spanish Localization

    Hi OCA members,

    I hope you’re doing well.

    I would like to express my interest in joining the Project Steering Committee (PSC) for the Spanish Localization project of the Odoo Community Association (OCA). Over the past two years, I have actively contributed to improving and maintaining the Spanish localization, focusing on key areas that directly impact its accuracy and functionality.

    My Contributions to OCA Spanish Localization:

    • 45 Pull Requests (PRs) submitted, primarily focused on fixing calculation errors in AEAT tax models and ensuring compliance with regulatory updates.

    • Enhancing AEAT tax reports, updating models to include new fields and features required by the tax authorities.

    • Active issue reporting and resolution, helping maintain the reliability and accuracy of the localization.

    • Code reviews and collaboration, ensuring high-quality contributions by reviewing PRs and engaging in technical discussions.

    • Community involvement, participating in discussions and contributing to decision-making processes related to localization improvements.

    You can find all my contributions to the OCA: PRs in OCA

    I believe my experience and contributions can help further improve the Spanish localization, and I would love the opportunity to take on more responsibility within the PSC. Please let me know if you need any additional information to support my application.

    Looking forward to your feedback.

    Best regards,
    Emilio Pascual
    GitHub: EmilioPascual


    by Emilio Pascual - 04:21 - 24 Feb 2025

    6 replies 6 replies

    • Re: Application for PSC Membership – OCA Spanish Localization
      Since people are still asking about PSC membership in this mailing list, in the future I would suggest to refrain from replying about the application itself and instead just provide info about opening a PR in https://github.com/OCA/repo-maintainer-conf/pulls and then moving the discussion with the relevant maintainers there. 

      Cheers 

      Francesco

      Il giorno lun 24 feb 2025 alle ore 18:13 Pedro M. Baeza <notifications@odoo-community.org> ha scritto:
      Certainly there are roles of every type here. I'm not usually the "nice guy", I'm the "do it" and direct one, but it also depends on the topic and context.

      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 - 06:46 - 24 Feb 2025
    • Re: Application for PSC Membership – OCA Spanish Localization
      Certainly there are roles of every type here. I'm not usually the "nice guy", I'm the "do it" and direct one, but it also depends on the topic and context.

      Regards.
      by Pedro M. Baeza - 06:11 - 24 Feb 2025
    • Re: Application for PSC Membership – OCA Spanish Localization

      Hi Jeroen,

      while one can disagree with the tone of such a message, there are currently no guidelines about "how" something should be communicated. Maybe there should be, but I'm not aware of them.

      I would say the decision is valid though - PSC are free to determine who else can become PSC. Not unless some other Spanish PSC or otherwise senior contributors disagree and we have another infight on our hands (it always seems to be l10n-spain.. :-)

      I would not say that unfriendly tones are common in OCA, as you will notice when you visit the OCA days come september! Nice that you decided to also contribute.

      -Tom


      On 2/24/25 16:47, Jeroen Baten wrote:
      Hi Pedro,

Just out of curiosity I have this question. Is this (your reply) in 
general the way to reply within the OCA community to somebody who 
publicly offers his energy and efforts to further the community?

I have been a team leader for several years, and it taught me to always 
compliment in public, and keep messages like the one below private.

As a new very junior active member myself it makes me wonder if this is 
the community for me.

Looking forward to your (public) reply on this question.

Regards,

Jeroen Baten


Op 24-02-2025 om 16:32 schreef Pedro M. Baeza:

> Hi, Emilio,

>

> Your contributions are of course very welcome, but all of them has 

> been focused on little improvements on existing things, and requires 

> supervision for even little things that have been talked before in 

> other versions (see for example the latest one in 

> https://github.com/OCA/l10n-spain/pull/3994#pullrequestreview-2635555858 

> that was already told in 

> https://github.com/OCA/l10n-spain/pull/3389#pullrequestreview-1856990061, 

> and that one required a lot of review waves), so I don't consider 

> scaling up to be part of the PSC is adequate. Besides, current PSC 

> members have proved to be enough to handle the current needs of the repo.

>

> Regards.

>

> _______________________________________________

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

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

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

>

-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands

      _______________________________________________
      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 - 05:46 - 24 Feb 2025
    • Re: Application for PSC Membership – OCA Spanish Localization
      Well, I always keep everything in public, for the good or the bad, and he has also written in public in the first place instead of doing his request in the proper channel, which is not public.

      Having rights in certain things is a meritocracy, and as so, this has been judged that way. That doesn't mean he can't contribute. It's just the direct merge rights.

      Regards.
      by Pedro M. Baeza - 04:56 - 24 Feb 2025
    • Re: Application for PSC Membership – OCA Spanish Localization 
      Hi Pedro,

Just out of curiosity I have this question. Is this (your reply) in 
general the way to reply within the OCA community to somebody who 
publicly offers his energy and efforts to further the community?

I have been a team leader for several years, and it taught me to always 
compliment in public, and keep messages like the one below private.

As a new very junior active member myself it makes me wonder if this is 
the community for me.

Looking forward to your (public) reply on this question.

Regards,

Jeroen Baten


Op 24-02-2025 om 16:32 schreef Pedro M. Baeza:

> Hi, Emilio,

>

> Your contributions are of course very welcome, but all of them has 

> been focused on little improvements on existing things, and requires 

> supervision for even little things that have been talked before in 

> other versions (see for example the latest one in 

> https://github.com/OCA/l10n-spain/pull/3994#pullrequestreview-2635555858 

> that was already told in 

> https://github.com/OCA/l10n-spain/pull/3389#pullrequestreview-1856990061, 

> and that one required a lot of review waves), so I don't consider 

> scaling up to be part of the PSC is adequate. Besides, current PSC 

> members have proved to be enough to handle the current needs of the repo.

>

> Regards.

>

> _______________________________________________

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

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

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

>

-- 
Jeroen Baten              | EMAIL :  JBATEN@I2RS.NL
  ____  _  __              | web   :  www.i2rs.nl
   |  )|_)(_               | tel   :  +31 (0)648519096
  _|_/_| \__)              | Frisolaan 16, 4101 JK, Culemborg, the Netherlands
      by Jeroen Baten - 04:46 - 24 Feb 2025

  • Let's boost the OCA together
    Internal communication: Dear contributors, OCA has accounts in social media and is posting regularly. I know some of you may consider this ridiculous, but simple like [...] ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

    Dear contributors, 

    OCA has accounts in social media and is posting regularly.  I know some of you may consider this ridiculous, but simple like or better a repost may help widespread the OCA awareness and attract people, who would assist us to make the OCA mightier together. I personally know several people who have discovered OCA thanks to the social media.

    Likes are still free, same are reposts. And it shouldn't take that much time to click that button) So let's cut some time from funny kitten videos and dedicate it to the OCA post. This is probably one of the easiest and yet most efficient ways of contributing.

    Best regards,

    photograph
    Ivan Sokolov
     Cetmix Odoo Solutions
    cetmix.com
    Facebook Twitter LinkedIn Instagram 
    This message is sent using Mail Messages Easy app


    Powered by Messages Easy Pro

    by "Ivan Sokolov via Cetmix OÜ" <team@cetmix.com> - 10:26 - 24 Feb 2025
  • Fwd: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh

    Hello OCA contributors,


    I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


    Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


    Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


    Many thanks!


    Dear OSS Community,


    To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
    Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
    As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
    The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

    At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
    Each interview response will be treated confidentially and will be processed in the end paper anonymously.
    Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

    Thank you in advance for assisting in this research.

    Best Regards,  Dylan 

    Dylan Kaekelbergh

    0491 62 34 82
    Student KU Leuven


    Long URL: https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

     

    Short URL: https://forms.office.com/e/esVRbvAPK7

     

     

     

    Virginie Dewulf
    Executive Director
    +32 477 64 17 20



    by Virginie Dewulf - 09:45 - 24 Feb 2025

    1 attachments 1 attachments

    image008.png

    5 replies 5 replies

    • Re: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh
      Hello Contributors,

      Dylan who is studying governance of open source projects is still looking for a few participants for his research.

      All info are below. Many thanks from him and myself. 

      I think this can lead to a better knowledge about our way of working together, which is not always easy as we can see from several messages on this mailing list for the past days.

      Enjoy the day!
      Virginie Dewulf
      Executive Director
      +32 477 64 17 20


      Le lun. 24 févr. 2025 à 09:42, Virginie Dewulf <virginie@odoo-community.org> a écrit :

      Hello OCA contributors,


      I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


      Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


      Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


      Many thanks!


      Dear OSS Community,


      To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
      Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
      As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
      The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

      At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
      Each interview response will be treated confidentially and will be processed in the end paper anonymously.
      Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

      Thank you in advance for assisting in this research.

      Best Regards,  Dylan 

      Dylan Kaekelbergh

      0491 62 34 82
      Student KU Leuven


      Long URL: https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

       

      Short URL: https://forms.office.com/e/esVRbvAPK7

       

       

       

      Virginie Dewulf
      Executive Director
      +32 477 64 17 20



      by Virginie Dewulf - 04:21 - 2 Apr 2025

      1 attachments 1 attachments

      image008.png
    • Re: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh

      Hi Graeme,

      oh that is awesome. Would you mind to sent it directly to me when you found a pdf of the document or the link?

      Best Frederik

      Am 24.02.25 um 12:17 schrieb Graeme Gellatly:
      My masters thesis was basically this. Motivations of contributors within gated and non gated open source ecosystems. Something like that. Maybe I can dig it out. I think it got published somewhere insignificant.

      On Mon, Feb 24, 2025 at 9:46 PM Virginie Dewulf <virginie@odoo-community.org> wrote:

      Hello OCA contributors,


      I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


      Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


      Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


      Many thanks!


      Dear OSS Community,


      To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
      Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
      As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
      The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

      At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
      Each interview response will be treated confidentially and will be processed in the end paper anonymously.
      Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

      Thank you in advance for assisting in this research.

      Best Regards,  Dylan 

      Dylan Kaekelbergh

      0491 62 34 82
      Student KU Leuven


      Long URL: https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

       

      Short URL: https://forms.office.com/e/esVRbvAPK7

       

       

       

      Virginie Dewulf
      Executive Director
      +32 477 64 17 20



      _______________________________________________
      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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
      by Frederik Kramer - 01:56 - 24 Feb 2025
    • Re: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh
      My masters thesis was basically this. Motivations of contributors within gated and non gated open source ecosystems. Something like that. Maybe I can dig it out. I think it got published somewhere insignificant.

      On Mon, Feb 24, 2025 at 9:46 PM Virginie Dewulf <virginie@odoo-community.org> wrote:

      Hello OCA contributors,


      I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


      Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


      Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


      Many thanks!


      Dear OSS Community,


      To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
      Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
      As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
      The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

      At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
      Each interview response will be treated confidentially and will be processed in the end paper anonymously.
      Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

      Thank you in advance for assisting in this research.

      Best Regards,  Dylan 

      Dylan Kaekelbergh

      0491 62 34 82
      Student KU Leuven


      Long URL: https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

       

      Short URL: https://forms.office.com/e/esVRbvAPK7

       

       

       

      Virginie Dewulf
      Executive Director
      +32 477 64 17 20



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

      by Graeme Gellatly - 12:16 - 24 Feb 2025
    • Re: Fwd: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh

      Har har probably work for the Governance Working Group. But yes that sounds very valuable. In order to give a multidimensional feedback, we should probably be at least 2 persons participating in that meeting. I will put the organization of that on my Agenda and discuss it with Daniel and Joel

      Best Frederik

      Am 24.02.25 um 09:46 schrieb Virginie Dewulf:

      Hello OCA contributors,


      I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


      Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


      Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


      Many thanks!


      Dear OSS Community,


      To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
      Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
      As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
      The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

      At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
      Each interview response will be treated confidentially and will be processed in the end paper anonymously.
      Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

      Thank you in advance for assisting in this research.

      Best Regards,  Dylan 

      Dylan Kaekelbergh

      0491 62 34 82
      Student KU Leuven


      Long URL: https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

       

      Short URL: https://forms.office.com/e/esVRbvAPK7

       

       

       

      Virginie Dewulf
      Executive Director
      +32 477 64 17 20



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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
      by Frederik Kramer - 11:11 - 24 Feb 2025
    • Re: Fwd: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh
      Internal communication: Looks like a really good idea! I'm in) ----- Original message ----- Date: Feb 24, 2025, 9:47:21 AM From: Virginie Dewulf Subject: Fwd: KU Leuven [...] ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

      Looks like a really good idea! I'm in)


      Best regards,

      photograph
      Ivan Sokolov
       Cetmix Odoo Solutions
      cetmix.com
      Facebook Twitter LinkedIn Instagram 
      This message is sent using Mail Messages Easy app


      ----- Original message -----
      Date: Feb 24, 2025, 9:47:21 AM
      From: Virginie Dewulf
      Subject: Fwd: KU Leuven - Link to Interview form Thesis research Dylan Kaekelbergh

      Hello OCA contributors,


      I forward a message from a student from Belgium, currently studying the governance of open source projects. The OCA is a Case Study for his master thesis.


      Would you help him? His findings will certainly help us understand how we currently work together and give us ideas to improve this together!


      Schedule your meeting with him here:https://forms.office.com/e/esVRbvAPK7


      Many thanks!


      Dear OSS Community,


      To introduce myself, I’m Dylan Kaekelbergh, master student at KU Leuven and fascinated by OSS Communities.
      Software quality and technology thrives due to the effort and contributions made by Open-Source Software communities. The way that a community of volunteers comes together and work towards a shared vision poses an interesting field of study. Understanding this more deeply can provide insights to help more OSS projects graduate and deduct significant best practices.
      As part of a Master Thesis, I’m conducting a qualitative empirical research on Governance configurations in OSS Communities to deeper explore this topic.
      The study has the aim to explore the relationship between motivations of contributors and the governance configurations that the communities upholds. Additionally, the study explores if multiple governance configurations can exist within a community and how these contribute to the success of a community.

      At this moment, I’m looking for OSS Community members and contributors of the Odoo Community Association to participate in a one hour (max. 1,5h) interview. The interviews will be conducted over a period of 4 weeks.
      Each interview response will be treated confidentially and will be processed in the end paper anonymously.
      Each interview will be conducted via Microsoft Teams. (If preferred F2F interviews in KU Leuven Brussels can also be organized)

      Thank you in advance for assisting in this research.

      Best Regards,  Dylan 

      Dylan Kaekelbergh

      0491 62 34 82
      Student KU Leuven


      Long URL:  https://forms.office.com/Pages/ResponsePage.aspx?id=m1hzOUCetU6ADrC2OD0WIcMj2GkfyiVFgEFeY96GiwhUMTVNNDNBWEJPSDhTOTRUMzFFVktXMVpJSy4u

       

      Short URL: https://forms.office.com/e/esVRbvAPK7

       

       

       

      Virginie Dewulf
      Executive Director
      +32 477 64 17 20



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

      Powered by Messages Easy Pro

      by "Ivan Sokolov via Cetmix OÜ" <team@cetmix.com> - 10:21 - 24 Feb 2025
  • Seeking Advice on Migrating Custom Pricing Logic to Built-in Features in Odoo 17

    Dear Community,

    I hope this message finds you well. I’m reaching out for advice on improving an Odoo 17 setup related to pricing strategies.

    Current Scenario

    The customer has configured 5 pricelists, with each partner assigned to one of them. Additionally, a simple custom development—let’s call it "On Sale"—has been implemented. This feature allows setting:

    • A customer
    • A product
    • A fixed price
    • A date interval

    When a product is selected in a sale order line, the system queries the "On Sale" model. If a match is found, the custom price is applied; otherwise, the default partner’s pricelist is used.

    My Goal

    I’d like to migrate this custom development to built-in or OCA features and remove the custom code. However, I’m struggling to replicate the same user experience (UX) and pricing logic.

    The Challenge

    The fallback mechanism is where I’m stuck. If I:

    1. Create a dedicated pricelist per partner with all relevant "On Sale" records, and
    2. Set this new pricelist on the partner,

    It works fine only if a match exists. However, if there’s no matching rule, I need a way to fallback to the original pricelist assigned to the partner. I haven't found a straightforward way to set a fallback pricelist for each partner using the built-in system.

    Possible Solution?

    The customer is currently using the "Multiple Prices per Product" pricing strategy. I’m considering switching to "Advanced Price Rules" instead. This might allow me to:

    • Create an "On Sale" pricelist for each partner.
    • Set up a "Coordinator" pricelist per partner, with two rules:
      1. A rule that prioritizes the "On Sale" pricelist.
      2. A fallback rule that applies the regular pricelist if no custom price applies.

    In theory, this setup should replicate the current logic while using built-in features. However, I’m not entirely sure if this will maintain the desired behavior without introducing unexpected issues.

    My Questions

    • Is switching to "Advanced Price Rules" the right approach for this scenario?
    • Has anyone faced a similar situation? If so, how did you manage the migration while keeping the UX intact?
    • Are there alternative methods to implement a fallback pricelist for each partner without custom development?

    Any suggestions or shared experiences would be greatly appreciated. Thank you for your time and support!

    Best regards,
    \rrebollo

    by Ing. Rolando Pérez Rebollo - 02:26 - 22 Feb 2025

    2 replies 2 replies

    • Re: Seeking Advice on Migrating Custom Pricing Logic to Built-in Features in Odoo 17 
      Thank U very much Pedro, when I tried to implement the approach 
mentioned before I faced some obstacles (mainly due to when price list 
rules are of same specificity Odoo picks the most expensive) then I 
played with the configuration until finally got it by myself. Your 
confirmation gives me peace of mind. Thanks again for taking the time to 
collaborate.

On 2/23/25 05:23, Pedro M. Baeza wrote:

> You have to set pricelists setting as advanced price rules, define all 

> the lines for specific prices, and add an extra final rule for "All 

> products", Computation = Formula, Based on = Other Pricelist, and 

> select the base pricelist.

>

> 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 Ing. Rolando Pérez Rebollo - 11:51 - 23 Feb 2025
    • Re: Seeking Advice on Migrating Custom Pricing Logic to Built-in Features in Odoo 17
      You have to set pricelists setting as advanced price rules, define all the lines for specific prices, and add an extra final rule for "All products", Computation = Formula, Based on = Other Pricelist, and select the base pricelist.

      Regards.
      by Pedro M. Baeza - 11:21 - 23 Feb 2025
  • Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0
    Hello,

    approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

    At first we thought version 18.0 is not affected but that was wrong.

    Here is the video with a manual fix of the fiscal positions:

    At Odoo SA we have a open bug report but no response so far:

    Issue Type: Critical Bug

    Module: Accounting / German Localization

    Odoo Versions: [16.0, 17.0]

    Also affected is [18.0]

    Impacted Environment:

    * Both
    * Not affected is 17.04., 18.0


    Summary:

    The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


    Steps to Reproduce:

    1. Configure the German localization module.
    2. Create a new partner with an address located in Germany.
    3. Assign a VAT ID to the partner.
    4. Create a sales order or invoice for the partner.
    5. Observe the fiscal position that gets assigned automatically (wrong).

    Expected Behavior:

    * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
    * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


    Observed Behavior:

    * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
    * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
    * This can result in non-compliance with German tax regulations and incorrect tax reporting.


    Impact:

    * Financial discrepancies due to incorrect tax application.
    * Compliance risks with German tax authorities.
    * Increased manual corrections required by users.

    Suggested Fix:

    * Review and correct the fiscal position assignment logic in the German localization module.
    * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
    * Implement additional validation checks to avoid incorrect fiscal position assignments.
    * I have proposed a quick fix solution in my video.

    Video:


    https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


    Priority: 

    Critical

    Additional Notes:


    * This issue was observed in trainings for our customers.
    * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
    * Affected users have reported increased manual workload due to incorrect assignments.
    * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
    * We have to investigate this now on all customer databases (german companies).
    * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


    Thorsten Vocks

    openBIG.org
    Dipl. Kaufmann (FH)
    Porscheweg 4-6
    49661 Cloppenburg

    Phone: +49 4471 8409000
    Fax: +49 4471 84090009
    Mail: thorsten.vocks@openbig.org

                  
    by Thorsten Vocks - 01:45 - 21 Feb 2025

    6 replies 6 replies

    • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0
      Hello, 
              


      Am Mo., 24. Feb. 2025 um 17:22 Uhr schrieb Christian Zöllner <notifications@odoo-community.org>:
      Hi Thorsten,

      I don't think anything has changed in the search logic for the fiscal positions in regard of the found problem. But the fiscal position “Business partner EU (with VAT ID)” was only changed to “auto apply” about 1 year ago. This should not have affected running systems, as an update of the accounting app has no effect on the fiscal positions, as these are set to “no update”.

      I have investigated the change and i am OK with that change, however it should not affect the logic who a fiscal position is assigned to a german partner.
      As the sequence of the rule is higher as the    “Business partner EU (with VAT ID)” rule Odoo should assign in any case (VAT ID / No VatID in combination with country germany) to "Domestic partner" / "Geschäftspartner Inland".
      That's who it was done in the past.


       


      I would prefer to create another fiscal position “Domestic business partner (with VAT ID)” rather than changing the country group “European Union”, because the latter may be used in other processes in Odoo and Germany should therefore remain included.

      If you check the video you have seen that i duplicated the country group, however i would be fine with a duplication of “Business partner EU (with VAT ID)” leading to:
      “Business partner EU (with VAT ID)”
      “Business partner EU (without VAT ID)”

      both before 
      “Business partner EU (with VAT ID)”


       

      Thank you for sharing all those informations in this mailing list.



      Yesterday i have received answer from Odoo support.
      They will investigate it, so no final answer yet.

      Best regards
      Thorsten
       

      Best Regards
      Christian
      Intero Technologies GmbH

      Von: "Thorsten Vocks" <notifications@odoo-community.org>
      An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Gesendet: Freitag, 21. Februar 2025 17:38:15
      Betreff: Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0

      Hallo Frederik,

      This revert

      https://github.com/odoo/odoo/commit/af3a24c010d3e7158c1324f36a1529c510d886a6

      and this original commit

      https://github.com/odoo/odoo/commit/bcaf8cb859dc2f7e975d180ba0fc49da20204557

      introduced and reverted the problematic code if i am not mistaken. I didn't review the code duely, but afais that the problematic code should only be in databases / data that have been created between

      24th of September 2024 and 25th of October 2024

      That means customers with versions of Odoo 16, 17 and 18 that either updated their code in that time frame or installed new databases should be affected. Others hopefully not!



      Unfortunately not.
      I could recapture that today on Odoo runbot v18.
      Last week on v16, v17 (current runbot versions).
      And all my other testing was also databases on odoo runbot.

      I guess the revert didn't fix the introduced problem.
      Honestly i am not 100% sure which exact commit introduced 
      the issue.

       
      Best regards
      Thorsten


      Best and thanks for circulating this

      Frederik

      Am 21.02.25 um 13:47 schrieb Thorsten Vocks:
      Hello,

      approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

      At first we thought version 18.0 is not affected but that was wrong.

      Here is the video with a manual fix of the fiscal positions:

      At Odoo SA we have a open bug report but no response so far:

      Issue Type: Critical Bug

      Module: Accounting / German Localization

      Odoo Versions: [16.0, 17.0]

      Also affected is [18.0]

      Impacted Environment:

      * Both
      * Not affected is 17.04., 18.0


      Summary:

      The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


      Steps to Reproduce:

      1. Configure the German localization module.
      2. Create a new partner with an address located in Germany.
      3. Assign a VAT ID to the partner.
      4. Create a sales order or invoice for the partner.
      5. Observe the fiscal position that gets assigned automatically (wrong).

      Expected Behavior:

      * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
      * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


      Observed Behavior:

      * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
      * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
      * This can result in non-compliance with German tax regulations and incorrect tax reporting.


      Impact:

      * Financial discrepancies due to incorrect tax application.
      * Compliance risks with German tax authorities.
      * Increased manual corrections required by users.

      Suggested Fix:

      * Review and correct the fiscal position assignment logic in the German localization module.
      * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
      * Implement additional validation checks to avoid incorrect fiscal position assignments.
      * I have proposed a quick fix solution in my video.

      Video:


      https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


      Priority: 

      Critical

      Additional Notes:


      * This issue was observed in trainings for our customers.
      * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
      * Affected users have reported increased manual workload due to incorrect assignments.
      * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
      * We have to investigate this now on all customer databases (german companies).
      * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


      Thorsten Vocks

      openBIG.org
      Dipl. Kaufmann (FH)
      Porscheweg 4-6
      49661 Cloppenburg

      Phone: +49 4471 8409000
      Fax: +49 4471 84090009
      Mail: thorsten.vocks@openbig.org

                    

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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247

      _______________________________________________
      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

      by Thorsten Vocks - 01:07 - 25 Feb 2025
    • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0
      Hi Thorsten,

      I don't think anything has changed in the search logic for the fiscal positions in regard of the found problem. But the fiscal position “Business partner EU (with VAT ID)” was only changed to “auto apply” about 1 year ago. This should not have affected running systems, as an update of the accounting app has no effect on the fiscal positions, as these are set to “no update”.


      I would prefer to create another fiscal position “Domestic business partner (with VAT ID)” rather than changing the country group “European Union”, because the latter may be used in other processes in Odoo and Germany should therefore remain included.

      Thank you for sharing all those informations in this mailing list.

      Best Regards
      Christian
      Intero Technologies GmbH

      Von: "Thorsten Vocks" <notifications@odoo-community.org>
      An: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Gesendet: Freitag, 21. Februar 2025 17:38:15
      Betreff: Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0

      Hallo Frederik,

      This revert

      https://github.com/odoo/odoo/commit/af3a24c010d3e7158c1324f36a1529c510d886a6

      and this original commit

      https://github.com/odoo/odoo/commit/bcaf8cb859dc2f7e975d180ba0fc49da20204557

      introduced and reverted the problematic code if i am not mistaken. I didn't review the code duely, but afais that the problematic code should only be in databases / data that have been created between

      24th of September 2024 and 25th of October 2024

      That means customers with versions of Odoo 16, 17 and 18 that either updated their code in that time frame or installed new databases should be affected. Others hopefully not!



      Unfortunately not.
      I could recapture that today on Odoo runbot v18.
      Last week on v16, v17 (current runbot versions).
      And all my other testing was also databases on odoo runbot.

      I guess the revert didn't fix the introduced problem.
      Honestly i am not 100% sure which exact commit introduced 
      the issue.

       
      Best regards
      Thorsten


      Best and thanks for circulating this

      Frederik

      Am 21.02.25 um 13:47 schrieb Thorsten Vocks:
      Hello,

      approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

      At first we thought version 18.0 is not affected but that was wrong.

      Here is the video with a manual fix of the fiscal positions:

      At Odoo SA we have a open bug report but no response so far:

      Issue Type: Critical Bug

      Module: Accounting / German Localization

      Odoo Versions: [16.0, 17.0]

      Also affected is [18.0]

      Impacted Environment:

      * Both
      * Not affected is 17.04., 18.0


      Summary:

      The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


      Steps to Reproduce:

      1. Configure the German localization module.
      2. Create a new partner with an address located in Germany.
      3. Assign a VAT ID to the partner.
      4. Create a sales order or invoice for the partner.
      5. Observe the fiscal position that gets assigned automatically (wrong).

      Expected Behavior:

      * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
      * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


      Observed Behavior:

      * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
      * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
      * This can result in non-compliance with German tax regulations and incorrect tax reporting.


      Impact:

      * Financial discrepancies due to incorrect tax application.
      * Compliance risks with German tax authorities.
      * Increased manual corrections required by users.

      Suggested Fix:

      * Review and correct the fiscal position assignment logic in the German localization module.
      * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
      * Implement additional validation checks to avoid incorrect fiscal position assignments.
      * I have proposed a quick fix solution in my video.

      Video:


      https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


      Priority: 

      Critical

      Additional Notes:


      * This issue was observed in trainings for our customers.
      * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
      * Affected users have reported increased manual workload due to incorrect assignments.
      * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
      * We have to investigate this now on all customer databases (german companies).
      * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


      Thorsten Vocks

      openBIG.org
      Dipl. Kaufmann (FH)
      Porscheweg 4-6
      49661 Cloppenburg

      Phone: +49 4471 8409000
      Fax: +49 4471 84090009
      Mail: thorsten.vocks@openbig.org

                    

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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247

      _______________________________________________
      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 Christian Zöllner - 05:21 - 24 Feb 2025
    • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0 
      Hi,

thx for putting that much work into analysis and sharing your findings.

Do we have a proper link to the upstream issue?

cheers,
Peter

On 21.02.25 13:47, Thorsten Vocks wrote:

> Hello,

> 

> approx. 7 days ago we have detected a critical issue regarding the 

> fiscal position assignation for setups with installed german 

> localisation (*l10n_de*). Obviously all databases created / last updated 

> approx. 20th October are affected.

> 

> *At first we thought version 18.0 is not affected but that was wrong.*

> 

> Here is the video with a manual fix of the fiscal positions:

> 

> https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view 

> <https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view>

> 

> *At Odoo SA we have a open bug report but no response so far:*

> 

> Issue Type: Critical Bug

> 

> Module: Accounting / German Localization

> 

> Odoo Versions: [16.0, 17.0]

> 

> *Also affected is [18.0]*

> 

> Impacted Environment:

> 

> * Both

> ** Not affected is 17.04., 18.0*

> 

> 

> *Summary:*

> 

> The fiscal position is being incorrectly assigned to partners in the 

> German localization (German B2B partners with Vat-ID assigned). This 

> leads to incorrect tax calculations and potential legal compliance 

> issues for users relying on automated fiscal position determination.

> 

> 

> *Steps to Reproduce:*

> 

> 1. Configure the German localization module.

> 2. Create a new partner with an address located in Germany.

> 3. Assign a VAT ID to the partner.

> 4. Create a sales order or invoice for the partner.

> 5. Observe the fiscal position that gets assigned automatically (wrong).

> 

> *Expected Behavior:*

> 

> * The fiscal position should be assigned based on the VAT ID, address, 

> and configured fiscal rules.

> * The correct tax rates and exemptions should be applied in accordance 

> with German tax regulations.

> 

> 

> *Observed Behavior:*

> 

> * The fiscal position is either not assigned correctly or does not 

> reflect the expected tax rules.

> * Especially B2B partners receive an incorrect fiscal position, leading 

> to incorrect tax calculations.

> * This can result in non-compliance with German tax regulations and 

> incorrect tax reporting.

> 

> 

> *Impact:*

> 

> * Financial discrepancies due to incorrect tax application.

> * Compliance risks with German tax authorities.

> * Increased manual corrections required by users.

> 

> *Suggested Fix:*

> 

> * Review and correct the fiscal position assignment logic in the German 

> localization module.

> * Ensure that VAT IDs and partner addresses are properly considered when 

> determining fiscal positions.

> * Implement additional validation checks to avoid incorrect fiscal 

> position assignments.

> * I have proposed a quick fix solution in my video.

> 

> *Video:*

> 

> *

> *https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view 

> <https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view>

> 

> 

> *Priority: *

> 

> Critical

> 

> *Additional Notes:*

> 

> *

> ** This issue was observed in trainings for our customers.

> * All customers running on v16, v17, *v18 *in Odoo are effected (except 

> they assign fixed fiscal positions to partners, which happens in some 

> rare cases).

> * Affected users have reported increased manual workload due to 

> incorrect assignments.

> * Maybe they have created wrong account moves. Due to audit_trail we 

> cannot fix that easily.

> * We have to investigate this now on all customer databases (german 

> companies).

> * We strongly recommend you to warn other german customers working on a 

> v16, v17, *v18* version.

> 

> 

> Thorsten Vocks

> 

> openBIG.org

> Dipl. Kaufmann (FH)

> Porscheweg 4-6

> 49661 Cloppenburg

> 

> Phone: +49 4471 8409000

> Fax: +49 4471 84090009

> Mail: thorsten.vocks@openbig.org <mailto:thorsten.vocks@openbig.org>

> Web: http://www.openbig.org <http://www.openbig.org>

> 

> _______________________________________________

> 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>

> 

mit freundlichen Grüßen,
Peter Niederlag

-- 
Dipl. Ökonom Peter Niederlag
Geschäftsführender Gesellschafter

Lösungen für digitale Zeiten
Agile DevOps, Cloud, TYPO3, Odoo und Linux

Datenbetrieb Technologie UG(haftungsbeschränkt)
Lipper Hellweg 146,  33605 Bielefeld
Geschäftsführer: Peter Niederlag
HRB 41826 Amtsgericht Bielefeld
Fon 0521 / 446 958 60
Fax 0521 / 446 958 69
      by Peter Niederlag - 12:41 - 22 Feb 2025
    • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0
      Hallo Frederik,

      This revert

      https://github.com/odoo/odoo/commit/af3a24c010d3e7158c1324f36a1529c510d886a6

      and this original commit

      https://github.com/odoo/odoo/commit/bcaf8cb859dc2f7e975d180ba0fc49da20204557

      introduced and reverted the problematic code if i am not mistaken. I didn't review the code duely, but afais that the problematic code should only be in databases / data that have been created between

      24th of September 2024 and 25th of October 2024

      That means customers with versions of Odoo 16, 17 and 18 that either updated their code in that time frame or installed new databases should be affected. Others hopefully not!



      Unfortunately not.
      I could recapture that today on Odoo runbot v18.
      Last week on v16, v17 (current runbot versions).
      And all my other testing was also databases on odoo runbot.

      I guess the revert didn't fix the introduced problem.
      Honestly i am not 100% sure which exact commit introduced 
      the issue.

       
      Best regards
      Thorsten


      Best and thanks for circulating this

      Frederik

      Am 21.02.25 um 13:47 schrieb Thorsten Vocks:
      Hello,

      approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

      At first we thought version 18.0 is not affected but that was wrong.

      Here is the video with a manual fix of the fiscal positions:

      At Odoo SA we have a open bug report but no response so far:

      Issue Type: Critical Bug

      Module: Accounting / German Localization

      Odoo Versions: [16.0, 17.0]

      Also affected is [18.0]

      Impacted Environment:

      * Both
      * Not affected is 17.04., 18.0


      Summary:

      The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


      Steps to Reproduce:

      1. Configure the German localization module.
      2. Create a new partner with an address located in Germany.
      3. Assign a VAT ID to the partner.
      4. Create a sales order or invoice for the partner.
      5. Observe the fiscal position that gets assigned automatically (wrong).

      Expected Behavior:

      * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
      * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


      Observed Behavior:

      * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
      * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
      * This can result in non-compliance with German tax regulations and incorrect tax reporting.


      Impact:

      * Financial discrepancies due to incorrect tax application.
      * Compliance risks with German tax authorities.
      * Increased manual corrections required by users.

      Suggested Fix:

      * Review and correct the fiscal position assignment logic in the German localization module.
      * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
      * Implement additional validation checks to avoid incorrect fiscal position assignments.
      * I have proposed a quick fix solution in my video.

      Video:


      https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


      Priority: 

      Critical

      Additional Notes:


      * This issue was observed in trainings for our customers.
      * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
      * Affected users have reported increased manual workload due to incorrect assignments.
      * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
      * We have to investigate this now on all customer databases (german companies).
      * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


      Thorsten Vocks

      openBIG.org
      Dipl. Kaufmann (FH)
      Porscheweg 4-6
      49661 Cloppenburg

      Phone: +49 4471 8409000
      Fax: +49 4471 84090009
      Mail: thorsten.vocks@openbig.org

                    

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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247

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

      by Thorsten Vocks - 05:36 - 21 Feb 2025
    • Re: Critical Fiscal Position Assignation Issue (only Germany) - 16.0 17.0 18.0

      Thanks Thorsten,

      that is an especially "funny" one that shows how important proper functional (regression) testing actually is. Especially but not limited to accounting!

      The responsible guys at Odoo seem to have had the global case (some cases in US, NL and BL) in mind but didn't care too much about getting things right for each and every country. Hence i am pretty sure the problem is not even limited to the German localisation.

      For the sake of transparency

      This revert

      https://github.com/odoo/odoo/commit/af3a24c010d3e7158c1324f36a1529c510d886a6

      and this original commit

      https://github.com/odoo/odoo/commit/bcaf8cb859dc2f7e975d180ba0fc49da20204557

      introduced and reverted the problematic code if i am not mistaken. I didn't review the code duely, but afais that the problematic code should only be in databases / data that have been created between

      24th of September 2024 and 25th of October 2024

      That means customers with versions of Odoo 16, 17 and 18 that either updated their code in that time frame or installed new databases should be affected. Others hopefully not!

      Best and thanks for circulating this

      Frederik

      Am 21.02.25 um 13:47 schrieb Thorsten Vocks:
      Hello,

      approx. 7 days ago we have detected a critical issue regarding the fiscal position assignation for setups with installed german localisation (l10n_de). Obviously all databases created / last updated approx. 20th October are affected.

      At first we thought version 18.0 is not affected but that was wrong.

      Here is the video with a manual fix of the fiscal positions:

      At Odoo SA we have a open bug report but no response so far:

      Issue Type: Critical Bug

      Module: Accounting / German Localization

      Odoo Versions: [16.0, 17.0]

      Also affected is [18.0]

      Impacted Environment:

      * Both
      * Not affected is 17.04., 18.0


      Summary:

      The fiscal position is being incorrectly assigned to partners in the German localization (German B2B partners with Vat-ID assigned). This leads to incorrect tax calculations and potential legal compliance issues for users relying on automated fiscal position determination.


      Steps to Reproduce:

      1. Configure the German localization module.
      2. Create a new partner with an address located in Germany.
      3. Assign a VAT ID to the partner.
      4. Create a sales order or invoice for the partner.
      5. Observe the fiscal position that gets assigned automatically (wrong).

      Expected Behavior:

      * The fiscal position should be assigned based on the VAT ID, address, and configured fiscal rules.
      * The correct tax rates and exemptions should be applied in accordance with German tax regulations.


      Observed Behavior:

      * The fiscal position is either not assigned correctly or does not reflect the expected tax rules.
      * Especially B2B partners receive an incorrect fiscal position, leading to incorrect tax calculations.
      * This can result in non-compliance with German tax regulations and incorrect tax reporting.


      Impact:

      * Financial discrepancies due to incorrect tax application.
      * Compliance risks with German tax authorities.
      * Increased manual corrections required by users.

      Suggested Fix:

      * Review and correct the fiscal position assignment logic in the German localization module.
      * Ensure that VAT IDs and partner addresses are properly considered when determining fiscal positions.
      * Implement additional validation checks to avoid incorrect fiscal position assignments.
      * I have proposed a quick fix solution in my video.

      Video:


      https://drive.google.com/file/d/1NY32FeGzALr8e-IpN9ojKlQGwe38ksAy/view


      Priority: 

      Critical

      Additional Notes:


      * This issue was observed in trainings for our customers.
      * All customers running on v16, v17, v18 in Odoo are effected (except they assign fixed fiscal positions to partners, which happens in some rare cases).
      * Affected users have reported increased manual workload due to incorrect assignments.
      * Maybe they have created wrong account moves. Due to audit_trail we cannot fix that easily.
      * We have to investigate this now on all customer databases (german companies).
      * We strongly recommend you to warn other german customers working on a v16, v17, v18 version.


      Thorsten Vocks

      openBIG.org
      Dipl. Kaufmann (FH)
      Porscheweg 4-6
      49661 Cloppenburg

      Phone: +49 4471 8409000
      Fax: +49 4471 84090009
      Mail: thorsten.vocks@openbig.org

                    

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

      -- 
Dr.-Ing. Frederik Kramer
Geschäftsführer

initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.

Tel:   +49 (0) 4181 13503 12
Fax:   +49 (0) 4181 13503 10
Mobil: +49 (0) 179 3901819

Email: frederik.kramer@initos.com
Internet: www.initos.com

Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
USt-IdNr.: DE815580155
Steuer-Nr: 15/200/53247
      by Frederik Kramer - 02:51 - 21 Feb 2025

  • Modules for oil & gas / remote catering

    Hello everyone,


    has anyone worked in the field of oil & gas or remote catering business? Are there any specific modules to support their operations? They need to track things weight ratio between frozen and thawed meet and various other things I am not that familiar with so rather than learning everything and implementing it from scratch I'd use and extend something readily available.


    Thank you. Best regards


        Radovan Skolnik

    by Radovan Skolnik - 11:30 - 20 Feb 2025
  • Odoo Experience 2025 - OCA Zone
    Hello OCA Contributors,

    We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

    I need to collate a bit of information to try and work this out with the Event Manager at Odoo.
    • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)
    • If you book a stand what size would you require (Standard, double or double premium)
    • You can see the stand costings here
    • Please respond by Friday this week (21st Feb)
    Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
    They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

    If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

    I hope you are all having a great week.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly (OCA) - 10:26 - 19 Feb 2025

    4 replies 4 replies

    • Re: Odoo Experience 2025 - OCA Zone
      Thanks for all the feedback everyone.

      I will go back to Odoo and see what the possibility is of moving stands around a bit and come back to you (though I am aware that those already booked will have chosen carefully their position).
      If you could please let me know by personal email (rebecca@odoo-community.org) which stands you have booked already that would be great).

      Hopefully we can make something work this year but if not we will have a better chance with things next year (Virginie had discussed this idea with Odoo some time back but unfortunately it was forgotten in their initial planning, so we are playing a bit of catch up. But, thanks to the continuing relationship that is happening I think we will be able to move things forward with better planning between us all over the years to come).

      I will come back to those that have commented once I have talked again with Pauline - thank you for the interest.

      Just a note though, there won't be discounts or specials unfortunately.

      I'll keep you posted.
      Rebecca

      On Sun, 23 Feb 2025 at 01:55, Ivan Sokolov via Cetmix OÜ <team@cetmix.com> wrote:
      Internal communication: Hey Rebecca, We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc [...] ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

      Hey Rebecca,

      We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc and Jay who already  paid their ones and move them to the OCA zone.


      Best regards,

      photograph
      Ivan Sokolov
       Cetmix Odoo Solutions
      cetmix.com
      Facebook Twitter LinkedIn Instagram 
      This message is sent using Mail Messages Easy app


      ----- Original message -----
      Date: Feb 19, 2025, 10:27:31 AM
      From: Rebecca Gellatly
      Subject: Odoo Experience 2025 - OCA Zone

      Hello OCA Contributors,

      We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

      I need to collate a bit of information to try and work this out with the Event Manager at Odoo.
      • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)
      • If you book a stand what size would you require (Standard, double or double premium)
      • You can see the stand costings here
      • Please respond by Friday this week (21st Feb)
      Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
      They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

      If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

      I hope you are all having a great week.
      Rebecca

      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association

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

      Powered by Messages Easy Pro



      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association
      by Rebecca Gellatly (OCA) - 08:16 - 25 Feb 2025
    • Re: Odoo Experience 2025 - OCA Zone
      Internal communication: Hey Rebecca, We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc [...] ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​ ͏ ​

      Hey Rebecca,

      We would go with a Standard booth. As long as it is not too late. Actually would be great if we could re-arrange the ones like Luc and Jay who already  paid their ones and move them to the OCA zone.


      Best regards,

      photograph
      Ivan Sokolov
       Cetmix Odoo Solutions
      cetmix.com
      Facebook Twitter LinkedIn Instagram 
      This message is sent using Mail Messages Easy app


      ----- Original message -----
      Date: Feb 19, 2025, 10:27:31 AM
      From: Rebecca Gellatly
      Subject: Odoo Experience 2025 - OCA Zone

      Hello OCA Contributors,

      We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

      I need to collate a bit of information to try and work this out with the Event Manager at Odoo.
      • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)
      • If you book a stand what size would you require (Standard, double or double premium)
      • You can see the stand costings here
      • Please respond by Friday this week (21st Feb)
      Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
      They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

      If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

      I hope you are all having a great week.
      Rebecca

      --
      Rebecca Gellatly
      General Secretary
      Odoo Community Association

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

      Powered by Messages Easy Pro

      by "Ivan Sokolov via Cetmix OÜ" <team@cetmix.com> - 01:56 - 22 Feb 2025
    • Re: Odoo Experience 2025 - OCA Zone
      True Luc. Same here.
      Rebecca, zone is a great idea.
      If the price is special or subsidised, it will look more attractive.
      Thanks 

      Regards,

      Contact: +91-9879354457 | Skype: jaynvora

             

      Technology Services @ www.serpentcs.com
      Business Solutions @ www.serpentcs.in
      Enterprise Mobile Apps @ www.odooonline.com 
      Quality Assurance @ www.odooqa.com
      Portal & DMS @ www.alfray.in


      On Sat, 22 Feb 2025 at 2:42 PM, luc.demeyer <notifications@odoo-community.org> wrote:

      I support this initiative but it’s too late for us  since we already ordered and paid our booth.

       

      Luc

       

      From: Rebecca Gellatly <rebecca@odoo-community.org>
      Sent: Wednesday, 19 February 2025 10:27
      To: Contributors <contributors@odoo-community.org>
      Subject: Odoo Experience 2025 - OCA Zone

       

      Hello OCA Contributors,

      We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

      I need to collate a bit of information to try and work this out with the Event Manager at Odoo.

      • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)

      • If you book a stand what size would you require (Standard, double or double premium)

      • You can see the stand costings here

      • Please respond by Friday this week (21st Feb)

      Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
      They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

       

      If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

       

      I hope you are all having a great week.

      Rebecca

       

      --

      Rebecca Gellatly

      General Secretary

      Odoo Community Association

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

      by Jay Vora - 11:20 - 22 Feb 2025
    • RE: Odoo Experience 2025 - OCA Zone

      I support this initiative but it’s too late for us  since we already ordered and paid our booth.

       

      Luc

       

      From: Rebecca Gellatly <rebecca@odoo-community.org>
      Sent: Wednesday, 19 February 2025 10:27
      To: Contributors <contributors@odoo-community.org>
      Subject: Odoo Experience 2025 - OCA Zone

       

      Hello OCA Contributors,

      We are in discussions with Odoo about having an OCA Zone for booths at the Odoo Experience this year.

      I need to collate a bit of information to try and work this out with the Event Manager at Odoo.

      • If you are interested in having a booth in this area could you please contact me? (rebecca@odoo-community.org)

      • If you book a stand what size would you require (Standard, double or double premium)

      • You can see the stand costings here

      • Please respond by Friday this week (21st Feb)

      Once we have agreed on the selected area with Odoo, then OCA community members will be able to book booths by sending an email to the Odoo Event Manager.
      They will generate the quotation for you, and they'll unpublish the booths from the website to make sure only community members get them.

       

      If you are keen on joining the OCA zone with a booth at the Odoo Experience, please get in touch with me.

       

      I hope you are all having a great week.

      Rebecca

       

      --

      Rebecca Gellatly

      General Secretary

      Odoo Community Association

      by Luc De Meyer. - 10:11 - 22 Feb 2025
  • New Module "Supervised Learning" - Create Machine Learning Pipelines directly in Odoo

    Hello OCA community,

     

    I’m excited to share a new module I’ve been working on: Supervised Learning for Odoo. This module provides a flexible framework for creating, training, and deploying classical machine learning pipelines directly within Odoo. It’s still in an early prototype stage (so only a small proof of concept is available at this point), but I’d love to hear your thoughts and ideas for improvement!

     

    Why Supervised Learning?

    With the current buzz around large language models (LLMs), it’s easy to overlook the benefits of more traditional supervised approaches. In many real-world business workflows, a direct supervised method can be:

     

    ·       More Accurate for Specific Tasks: Large language models are generalized and can be overkill or less precise for certain domain-specific problems.

    ·       Resource-Efficient: Training a random forest or logistic regression is typically faster and cheaper than managing an LLM.

    ·       Interpretability & Control: Classical ML pipelines often let you see feature importances and fine-tune hyperparameters in a more straightforward way, providing better transparency.

    ·       Privacy & Compliance: With local training on your own Odoo data, you avoid sending sensitive information to external APIs.

     

    What the Module Does

    ·       Integrates https://scikit-learn.org/ into Odoo

    ·       Allows you to define pipelines consisting of preprocessing, feature extraction, and estimators to make predictions using all the data in your Odoo instance

    ·       Integrates seamlessly with Odoo models, letting you train and deploy directly in your Odoo instance.

    ·       Provides a mechanism to add your own custom steps and estimators as needed.

     

    Looking for Feedback & Collaboration

    Because this is still a prototype, I’d appreciate your feedback on:

    1.       Use Cases: What real-world scenarios do you see where such a pipeline would help?

    2.       Features: Are there additional estimators or preprocessing steps you’d like to see?

    3.       Collaboration: If you have ideas or want to contribute code, let me know! I’d be thrilled to work together on making this more robust.

     

    You can find the full source code on GitHub: https://github.com/mkoeck/supervised-learning

    I would also be happy to integrate this into an existing OCA PCA, but I was unsure which one would fit best. If anyone could guide me in the right direction, that would be great!

     

    Thank you for taking the time to check this out. I’m excited to see if others are interested in shaping this into a valuable module for the Odoo ecosystem.

     

    Looking forward to your thoughts and suggestions!

     

    Best regards,

    Michael Köck

    by mkoeck - 06:36 - 16 Feb 2025

    1 replies 1 replies

    • Re: New Module "Supervised Learning" - Create Machine Learning Pipelines directly in Odoo
      Hi Michael

      I think your contribution will be very welcome in the community and will need new repo(s)...

      I suggest connector-ai where your module would be renamed into connector-scikit-learn 
      Other modules that will use that connector would go in their respective repo.

      Use cases that I can imagine :
      - find a similar record in project_task, crm_lead that has been done before and suggest a solution
      - suggest automatic entry for supplier invoices in accounting (see Alexis's amazing work here https://m.youtube.com/watch?v=edsEuXVyEYE)
      ...


      Best regards

      --------------------------------
      Cyril VINH-TUNG
      INVITU
      Computer & Network Engineering
      BP 32 - 98713 Papeete - French Polynesia
      Tél: +689 40 46 11 99
      contact@invitu.com

      Le dim. 16 févr. 2025, 07:37, Elektro-Shop Köck GmbH - Michael Köck <notifications@odoo-community.org> a écrit :

      Hello OCA community,

       

      I’m excited to share a new module I’ve been working on: Supervised Learning for Odoo. This module provides a flexible framework for creating, training, and deploying classical machine learning pipelines directly within Odoo. It’s still in an early prototype stage (so only a small proof of concept is available at this point), but I’d love to hear your thoughts and ideas for improvement!

       

      Why Supervised Learning?

      With the current buzz around large language models (LLMs), it’s easy to overlook the benefits of more traditional supervised approaches. In many real-world business workflows, a direct supervised method can be:

       

      ·       More Accurate for Specific Tasks: Large language models are generalized and can be overkill or less precise for certain domain-specific problems.

      ·       Resource-Efficient: Training a random forest or logistic regression is typically faster and cheaper than managing an LLM.

      ·       Interpretability & Control: Classical ML pipelines often let you see feature importances and fine-tune hyperparameters in a more straightforward way, providing better transparency.

      ·       Privacy & Compliance: With local training on your own Odoo data, you avoid sending sensitive information to external APIs.

       

      What the Module Does

      ·       Integrates https://scikit-learn.org/ into Odoo

      ·       Allows you to define pipelines consisting of preprocessing, feature extraction, and estimators to make predictions using all the data in your Odoo instance

      ·       Integrates seamlessly with Odoo models, letting you train and deploy directly in your Odoo instance.

      ·       Provides a mechanism to add your own custom steps and estimators as needed.

       

      Looking for Feedback & Collaboration

      Because this is still a prototype, I’d appreciate your feedback on:

      1.       Use Cases: What real-world scenarios do you see where such a pipeline would help?

      2.       Features: Are there additional estimators or preprocessing steps you’d like to see?

      3.       Collaboration: If you have ideas or want to contribute code, let me know! I’d be thrilled to work together on making this more robust.

       

      You can find the full source code on GitHub: https://github.com/mkoeck/supervised-learning

      I would also be  to integrate this into an existing OCA PCA, but I was unsure which one would fit best. If anyone could guide me in the right direction, that would be great!

       

      Thank you for taking the time to check this out. I’m excited to see if others are interested in shaping this into a valuable module for the Odoo ecosystem.

       

      Looking forward to your thoughts and suggestions!

       

      Best regards,

      Michael Köck

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

      by Cyril VINH-TUNG - 10:46 - 16 Feb 2025
  • Re: New wor ?kgroup: OCA internal tools
    Hi,

    I'll be very happy to be part of such a group. I think, currently I'm able to share around 1 or 2 hours a week which should be enough to start something and finally spend more time on it 😅.

    Regards,
    Pierre Verkest

    Le ven. 14 févr. 2025 à 09:48, Rob <notifications@odoo-community.org> a écrit :
    Dear Tom,

    I’d also be very keen to help. I have been using Odoo as a manager for five years (at a functional level) and am currently training as a developer. I would be very interested in contributing to a project that also involves the technical aspect.

    Best regards,
    Robin Angelé


    On February 14, 2025 8:07:42 AM GMT+01:00, "Mignon, Laurent" <notifications@odoo-community.org> wrote:
    Dear Tom,

    I'm also interested in joining the workgroup. I have a development background and would be happy to contribute.

    Best regards,

    Laurent



    On Thu, Feb 13, 2025 at 8:37 PM Rolando Pérez Rebollo <notifications@odoo-community.org> wrote:

    I would like to help (development background)

    \rrebollo

    On 2/13/25 12:23, Tom Blauwendraat wrote:
    Dear contributors,

    The OCA has quite a number of tools that are used internally.

    For some of them, we run into issues that need fixing but which:
    - Arent crucial enough to put out an RFQ for
    - Would not be naturally picked up by someone unless asked to do so

    To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

    So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

    Examples are:
    - Maintenance of the OCA module shop
    - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
    - Reviving our CLA bot
    - Perhaps some work on the OCA bot to assist with new ideas the Board has
    - etc

    If you are interested, please let me know and we can talk about it.

    -Tom

    _______________________________________________
    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

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

    by Pierre Verkest - 03:21 - 15 Feb 2025
  • usage bank-payment
    Hi,

    Having an invoice
    with payment mode/method "[sepa_direct_debit] SEPA Direct Debit for customers (inbound)" 

    with payment condition to pay in 3 times:
    1# mensualités de 30,00 € le 14/02/2025
    2# mensualités de 30,00 € le 15/02/2025
    3# mensualités de 40,00 € le 16/02/2025

    How may I automatically add the due amount to a mandate? Based on the above example, I would like to have a payment with amount 30,00 added on Feb 14th mandate and another 30,00 on another mandate with date Feb 15 etc.

    Maybe account_payment_order module can partially help. Any existing module could further help ?
    Thank you.





     --
    Yves Goldberg
    --

    by Yves Goldberg - 11:31 - 14 Feb 2025

    1 attachments 1 attachments

    image.png

    2 replies 2 replies

    • Re: usage bank-payment
      Hi Daniel,
      That case works fine with account_payment_order. It seems Odoo's SDD doesn't support due date while payment_order use another banking standard that does. so when adding an invoice to the order, all installments are added with their respective due date and the bank handle it from there.
      The other option I was exploring was to manage the due date locally and only add the payment that are due to the Odoo vanilla SDD, but I think it is less efficient.
      Thanks

       --
      Yves Goldberg 
      --

      ----- Original message -----
      Subject: Re: usage bank-payment
      Date: Monday, June 23, 2025 13:51

      Hello Yves,

      I implemented this for a customer in v17.
      It would be nice having it as an OCA feature.

      Here is the code used to implement it:

      from odoo import _, models
      from odoo.exceptions import UserError
      class AccountPaymentRegister(models.TransientModel):
          _inherit = "account.payment.register"
          def _create_payments(self):
              # If there are multiple lines for the same move, we only use the first one
              # Example: 50% on Jun30 and 50% on Jul15,
              # the first payment should select the first 50% amount, and not the full amount
              # NOTE: only for SDD, should be extended to other payment methods? configurable?
              sdd_method = self.env.ref("account_sepa_direct_debit.payment_method_sdd")
              if self.payment_method_line_id.payment_method_id == sdd_method:
                  original_method = self.payment_method_line_id
                  # A SDD batch should be able to include multiple due dates
                  # previous to the requested payment date
                  dt = self.payment_date
                  self.line_ids = self.line_ids.filtered(lambda x: x.date_maturity <= dt)
                  if not self.line_ids:
                      raise UserError(_("No invoice matches the SDD payment date selected."))
                  # For some reason, the payment method is reset at this point :-P
                  self.payment_method_line_id = original_method
              return super()._create_payments()


      On 14/02/2025 10:32, Yves Goldberg wrote:
      Hi,

      Having an invoice
      with payment mode/method "[sepa_direct_debit] SEPA Direct Debit for customers (inbound)" 

      with payment condition to pay in 3 times:
      1# mensualités de 30,00 € le 14/02/2025
      2# mensualités de 30,00 € le 15/02/2025
      3# mensualités de 40,00 € le 16/02/2025

      How may I automatically add the due amount to a mandate? Based on the above example, I would like to have a payment with amount 30,00 added on Feb 14th mandate and another 30,00 on another mandate with date Feb 15 etc.

      Maybe account_payment_order module can partially help. Any existing module could further help ?

      Thank you.





       --
      Yves Goldberg
      --


      --
      DANIEL REIS
      MANAGING PARTNER

      >> Schedule time on my calendar.
      M: +351 919 991 307
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]

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


      by Yves Goldberg - 09:41 - 8 Jul 2025
    • Re: usage bank-payment
      Hello Yves,

      I implemented this for a customer in v17.
      It would be nice having it as an OCA feature.

      Here is the code used to implement it:

      from odoo import _, models
      from odoo.exceptions import UserError
      class AccountPaymentRegister(models.TransientModel):
          _inherit = "account.payment.register"
          def _create_payments(self):
              # If there are multiple lines for the same move, we only use the first one
              # Example: 50% on Jun30 and 50% on Jul15,
              # the first payment should select the first 50% amount, and not the full amount
              # NOTE: only for SDD, should be extended to other payment methods? configurable?
              sdd_method = self.env.ref("account_sepa_direct_debit.payment_method_sdd")
              if self.payment_method_line_id.payment_method_id == sdd_method:
                  original_method = self.payment_method_line_id
                  # A SDD batch should be able to include multiple due dates
                  # previous to the requested payment date
                  dt = self.payment_date
                  self.line_ids = self.line_ids.filtered(lambda x: x.date_maturity <= dt)
                  if not self.line_ids:
                      raise UserError(_("No invoice matches the SDD payment date selected."))
                  # For some reason, the payment method is reset at this point :-P
                  self.payment_method_line_id = original_method
              return super()._create_payments()


      On 14/02/2025 10:32, Yves Goldberg wrote:
      Hi,

      Having an invoice
      with payment mode/method "[sepa_direct_debit] SEPA Direct Debit for customers (inbound)" 

      with payment condition to pay in 3 times:
      1# mensualités de 30,00 € le 14/02/2025
      2# mensualités de 30,00 € le 15/02/2025
      3# mensualités de 40,00 € le 16/02/2025

      How may I automatically add the due amount to a mandate? Based on the above example, I would like to have a payment with amount 30,00 added on Feb 14th mandate and another 30,00 on another mandate with date Feb 15 etc.

      Maybe account_payment_order module can partially help. Any existing module could further help ?
      Thank you.





       --
      Yves Goldberg
      --


      --
      DANIEL REIS
      MANAGING PARTNER

      >> Schedule time on my calendar.
      M: +351 919 991 307
      E: dreis@OpenSourceIntegrators.com
      A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

      [Logo OpenSourceIntegrators.com]

      by Daniel Reis - 12:50 - 23 Jun 2025
  • New workgroup: OCA internal tools
    Dear contributors,

    The OCA has quite a number of tools that are used internally.

    For some of them, we run into issues that need fixing but which:
    - Arent crucial enough to put out an RFQ for
    - Would not be naturally picked up by someone unless asked to do so

    To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

    So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

    Examples are:
    - Maintenance of the OCA module shop
    - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
    - Reviving our CLA bot
    - Perhaps some work on the OCA bot to assist with new ideas the Board has
    - etc

    If you are interested, please let me know and we can talk about it.

    -Tom
    by Tom Blauwendraat - 06:21 - 13 Feb 2025

    5 replies 5 replies

    • Re: New workgroup: OCA internal tools
      Hi Tom,

      Just to double check that you received my message and could find me in the OCA database ;)

      Best,
      Robin


      On February 14, 2025 9:46:38 AM GMT+01:00, Rob <rob.a@posteo.net> wrote:
      Dear Tom,

      I’d also be very keen to help. I have been using Odoo as a manager for five years (at a functional level) and am currently training as a developer. I would be very interested in contributing to a project that also involves the technical aspect.

      Best regards,
      Robin Angelé


      On February 14, 2025 8:07:42 AM GMT+01:00, "Mignon, Laurent" <notifications@odoo-community.org> wrote:
      Dear Tom,

      I'm also interested in joining the workgroup. I have a development background and would be happy to contribute.

      Best regards,

      Laurent



      On Thu, Feb 13, 2025 at 8:37 PM Rolando Pérez Rebollo <notifications@odoo-community.org> wrote:

      I would like to help (development background)

      \rrebollo

      On 2/13/25 12:23, Tom Blauwendraat wrote:
      Dear contributors,

      The OCA has quite a number of tools that are used internally.

      For some of them, we run into issues that need fixing but which:
      - Arent crucial enough to put out an RFQ for
      - Would not be naturally picked up by someone unless asked to do so

      To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

      So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

      Examples are:
      - Maintenance of the OCA module shop
      - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
      - Reviving our CLA bot
      - Perhaps some work on the OCA bot to assist with new ideas the Board has
      - etc

      If you are interested, please let me know and we can talk about it.

      -Tom

      _______________________________________________
      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

      by Robin Angelé - 03:31 - 22 Feb 2025
    • Re: New workgroup: OCA internal tools

      Hi Rolando, Laurent & Rob,

      Loving the enthusiasm!

      could you also send me a mail at tblauwendraat@therp.nl so that I have your email address?

      I don't see quickly how I can deduce that from what was sent to the mailing list, and then I can contact you next week with the next steps.

      -Tom


      On 2/13/25 20:37, Rolando Pérez Rebollo wrote:

      I would like to help (development background)

      \rrebollo

      On 2/13/25 12:23, Tom Blauwendraat wrote:
      Dear contributors,

      The OCA has quite a number of tools that are used internally.

      For some of them, we run into issues that need fixing but which:
      - Arent crucial enough to put out an RFQ for
      - Would not be naturally picked up by someone unless asked to do so

      To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

      So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

      Examples are:
      - Maintenance of the OCA module shop
      - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
      - Reviving our CLA bot
      - Perhaps some work on the OCA bot to assist with new ideas the Board has
      - etc

      If you are interested, please let me know and we can talk about it.

      -Tom

      _______________________________________________
      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 Tom Blauwendraat - 09:56 - 14 Feb 2025
    • Re: New workgroup: OCA internal tools
      Dear Tom,

      I’d also be very keen to help. I have been using Odoo as a manager for five years (at a functional level) and am currently training as a developer. I would be very interested in contributing to a project that also involves the technical aspect.

      Best regards,
      Robin Angelé


      On February 14, 2025 8:07:42 AM GMT+01:00, "Mignon, Laurent" <notifications@odoo-community.org> wrote:
      Dear Tom,

      I'm also interested in joining the workgroup. I have a development background and would be happy to contribute.

      Best regards,

      Laurent



      On Thu, Feb 13, 2025 at 8:37 PM Rolando Pérez Rebollo <notifications@odoo-community.org> wrote:

      I would like to help (development background)

      \rrebollo

      On 2/13/25 12:23, Tom Blauwendraat wrote:
      Dear contributors,

      The OCA has quite a number of tools that are used internally.

      For some of them, we run into issues that need fixing but which:
      - Arent crucial enough to put out an RFQ for
      - Would not be naturally picked up by someone unless asked to do so

      To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

      So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

      Examples are:
      - Maintenance of the OCA module shop
      - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
      - Reviving our CLA bot
      - Perhaps some work on the OCA bot to assist with new ideas the Board has
      - etc

      If you are interested, please let me know and we can talk about it.

      -Tom

      _______________________________________________
      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

      by rob.a - 09:46 - 14 Feb 2025
    • Re: New workgroup: OCA internal tools
      Dear Tom,

      I'm also interested in joining the workgroup. I have a development background and would be happy to contribute.

      Best regards,

      Laurent



      On Thu, Feb 13, 2025 at 8:37 PM Rolando Pérez Rebollo <notifications@odoo-community.org> wrote:

      I would like to help (development background)

      \rrebollo

      On 2/13/25 12:23, Tom Blauwendraat wrote:
      Dear contributors,

      The OCA has quite a number of tools that are used internally.

      For some of them, we run into issues that need fixing but which:
      - Arent crucial enough to put out an RFQ for
      - Would not be naturally picked up by someone unless asked to do so

      To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

      So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

      Examples are:
      - Maintenance of the OCA module shop
      - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
      - Reviving our CLA bot
      - Perhaps some work on the OCA bot to assist with new ideas the Board has
      - etc

      If you are interested, please let me know and we can talk about it.

      -Tom

      _______________________________________________
      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



      --
      Laurent Mignon
      Technical lead / Management Team
      T: +32 2 8883148


      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg

      by Laurent Mignon - 08:05 - 14 Feb 2025
    • Re: New workgroup: OCA internal tools

      I would like to help (development background)

      \rrebollo

      On 2/13/25 12:23, Tom Blauwendraat wrote:
      Dear contributors,

      The OCA has quite a number of tools that are used internally.

      For some of them, we run into issues that need fixing but which:
      - Arent crucial enough to put out an RFQ for
      - Would not be naturally picked up by someone unless asked to do so

      To solve these kind of issues we would like to bring a new workgroup into life, that tracks these issues by priority and distributes them among those willing to help out.

      So the question: are you, or do you have a colleague who would be willing to join such a workgroup either on the functional or on the development level? And participate either in specifying, solving or testing.

      Examples are:
      - Maintenance of the OCA module shop
      - Some non optimal workflows in the OCA odoo instance, regarding memberships, invoicing and the like, causing issues for Rebecca
      - Reviving our CLA bot
      - Perhaps some work on the OCA bot to assist with new ideas the Board has
      - etc

      If you are interested, please let me know and we can talk about it.

      -Tom

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

      by Ing. Rolando Pérez Rebollo - 08:35 - 13 Feb 2025