Skip to Content

Contributors

  • 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
  • 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
  • Re: Survey XLSX module cannot be found on OCA shop page.
    Hello Virginie,

    Thank you for looking into this. I appreciate all the great work OCA!

    2025年2月17日(月) 20:52 Virginie Dewulf <virginie@odoo-community.org>:
    Hello Kanda,

    This is a perfect first task for our new "OCA internal tools" working group!

    Tom, another task on your plate :)

    Thanks!
    Virginie Dewulf
    Executive Director
    +32 477 64 17 20


    Le jeu. 6 févr. 2025 à 11:58, Tatsuki Kanda <notifications@odoo-community.org> a écrit :
    Here is a brief report:

    When trying to open the Survey XLSX module on the OCA shop page, the following error occurs:
    "403: Forbidden
    The page you were looking for could not be authorized.
    Error message:
    Due to security restrictions, you are not allowed to access 'Product Template' (product.template) records.
    Contact your administrator to request access if necessary."

    However, the module can be viewed on the Odoo app store:
    https://apps.odoo.com/apps/modules/16.0/survey_xlsx

    It is also available on GitHub:
    https://github.com/OCA/survey

    Is there any specific reason why it is not displayed on the OCA shop page?


    --

    -- 

    神田樹 Tatsuki Kanda
    コタエル株式会社 / Quartile
    Phone: +81-92-707-3087
    kanda@quartile.co
    https://www.quartile.co

    _______________________________________________
    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



    --

    -- 

    神田樹 Tatsuki Kanda
    コタエル株式会社 / Quartile
    Phone: +81-92-707-3087
    kanda@quartile.co
    https://www.quartile.co


    by Tatsuki Kanda - 02:36 - 18 Feb 2025
  • Re: Survey XLSX module cannot be found on OCA shop page.
    Hello Kanda,

    This is a perfect first task for our new "OCA internal tools" working group!

    Tom, another task on your plate :)

    Thanks!
    Virginie Dewulf
    Executive Director
    +32 477 64 17 20


    Le jeu. 6 févr. 2025 à 11:58, Tatsuki Kanda <notifications@odoo-community.org> a écrit :
    Here is a brief report:

    When trying to open the Survey XLSX module on the OCA shop page, the following error occurs:
    "403: Forbidden
    The page you were looking for could not be authorized.
    Error message:
    Due to security restrictions, you are not allowed to access 'Product Template' (product.template) records.
    Contact your administrator to request access if necessary."

    However, the module can be viewed on the Odoo app store:
    https://apps.odoo.com/apps/modules/16.0/survey_xlsx

    It is also available on GitHub:
    https://github.com/OCA/survey

    Is there any specific reason why it is not displayed on the OCA shop page?


    --

    -- 

    神田樹 Tatsuki Kanda
    コタエル株式会社 / Quartile
    Phone: +81-92-707-3087
    kanda@quartile.co
    https://www.quartile.co

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


    by Virginie Dewulf - 12:50 - 17 Feb 2025
  • 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
  • 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
  • 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
  • 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
  • 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
  • Re: Increased Queue Job Failures – Need Advice
    I am a big fan of

    except SerializationFailure as e:
        _logger.exception(e)
        raise RetryableJobError(e)

    Beware side effects (third party service calls, file system operations)!

    On Thu, Feb 13, 2025 at 7:03 AM Jacques-Etienne Baudoux <notifications@odoo-community.org> wrote:
    Indeed, configure a smaller amount of workers for that specific channel. I think the max retry was not respected in the past, so that failing jobs were always restarted in case of SerializationFailure.

    Le jeu. 13 févr. 2025 à 11:47, Graeme Gellatly <notifications@odoo-community.org> a écrit :
    It is a serialization failure. There isn't much (sensible) you can do but use a smaller queue (say 1 channel) for those jobs. If the row is locked or the table is locked, it is locked. If it really matters, and it must be parallel well you need to really dig into the methods, work out when locks are taken, when they are released and optimise the sh!t out of that portion that code. If you can't then you start to get in queuing rights, dropping ACID commitments within transaction etc.

    On Thu, Feb 13, 2025 at 11:02 PM Emanuel Cino <notifications@odoo-community.org> wrote:
    Hello everyone,

    We use queue jobs in our Odoo 14 instance for various operations, and they have worked well so far. However, we've recently noticed an increasing number of failures with the following errors:

    1. psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block
    2. psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update

    This issue may have started after updating the queue_job module to the latest version in branch 14.0, though we're not certain. No other changes have been made to our server configuration.

    Since we’re unsure how to resolve this, does anyone have experience with this module and the best server configuration for handling parallel job execution? The errors typically occur when multiple jobs run in parallel or when users work on the same models as the running jobs.

    Any insights or recommendations would be greatly appreciated!

    Thanks,

    Emanuel

    _______________________________________________
    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 Adam Heinz - 02:41 - 13 Feb 2025
  • Re: Increased Queue Job Failures – Need Advice
    Indeed, configure a smaller amount of workers for that specific channel. I think the max retry was not respected in the past, so that failing jobs were always restarted in case of SerializationFailure.

    Le jeu. 13 févr. 2025 à 11:47, Graeme Gellatly <notifications@odoo-community.org> a écrit :
    It is a serialization failure. There isn't much (sensible) you can do but use a smaller queue (say 1 channel) for those jobs. If the row is locked or the table is locked, it is locked. If it really matters, and it must be parallel well you need to really dig into the methods, work out when locks are taken, when they are released and optimise the sh!t out of that portion that code. If you can't then you start to get in queuing rights, dropping ACID commitments within transaction etc.

    On Thu, Feb 13, 2025 at 11:02 PM Emanuel Cino <notifications@odoo-community.org> wrote:
    Hello everyone,

    We use queue jobs in our Odoo 14 instance for various operations, and they have worked well so far. However, we've recently noticed an increasing number of failures with the following errors:

    1. psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block
    2. psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update

    This issue may have started after updating the queue_job module to the latest version in branch 14.0, though we're not certain. No other changes have been made to our server configuration.

    Since we’re unsure how to resolve this, does anyone have experience with this module and the best server configuration for handling parallel job execution? The errors typically occur when multiple jobs run in parallel or when users work on the same models as the running jobs.

    Any insights or recommendations would be greatly appreciated!

    Thanks,

    Emanuel

    _______________________________________________
    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 Jacques-Etienne Baudoux - 02:01 - 13 Feb 2025
  • Re: Increased Queue Job Failures – Need Advice
    It is a serialization failure. There isn't much (sensible) you can do but use a smaller queue (say 1 channel) for those jobs. If the row is locked or the table is locked, it is locked. If it really matters, and it must be parallel well you need to really dig into the methods, work out when locks are taken, when they are released and optimise the sh!t out of that portion that code. If you can't then you start to get in queuing rights, dropping ACID commitments within transaction etc.

    On Thu, Feb 13, 2025 at 11:02 PM Emanuel Cino <notifications@odoo-community.org> wrote:
    Hello everyone,

    We use queue jobs in our Odoo 14 instance for various operations, and they have worked well so far. However, we've recently noticed an increasing number of failures with the following errors:

    1. psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block
    2. psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update

    This issue may have started after updating the queue_job module to the latest version in branch 14.0, though we're not certain. No other changes have been made to our server configuration.

    Since we’re unsure how to resolve this, does anyone have experience with this module and the best server configuration for handling parallel job execution? The errors typically occur when multiple jobs run in parallel or when users work on the same models as the running jobs.

    Any insights or recommendations would be greatly appreciated!

    Thanks,

    Emanuel

    _______________________________________________
    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 - 11:46 - 13 Feb 2025
  • Increased Queue Job Failures – Need Advice
    Hello everyone,

    We use queue jobs in our Odoo 14 instance for various operations, and they have worked well so far. However, we've recently noticed an increasing number of failures with the following errors:

    1. psycopg2.errors.InFailedSqlTransaction: current transaction is aborted, commands ignored until end of transaction block
    2. psycopg2.errors.SerializationFailure: could not serialize access due to concurrent update

    This issue may have started after updating the queue_job module to the latest version in branch 14.0, though we're not certain. No other changes have been made to our server configuration.

    Since we’re unsure how to resolve this, does anyone have experience with this module and the best server configuration for handling parallel job execution? The errors typically occur when multiple jobs run in parallel or when users work on the same models as the running jobs.

    Any insights or recommendations would be greatly appreciated!

    Thanks,

    Emanuel

    by "Emanuel Cino" <emanuel@compassion.ch> - 11:01 - 13 Feb 2025
  • odoo para manufactura
    lo comparto para que otros lo puedan aprovechar, se pueda mejorar y darle continuidad.                 https://github.com/zurbaran/odoo_metal_manufacturing


    by "Antonio Jose Caballero Alcaraz" <zurbaran79@hotmail.com> - 07:16 - 12 Feb 2025
  • Re: Experience with Odoo Project module for Agile/Scrum
    Hi Anders,
    Any recommendation on the module is welcomed, if you find anything that can improve it, we can add it on the next upgrade.
    We hope to start with this in the near future.
    Thank you

    On Tue, Feb 11, 2025 at 1:57 PM Anders Wallenquist <notifications@odoo-community.org> wrote:

    I have been using the module project_scrum that is template for the module project agile for several years now.

    I think its working well, it have some ruff edges. There are always customers that have their own definition av Scrum but in most cases it works for both small to large projects.


    /Anders

    Den 2025-02-11 kl. 11:52, skrev Stephane Eicher:

    Dear OCA Community,

    I hope you're all doing well.

    I’m currently exploring the use of the Odoo Project module for managing projects with an Agile/Scrum methodology. Before diving deeper, I wanted to check if anyone in the community has experience using this module for Scrum-based project management.

    If you have implemented Scrum workflows with Odoo Project, I would love to hear about your experiences, best practices, and any challenges you faced. Additionally, if there are any community modules that enhance Scrum functionalities within Odoo, I would greatly appreciate any recommendations.

    Thanks in advance for your insights!

    Best regards,

    --
    Eicher Stéphane
    Co-fondateur / Ingénieur logiciel
    +41 32 552 27 77
    info@jumpto.ch


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

    -- 
    Med vänlig hälsning / Best regards / 顺祝商祺 ,
    Anders Wallenquist
    
    <b>VERTEL AB</b>| Anders Wallenquist | anders.wallenquist@vertel.se
    +46 (0)13 99 19 480 | +46 (0) 709 565 160 | vertel.se

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



    --
    Binhex Logo
    Jorge Elena Poblet
    Founder & CEO
    Binhex
    j.elena@binhex.cloud
    Office (Spain) : +34 622 40 08 08
    Office (USA): +1 561 403 4406
    Offices:
    Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
    Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
    Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
    Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
    LinkedIn Twitter Facebook YouTube
    Start for free: Try Odoo Community in the cloud

    This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
    Privacy Policy


    by Jorge Elena Poblet - 04:26 - 11 Feb 2025