Archives
Contributors
-
Re: Removal of migration scripts on each new version
+1 to keep them
--Maxime ChambreuilDesde mi móvil
From: Stefan Rijnhart <notifications@odoo-community.org>
Sent: Tuesday, May 6, 2025 5:02:06 AM
To: Contributors <contributors@odoo-community.org>
Subject: Removal of migration scripts on each new versionHi,
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, removemigrationsfolder inside the module if exists).
(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
-- 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 Maxime Chambreuil - 02:36 - 6 May 2025 -
Re: Removal of migration scripts on each new version
On 06-05-2025 14:17, Juan José Scarafía wrote: > I agree, keeping the migration scripts probably doesn't mean you can > just skip versions and expect them to run flawlessly, but in a lot of > cases, it does seem to work out just fine. Well, they should run flawlessly otherwise it will break everyone's migration. The scripts that we keep should be idempotent and not be invalidated by subsequent data model changes. So special care should be taken when reviewing PRs that contain older scripts. > On the other hand, I'm not really seeing any downside to leaving them > there. If you *are* updating version by version, those older scripts > just won't run anyway, right? That is correct, if you migrate from 17 to 18, any 16.0.x.x.x migration script will not be triggered. -- 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
by Stefan Rijnhart - 02:25 - 6 May 2025 -
Re: Removal of migration scripts on each new version
I agree, keeping the migration scripts probably doesn't mean you can just skip versions and expect them to run flawlessly, but in a lot of cases, it does seem to work out just fine.On the other hand, I'm not really seeing any downside to leaving them there. If you *are* updating version by version, those older scripts just won't run anyway, right?Without diving into a super deep analysis or discussion, my feeling is that it's better to keep the scripts.Best,Juan JoséEl mar, 6 may 2025 a la(s) 8:52 a.m., Luc De Meyer (notifications@odoo-community.org) escribió:>>> Can I have a temperature check from the community to see how you all feel about this?
I prefer that we keep migration scripts since we tend to use Odoo Enterprise migration for those customers who licensed Enterprise and most of our customers are skipping releases.
Regards,Luc
From: Stefan Rijnhart <notifications@odoo-community.org>
Sent: Tuesday, May 6, 2025 1:02 PM
To: Contributors <contributors@odoo-community.org>
Subject: Removal of migration scripts on each new versionHi,
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, removemigrationsfolder inside the module if exists).
(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
-- 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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Juan José Scarafía - 02:16 - 6 May 2025 -
Re: Removal of migration scripts on each new version
>>> Can I have a temperature check from the community to see how you all feel about this?
I prefer that we keep migration scripts since we tend to use Odoo Enterprise migration for those customers who licensed Enterprise and most of our customers are skipping releases.
Regards,Luc
From: Stefan Rijnhart <notifications@odoo-community.org>
Sent: Tuesday, May 6, 2025 1:02 PM
To: Contributors <contributors@odoo-community.org>
Subject: Removal of migration scripts on each new versionHi,
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, removemigrationsfolder inside the module if exists).
(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
-- 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 Luc De Meyer. - 01:51 - 6 May 2025 -
Re: SAAS solution
I'm not going to promote anything here, but you can have a look at this: https://www.youtube.com/watch?v=TNVrOxVeHgM
Best regards,
Ivan Sokolov
Cetmix Odoo Solutionscetmix.com 
This message is sent using Mail Messages Easy app ----- Original message -----
Date: May 6, 2025, 4:53:15 AM
From: Notifications
Subject: SAAS solutionDear Sir/Madam,
I hope this email finds you well.
We are seeking a solution for deploying Odoo as a SaaS offering. While Webkul's solution appears promising, we are exploring community-based alternatives. Could you advise on the optimal approach and best practices for deploying a community Odoo solution as a SaaS?
Thank you.
Sincerely,
Abdulbasit Suleiman_______________________________________________
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:00 - 6 May 2025 -
Removal of migration scripts on each new version
Hi,
the migration guide mandates the following
> Remove any possible migration script from previous version (in a nutshell, removemigrationsfolder inside the module if exists).
(https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-18.0#tasks-to-do-in-the-migration)
However, it is not uncommon to skip versions when migrating an Odoo instance. You would go from 15.0 or 16.0 to 18.0 rather than migrating every year. When using the Odoo enterprise migration, the migration scripts between the source and the target version are supposed to be present in the target version. So the migration guideline breaks this type of migration.
I had a disagreement with Pedro Baeza about this on one PR, but I keep coming across instances of this such as https://github.com/OCA/account-invoicing/pull/1874 today so I would like to discuss this in a wider audience.
My preference would be for the guideline to change to say that it is allowed to keep some of the scripts if they are safe for inclusion in the later version (such as the script from https://github.com/OCA/account-invoicing/pull/1874, which checks if a field already exists before trying to add it).
Can I have a temperature check from the community to see how you all feel about this?
Best regards,
Stefan
-- 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
by Stefan Rijnhart - 01:00 - 6 May 2025 -
Re: Analytic info on inventory adjustments (Odoo 17)
🙂
Thanks!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
De: Roussel, Denis <notifications@odoo-community.org>
Enviado: lunes, 5 de mayo de 2025 13:37
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Analytic info on inventory adjustments (Odoo 17)
Le lun. 5 mai 2025, 20:57, Maxime Chambreuil <notifications@odoo-community.org> a écrit :
Hello,
Do we have a module on Odoo 17 to set the analytic information when doing an inventory adjustment?
I found something on previous versions and inventory line and I was wondering if it was migrated somewhere in a different repo.
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.com
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Maxime Chambreuil - 10:31 - 5 May 2025 -
Re: Analytic info on inventory adjustments (Odoo 17)
Le lun. 5 mai 2025, 20:57, Maxime Chambreuil <notifications@odoo-community.org> a écrit :Hello,
Do we have a module on Odoo 17 to set the analytic information when doing an inventory adjustment?
I found something on previous versions and inventory line and I was wondering if it was migrated somewhere in a different repo.
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.com
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel - 09:33 - 5 May 2025 -
Analytic info on inventory adjustments (Odoo 17)
Hello,
Do we have a module on Odoo 17 to set the analytic information when doing an inventory adjustment?
I found something on previous versions and inventory line and I was wondering if it was migrated somewhere in a different repo.
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
by Maxime Chambreuil - 08:56 - 5 May 2025 -
Re: Large Data Files
Hello everyone,
Thanks to your valuable feedback and suggestions, I’ve developed a dedicated ETL module for Odoo designed to handle large-scale data synchronization efficiently.
The solution bypasses ORM bottlenecks using optimized SQL and batch processing, and integrates Polars and SQLAlchemy for fast data transformation.
It supports millions of records and is ideal for daily sync with legacy systems (from SQLITE for now).
The module is available here: https://github.com/cyberwave-odoo/odoo-etl
I truly appreciate the community insights that shaped this project — thank you!
Best regards,
Jérôme
On Wed, Aug 21, 2024 at 9:17 AM David Beal <notifications@odoo-community.org> wrote:Nice to see pandas run fast.For those for those that want run very very ... very fast consider to use polarsLe mer. 21 août 2024 à 01:57, Graeme Gellatly <notifications@odoo-community.org> a écrit :Queue job and batching can work. It is commonplace. But if it is CPU/Memory then honestly, after optimising what you can within the framework (e.g. as per Holger) a lot of the time you just get away with running a seperate worker on a separate port for long running jobs and set the limits/timeouts high. That is how a lot of people deploy cron workers these days and in older Odoo we used to have to do it to run financial reports and seemingly again now. 30,000 simple records is not so much.There may also be some db tuning you can do around WAL files, checkpoints etc if they get in the way.On Wed, Aug 21, 2024 at 9:57 AM Jerôme Dewandre <notifications@odoo-community.org> wrote:Hello,Thank you very much for your quick responses :)
Tom Blauwendraat: I am running on v16Holger Brunn: adapting the script with .with_context(tracking_disable=True) to Disable email notification divides the running time by at least 4
Goran Sunjka: It is indeed an interesting idea, I was wondering if I could store a hash of the row in Postgres to check if an existing record was updated to separate "create" and "update" action
Daniel Reis: This is indeed the problem I encountered.
Thank you all for your replies, it helps a lot :)JérômeOn Tue, Aug 20, 2024 at 7:47 PM Daniel Reis <notifications@odoo-community.org> wrote:I would expect this code to just abort for a non trivial quantity of records.
The reason why is that this is a single worker doing a single database transaction.
So the worker process will probably hit the time and CPU limits and be killed, and no records would be saved because of a transaction rollback.
And if you increase those limits a lot, you will probably cause long table locks on the database, and hurt other users and processes.
Going direct to the database can work if the data is pretty simple.
It can work but it can also be a can of worms.
One approach is to have an incremental approach to the data loading.
In the past I have used external ETL tools or scripts to do this.
Keeping it inside Odoo, one of the tools that can help is the Job Queue, possibly along with something like base_import_async:
https://github.com/OCA/queue/tree/16.0/base_import_async
Thanks
--
DANIEL REIS
MANAGING PARTNERMeet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais![[Logo OpenSourceIntegrators.com]](https://www.opensourceintegrators.com/images/opensource-logo-2022.svg)
On 20/08/2024 16:32, Jerôme Dewandre wrote:
Hello,
I am currently working on a syncro with a legacy system (adesoft) containing a large amount of data that must be synchronized on a daily basis (such as meetings).
It seems everything starts getting slow when I import 30.000 records with the conventional "create()" method.
I suppose the ORM might be an issue here. Potential workaround:
1. Bypass the ORM to create a record with self.env.cr.execute (but if I want to delete them I will also need a custom query)2. Bypass the ORM with stored procedures (https://www.postgresql.org/docs/current/sql-createprocedure.html)3. Increase the CPU/RAM/Worker nodes4. Some better ideas?
What would be the best way to go?
A piece of my current test (df is a pandas dataframe containing the new events):
@api.modeldef create_events_from_df(self, df):Event = self.env['event.event']events_data = []for _, row in df.iterrows():event_data = {'location': row['location'],'name': row['name'],'date_begin': row['date_begin'],'date_end': row['date_end'],}events_data.append(event_data)# Create all events in a single batchEvent.create(events_data)
Thanks in advance if you read this, and thanks again if you replied :)
Jérôme_______________________________________________
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Jerôme Dewandre" <jerome.dewandre.mail@gmail.com> - 11:56 - 2 May 2025 -
Re: Odoo Module Dependency Visualisation
Actually there is a non OCA but open source module that does the same thing.
https://apps.odoo.com/apps/modules/18.0/cx_odoo_plantuml
Best regards,
Ivan Sokolov
Cetmix Odoo Solutionscetmix.com This message is sent using Mail Messages Easy app ----- Original message -----
Date: May 1, 2025, 10:12:53 AM
From: Notifications
Subject: Re: Odoo Module Dependency VisualisationHelloGreat tool !It could be supercool if you colorize depending on the licence... it could show if licence inheritance is correct for a project...for instance OPL-1 should not inherit AGPL-3...Bravo--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe ven. 25 avr. 2025, 04:33, Janik von Rotz <notifications@odoo-community.org> a écrit :_______________________________________________
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 - 1 May 2025 -
Re: Odoo Module Dependency Visualisation
HelloGreat tool !It could be supercool if you colorize depending on the licence... it could show if licence inheritance is correct for a project...for instance OPL-1 should not inherit AGPL-3...Bravo--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe ven. 25 avr. 2025, 04:33, Janik von Rotz <notifications@odoo-community.org> a écrit :Hi everybody,
I wanted to visualize the dependencies of Odoo modules in a folder and build a script that produces a vis.js powered html: https://github.com/Mint-System/Odoo-Build/blob/main/bin/odoo-module-dependencies
Here is the Odoo 16.0 planet 🙂
Now I am thinking about adding more features such as search and coloring the type of modules.
However, I would like to know if somebody in the OCA community already did something similar.
Would be nice to hear from you :)
Cheers, Janik
-- Suggest a meeting: https://apmt.day/janikvonrotz/999120f2/ We are hiring: https://www.mint-system.ch/jobs CTO Mint System GmbH Tel: +41 44 244 7222
_______________________________________________
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:11 - 1 May 2025 -
New typesense and odoo connector
Typesense is a search engine and using new module we can index whatever data we want friendly without needing for coding special serializing functions for each form of data we want to send.happy for review
Typesense is a powerful easy to configure search engine.
by Mohamed Alkobrosly - 03:45 - 1 May 2025 -
Partnership with Flatio
Partnership with Flatio
Hello!
are you open to content collaboration? I’m reaching out from Flatio, a platform offering mid-term housing solutions.
I’d love to explore publishing an article or adding links to existing content.
In return, you can place your link to some of our articles in our blog or send us your own.
Looking forward to hearing your thoughts!
Have a lovely day,
Jitka Pálešová
Marketing & Partnership
Unlock your freedom with Flatio
+420 734 204 972
Copyright © 2025 Flatio, s.r.o., All rights reserved.
Want to change how you receive these emails?
You can unsubscribe.
by "Flatio" <partners@flatio.com> - 03:51 - 29 Apr 2025 -
Re: Sale workflow repository v16
Thanks Daniel
Il 29/04/2025 09:31, Daniel Reis ha scritto:
A segunda, 28/04/2025, 23:22, Pedro M. Baeza <notifications@odoo-community.org> escreveu:
Thanks for doing this work._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Security Notice: Don't be too quick to click!
Think carefully before clicking on links or attachments. Never provide your User ID or Passwords. Report any suspicious emails to your system administrator._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Antonio M. Vigliotti - 11:05 - 29 Apr 2025 -
Re: Sale workflow repository v16
Many thanks Denis!Sergio CoratoIl giorno mar 29 apr 2025 alle ore 10:28 Alex Comba <notifications@odoo-community.org> ha scritto:Thanks a lot!On Mon, Apr 28, 2025 at 5:57 PM Roussel, Denis <notifications@odoo-community.org> wrote:Dear contributors,For weeks, the v16 builds on sale-workflow repository have been broken due to the incompatibility with current sale_triple_discount module implementation and the depending version of account_invoice_triple_discount (refactoring has been done there and not yet on sale side).I've fixed the builds pinning the account_invoice_triple_discount dependency before refactor.You can now rebase your pending PR's and let's go forward.Thanks for your patience._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sergio Corato - 10:31 - 29 Apr 2025 -
Re: Sale workflow repository v16
Thanks a lot!On Mon, Apr 28, 2025 at 5:57 PM Roussel, Denis <notifications@odoo-community.org> wrote:Dear contributors,For weeks, the v16 builds on sale-workflow repository have been broken due to the incompatibility with current sale_triple_discount module implementation and the depending version of account_invoice_triple_discount (refactoring has been done there and not yet on sale side).I've fixed the builds pinning the account_invoice_triple_discount dependency before refactor.You can now rebase your pending PR's and let's go forward.Thanks for your patience._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 10:20 - 29 Apr 2025 -
Re: Sale workflow repository v16
A segunda, 28/04/2025, 23:22, Pedro M. Baeza <notifications@odoo-community.org> escreveu:Thanks for doing this work._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Security Notice: Don't be too quick to click!
Think carefully before clicking on links or attachments. Never provide your User ID or Passwords. Report any suspicious emails to your system administrator.
by Daniel Reis - 09:30 - 29 Apr 2025 -
Re: Sale workflow repository v16
Thanks for doing this work.
by Pedro M. Baeza - 12:21 - 29 Apr 2025
