Archives
Contributors
-
Multiple customers on Purchase Orders
Hello,
I am dealing with a scenario where 2 sister companies share parts of their operations and make purchase orders together with split ratio between them. The way they do it is 3-party agreements, where there are 2 customers and 1 supplier and for purchase orders there are instructions for suppliers on how to split the invoicing (i.e. the supplier sends 2 separate invoices - each to individual company according to the split ratio).
Anyone faced anything similar? I am thinking of using 2 companies to model it and tinkering with visibility in each according to split. Because where there is a split, they want to see the document in both. Where there is not (it belongs to single company), should ony be visible there. However how to model in a best way that there should be 2 customers (maybe more for future extensions) on each document?
Any advice is highly welcome. Thank you very much.
Best regards
Radovan Skolnik
by Radovan Skolnik - 12:06 - 23 Sep 2024-
Re: Multiple customers on Purchase Orders
Thanks Holger,
the idea of "consortium" instead of trying to put multiple customers into PO is a good one and also naturally extendable beyond more than 2 companies.
Best regards
Radovan
On pondelok 23. septembra 2024 12:37:45 CEST Holger Brunn wrote:
> > Anyone faced anything similar? I am thinking of using 2 companies to model
> > it and tinkering with visibility in each according to split. Because where
> > there is a split, they want to see the document in both. Where there is
> > not
> > (it belongs to single company), should ony be visible there. However how
> > to
> > model in a best way that there should be 2 customers (maybe more for
> > future
> > extensions) on each document?
>
> I have a customer with a similar requirement the other way around, where
> multiple suppliers invoice the same customer:
> https://github.com/tosccolors/vertical-professional-services/tree/16.0/
> ps_partner_multi_relation
> They solved this by defining a partner relation "consortium", and every time
> an invoice for a consortium partner is posted, this invoice is split by the
> weights ("distribution key") on the consortium relation and new invoices
> are created for the involved partners.
> This concept should extend quite naturally to the purchase side, where you
> split the supplier invoices and deliveries according to the distribution key
> on the partner relation.
> --
> Your partner for the hard Odoo problems
> https://hunki-enterprises.com
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 02:46 - 23 Sep 2024 -
Re: Multiple customers on Purchase Orders
> Anyone faced anything similar? I am thinking of using 2 companies to model > it and tinkering with visibility in each according to split. Because where > there is a split, they want to see the document in both. Where there is not > (it belongs to single company), should ony be visible there. However how to > model in a best way that there should be 2 customers (maybe more for future > extensions) on each document? I have a customer with a similar requirement the other way around, where multiple suppliers invoice the same customer: https://github.com/tosccolors/vertical-professional-services/tree/16.0/ ps_partner_multi_relation They solved this by defining a partner relation "consortium", and every time an invoice for a consortium partner is posted, this invoice is split by the weights ("distribution key") on the consortium relation and new invoices are created for the involved partners. This concept should extend quite naturally to the purchase side, where you split the supplier invoices and deliveries according to the distribution key on the partner relation. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 12:32 - 23 Sep 2024
-
-
Fwd: Purchase Request inconvinient
---------- Forwarded message ---------
De: Manuel Scarafia <manuelscarafia@gmail.com>
Date: vie, 20 sept 2024 a las 15:38
Subject: Purchase Request inconvinient
To: <support@odoo-community.org>¡Hi! ¿How's going?I was using your Purchase Request module (purchase_request) when I noticed that it didn't let me change the currency on a Purchase Request; I was able to change the currency (from ARS to USD) but when I clicked "Save" it took me back to ARS again. I've also noticed that when I change the currency in the currency field, it doesn't change the currency in the product lines and doesn't let me change it as well.¿Do you have a fix for this problem? ¿Or is there any configuration that I could check?
by Manuel Scarafia - 09:57 - 20 Sep 2024 -
Subject: Welcome to the VentorTech Support!
Hi there,
We're excited to welcome you to the VentorTech Support! This is your one-stop shop for getting help with our products and services.
Here's what you can do in the portal:
- Create and track support requests: Get the help you need, when you need it.
- Access our knowledge base: Find answers to common questions and troubleshoot issues.
- Stay up-to-date: Receive notifications about product updates and announcements.
To get started, simply click the link below to set up your account: sign up link
We're here to help you make the most of our products. If you have any questions, don't hesitate to reach out!
Sincerely,
The VentorTech Team
by "VentorTech Support" <support@ventor.tech> - 02:36 - 20 Sep 2024-
Re: Subject: Welcome to the VentorTech Support!
HiI’m in testing , stock RFID implements to my client , as found your ventor app is very good , but I want to ask about RFID device , can ventor app support other RFID device not Zebra ,Thanks,Chedtha
From: VentorTech Support <notifications@odoo-community.org>
Date: Friday, 20 September BE 2567 at 19:38
To: Contributors <contributors@odoo-community.org>
Subject: Subject: Welcome to the VentorTech Support!
Hi there,
We're excited to welcome you to the VentorTech Support! This is your one-stop shop for getting help with our products and services.
Here's what you can do in the portal:
- Create and track support requests: Get the help you need, when you need it.
- Access our knowledge base: Find answers to common questions and troubleshoot issues.
- Stay up-to-date: Receive notifications about product updates and announcements.
To get started, simply click the link below to set up your account: sign up link
We're here to help you make the most of our products. If you have any questions, don't hesitate to reach out!
Sincerely,
The VentorTech Team
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Chedtha Makaew - 02:45 - 25 Aug 2025
-
OCA Days India - 2024 - 28th September
Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.If you have any questions please get in touch.Warmest regards,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 01:50 - 17 Sep 2024-
Re: OCA Days India - 2024 - 28th September
That's a great news!Thanks for sharing Rebecca :)Thanks Serpent and BizzAppDev :)On Tue, Sep 17, 2024 at 1:52 AM Rebecca Gellatly <rebecca@odoo-community.org> wrote:Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.If you have any questions please get in touch.Warmest regards,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo 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
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 10:36 - 18 Sep 2024 -
RE: OCA Days India - 2024 - 28th September
Jordan Kinsella reacted to your message:
From: Rebecca Gellatly <rebecca@odoo-community.org>
Sent: Monday, September 16, 2024 11:52:52 PM
To: Contributors <contributors@odoo-community.org>
Subject: OCA Days India - 2024 - 28th SeptemberCaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your Department Manager
Hello OCA Contributors.
I hope this email finds you all well.
I wanted to share with you that we have a one day OCA Days India 2024 event in Gandhinagar at the Serpent Consulting Offices from 10am - 5pm on Saturday the 28th September.
We had so many visitors at the Odoo Community Days just a couple of weeks ago, our friends at Serpent Consulting and BizzAppDev are keen to help support the community and share the OCA with Odoo supporters in the area.
There are talks to help with contributing, how to use the Indian Localisation and a number of sprint topics. Technical and Functional profiles are warmly encouraged to attend.
You can see the agenda here.You can register here.
If you are attending but haven't signed an ICLA, you can find all the details here. Please get on to this quick so I have time to action them before I start travelling from NZ to Belgium late next week for the European OCA Days 2024.
If you have any questions please get in touch.Warmest regards,Rebecca--
Rebecca GellatlyGeneral SecretaryOdoo 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 Jordan Kinsella - 10:21 - 18 Sep 2024
-
-
odoo kernel for web development
Hello Odoo community, I have started to make use of the best of odoo which is the magnificent ORM and OWL.
To simplify I made a special light version of odoo that runs only the base module and it's related logical associated modules.
I took this step as 4 months ago, I have created my company website:This website was built using Flask in the backend and OWL for the frontend.
It was very nice as I found OWL is quite simple and highly efficient as React and Vue.js.
Flask is great to run my website, but if I get a project that needs connection to the database then I have to use opensource ORM library and connect it with Flask, or I can directily use Django.
I am satisfied with Django and comfortable with Flask, but I like too much to make use of odoo ORM.
That is how I got the idea, and I hope I find it helpful in the future.
I also hope that you find my email useful.
Here is the repository for Odoo Kernel:
Thanks all
by Mohamed Alkobrosly - 09:01 - 15 Sep 2024 -
Preparing for Odoo 18
Hi everyone,If history repeats itself, we may have a new Odoo version 3 weeks from now.I created the tracking issue to prepare OCA tooling for Odoo 18, including suggestions for improvements: https://github.com/OCA/maintainer-tools/issues/628Contributions are most welcome, so don't hesitate to chime in if you want to help.Best regards,-Stéphane--Stéphane Bidoul
by Stéphane Bidoul - 03:41 - 12 Sep 2024-
Re: Preparing for Odoo 18
Well @Virginie Dewulf this is the perfect time to start elaborating some easy training guide (for beginners). We already talked about it- how to install a dev environment- how to find an OCA module- how to migrate a module- how to use openupgrade...Unless all the documentations already exist, i think it would be cool to have something like a training session to help neebies becoming masters...IMHOIf you launch a workgroup on that subject, I'll be happy to contributeBTW, the complete openupgrade documentation is here https://oca.github.io/OpenUpgrade/--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
www.invitu.comLe ven. 18 oct. 2024, 04:56, Virginie Dewulf <virginie@odoo-community.org> a écrit :Hello,Welcome in the community!On YouTube, there is now a dedicated playlist on the topic of OpenUpgrade and migrations from the past OCA Days.Testing the scripts is a very good way to start contributing to the OpenUpgrade project, indeed. Pay attention to the fact that sometimes the scripts are good but your data cause issues.To start contributing to review and write the scripts themselves, experience shows that you need to be an Odoo expert from the technical and functional point of view, with at least several years of practice as an Odoo developer, because you need to understand well how things work in the different versions from a technical and functional perspective. So we hope to see you contributing there in a bit!Enjoy your weekend everyone!Le ven. 18 oct. 2024, 11:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :On 10/18/24 04:03, Jacob Christ wrote: > I would like to help improve OpenUpgrade but I don't know how to > get started. If nothing else, I'm happy to test 16 to 17 upgrades as > improvements are made. In one of the previous OCA days, there was a talk about how to get started with OpenUpgrade. Might be this one: https://www.youtube.com/watch?v=Vx7-PuXCIsY but there could be more. It seems everybody has their own way of doing things; I think what's "common" is to make a "build" for each version and then include OpenUpgrade in it (it could be for example a Doodba docker container, or one of the other build systems that are around - we use our own Doodba-based concoction at https://github.com/sunflowerit/waftlib) and then add OpenUpgrade into the build and run odoo -u on each version in sequence. Whichever build system you choose, like Graeme says, it's handy if gitaggregator is an integral part of it, so that you can easily include patch PR's into the build - your own, or ones from others. With every migration we have done so far there are at least a handful errors that you will run into - usually it's a case of the database in your data being slightly different than a specific OpenUpgrade script expects it to be. It can be all kinds of things, for example it might be that on Odoo 14, it was possible to set a financial ledger account to a certain type that it should not be, and you changed it, but now OpenUpgrade does not cover that specific case. What you can then do is either adjust your data on Odoo 14 manually and try the migration again from start, or to make a migration script yourself, and either run it as a custom script or actually propose it as an addition to OpenUpgrade using a PR. If you're not up to this whole process, what's also a common method for instances without a lot of data is to start over with a fresh Odoo 17 instance and use import/export to get your data across. That's of course also laborious but in some cases it can be a good option.
_______________________________________________
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 Cyril VINH-TUNG - 06:55 - 18 Oct 2024 -
Re: Preparing for Odoo 18
Hello,Welcome in the community!On YouTube, there is now a dedicated playlist on the topic of OpenUpgrade and migrations from the past OCA Days.Testing the scripts is a very good way to start contributing to the OpenUpgrade project, indeed. Pay attention to the fact that sometimes the scripts are good but your data cause issues.To start contributing to review and write the scripts themselves, experience shows that you need to be an Odoo expert from the technical and functional point of view, with at least several years of practice as an Odoo developer, because you need to understand well how things work in the different versions from a technical and functional perspective. So we hope to see you contributing there in a bit!Enjoy your weekend everyone!Le ven. 18 oct. 2024, 11:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :On 10/18/24 04:03, Jacob Christ wrote: > I would like to help improve OpenUpgrade but I don't know how to > get started. If nothing else, I'm happy to test 16 to 17 upgrades as > improvements are made. In one of the previous OCA days, there was a talk about how to get started with OpenUpgrade. Might be this one: https://www.youtube.com/watch?v=Vx7-PuXCIsY but there could be more. It seems everybody has their own way of doing things; I think what's "common" is to make a "build" for each version and then include OpenUpgrade in it (it could be for example a Doodba docker container, or one of the other build systems that are around - we use our own Doodba-based concoction at https://github.com/sunflowerit/waftlib) and then add OpenUpgrade into the build and run odoo -u on each version in sequence. Whichever build system you choose, like Graeme says, it's handy if gitaggregator is an integral part of it, so that you can easily include patch PR's into the build - your own, or ones from others. With every migration we have done so far there are at least a handful errors that you will run into - usually it's a case of the database in your data being slightly different than a specific OpenUpgrade script expects it to be. It can be all kinds of things, for example it might be that on Odoo 14, it was possible to set a financial ledger account to a certain type that it should not be, and you changed it, but now OpenUpgrade does not cover that specific case. What you can then do is either adjust your data on Odoo 14 manually and try the migration again from start, or to make a migration script yourself, and either run it as a custom script or actually propose it as an addition to OpenUpgrade using a PR. If you're not up to this whole process, what's also a common method for instances without a lot of data is to start over with a fresh Odoo 17 instance and use import/export to get your data across. That's of course also laborious but in some cases it can be a good option.
_______________________________________________
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 - 04:55 - 18 Oct 2024 -
Re: Preparing for Odoo 18
On 10/18/24 04:03, Jacob Christ wrote: > I would like to help improve OpenUpgrade but I don't know how to > get started. If nothing else, I'm happy to test 16 to 17 upgrades as > improvements are made. In one of the previous OCA days, there was a talk about how to get started with OpenUpgrade. Might be this one: https://www.youtube.com/watch?v=Vx7-PuXCIsY but there could be more. It seems everybody has their own way of doing things; I think what's "common" is to make a "build" for each version and then include OpenUpgrade in it (it could be for example a Doodba docker container, or one of the other build systems that are around - we use our own Doodba-based concoction at https://github.com/sunflowerit/waftlib) and then add OpenUpgrade into the build and run odoo -u on each version in sequence. Whichever build system you choose, like Graeme says, it's handy if gitaggregator is an integral part of it, so that you can easily include patch PR's into the build - your own, or ones from others. With every migration we have done so far there are at least a handful errors that you will run into - usually it's a case of the database in your data being slightly different than a specific OpenUpgrade script expects it to be. It can be all kinds of things, for example it might be that on Odoo 14, it was possible to set a financial ledger account to a certain type that it should not be, and you changed it, but now OpenUpgrade does not cover that specific case. What you can then do is either adjust your data on Odoo 14 manually and try the migration again from start, or to make a migration script yourself, and either run it as a custom script or actually propose it as an addition to OpenUpgrade using a PR. If you're not up to this whole process, what's also a common method for instances without a lot of data is to start over with a fresh Odoo 17 instance and use import/export to get your data across. That's of course also laborious but in some cases it can be a good option.
by Tom Blauwendraat - 11:11 - 18 Oct 2024 -
Re: Preparing for Odoo 18
Hi,Having done more upgrades/migrations than I care to remember 15-20 hours is reasonable even if getting someone to do it via enterprise for you. Big complex ones with custom code and/or lots of data involved can be months.You would normally have builds, testing, user training, scheduling to go live, then a final go live, then day 1 support (because in that testing phase no one really tested). A completely smooth upgrade process with zero issues/compromises/decisions using any upgrade method on anything but the simplest system feels like winning the lottery.https://github.com/OCA/OpenUpgrade/issues/4124 is the issue that covers off what has been done for v17, and what is an Open PR. Getting used to building with a tool called git-aggregator to pull in all those Open PR's and run and test them can be useful and makes things a lot quicker to test.In any case, version 16 is a good version.On Fri, Oct 18, 2024 at 3:02 PM Jacob Christ <notifications@odoo-community.org> wrote:Stéphane et al,I just joined the OCA a few days ago.My background (sorry for the long introduction, you can skip to the TL;DR if you are busy):I'm a software/electrictronics engineer and run my own little company and teach an embedded electronics class once a year at a local junior college. A company I worked for tried to implement Odoo 2 years ago but failed. I had never heard of Odoo but I still had a bad taste in my mouth from a recent SAP experience and I was intrigued. A little research and I discovered that it was open source* and decided to try to install it. It took me about 16 hours to figure out how to get Odoo14 installed. I discovered the web authoring tools were better than my CSS skills and left it up and pointed my domain at the installation. About a year ago I was trying to figure out how to upgrade Odoo and it seemed like my best option was to pay for hosting with Odoo S.A. I tried to make it happen at the time but it didn't work out for me. Two weeks ago I got a quote for upgrading Odoo from 14 to 18 from an integrator and it came back that it should take between 15-20 hours to do. I couldn't believe that it would take this long so I decided to investigate how difficult this was. I quickly learned that I had to go from one version to the next one at a time and that I needed Odoo 14, 15, 16, 17 and 18 installed. Since it had been 2 years since I installed Odoo I had to relearn the process. It took me about 2 hours to get Odoo 14 installed and I documented what I learned. I blew away Odoo 14 and started over. I was able to do the install in 30 minutes. Then probably another 15 mins for each additional version to 18. Next I spent 4 hours trying to figure out how to run OpenUpgrade. Once I figured it out I was able to quickly get from 14 to 15, 15 to 16 (though some pictures resized at 16 in my store and I don't know why) and 16 to 17 but 17 wasn't working. I took another four hours to figure out that the 16 to 17 upgrade is not working yet. In all I spent about 13 hours on the process and decided that the quote I received was high if I figured out how to do upgrades, having never done them before. More importantly I learned alot about Odoo and I feel more confident using it to run my business. I also am willing to help improve Odoo and the scripts.TL;DRI would like to help improve OpenUpgrade but I don't know how to get started. If nothing else, I'm happy to test 16 to 17 upgrades as improvements are made.On Wed, Oct 16, 2024 at 9:33 AM Stéphane Bidoul <notifications@odoo-community.org> wrote:Hi everyone,The 18.0 branches were created 10 days ago, and migrations are going full speed already.Thanks a lot to everyone who helped and continued to help since, this is much appreciated !We need to push an update to the dotfiles, with a new version of pylint-odoo with Odoo 18 support.At the same time, we'll update the JS linters as well as prettier, taking advantage of an improved version of the xml auto formatter.This may make some 18.0 branches or open PR red, so keep an eye on it.I'll push that one of these evenings. In the meantime, PSC can already apply it by running "pipx run copier update --trust --defaults".Please create an issue on https://github.com/OCA/oca-addons-repo-template/ if you encounter problems.-StéphaneOn Thu, Sep 12, 2024 at 3:36 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi everyone,If history repeats itself, we may have a new Odoo version 3 weeks from now.I created the tracking issue to prepare OCA tooling for Odoo 18, including suggestions for improvements: https://github.com/OCA/maintainer-tools/issues/628Contributions are most welcome, so don't hesitate to chime in if you want to help.Best regards,-Stéphane--Stéphane Bidoul_______________________________________________
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 Graeme Gellatly - 04:46 - 18 Oct 2024 -
Re: Preparing for Odoo 18
Stéphane et al,I just joined the OCA a few days ago.My background (sorry for the long introduction, you can skip to the TL;DR if you are busy):I'm a software/electrictronics engineer and run my own little company and teach an embedded electronics class once a year at a local junior college. A company I worked for tried to implement Odoo 2 years ago but failed. I had never heard of Odoo but I still had a bad taste in my mouth from a recent SAP experience and I was intrigued. A little research and I discovered that it was open source* and decided to try to install it. It took me about 16 hours to figure out how to get Odoo14 installed. I discovered the web authoring tools were better than my CSS skills and left it up and pointed my domain at the installation. About a year ago I was trying to figure out how to upgrade Odoo and it seemed like my best option was to pay for hosting with Odoo S.A. I tried to make it happen at the time but it didn't work out for me. Two weeks ago I got a quote for upgrading Odoo from 14 to 18 from an integrator and it came back that it should take between 15-20 hours to do. I couldn't believe that it would take this long so I decided to investigate how difficult this was. I quickly learned that I had to go from one version to the next one at a time and that I needed Odoo 14, 15, 16, 17 and 18 installed. Since it had been 2 years since I installed Odoo I had to relearn the process. It took me about 2 hours to get Odoo 14 installed and I documented what I learned. I blew away Odoo 14 and started over. I was able to do the install in 30 minutes. Then probably another 15 mins for each additional version to 18. Next I spent 4 hours trying to figure out how to run OpenUpgrade. Once I figured it out I was able to quickly get from 14 to 15, 15 to 16 (though some pictures resized at 16 in my store and I don't know why) and 16 to 17 but 17 wasn't working. I took another four hours to figure out that the 16 to 17 upgrade is not working yet. In all I spent about 13 hours on the process and decided that the quote I received was high if I figured out how to do upgrades, having never done them before. More importantly I learned alot about Odoo and I feel more confident using it to run my business. I also am willing to help improve Odoo and the scripts.TL;DRI would like to help improve OpenUpgrade but I don't know how to get started. If nothing else, I'm happy to test 16 to 17 upgrades as improvements are made.On Wed, Oct 16, 2024 at 9:33 AM Stéphane Bidoul <notifications@odoo-community.org> wrote:Hi everyone,The 18.0 branches were created 10 days ago, and migrations are going full speed already.Thanks a lot to everyone who helped and continued to help since, this is much appreciated !We need to push an update to the dotfiles, with a new version of pylint-odoo with Odoo 18 support.At the same time, we'll update the JS linters as well as prettier, taking advantage of an improved version of the xml auto formatter.This may make some 18.0 branches or open PR red, so keep an eye on it.I'll push that one of these evenings. In the meantime, PSC can already apply it by running "pipx run copier update --trust --defaults".Please create an issue on https://github.com/OCA/oca-addons-repo-template/ if you encounter problems.-StéphaneOn Thu, Sep 12, 2024 at 3:36 PM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:Hi everyone,If history repeats itself, we may have a new Odoo version 3 weeks from now.I created the tracking issue to prepare OCA tooling for Odoo 18, including suggestions for improvements: https://github.com/OCA/maintainer-tools/issues/628Contributions are most welcome, so don't hesitate to chime in if you want to help.Best regards,-Stéphane--Stéphane Bidoul_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jacob Christ - 04:01 - 18 Oct 2024
-
-
Triple discount modules refactor and maturity levels
Hello communityA few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.We actually have migration PRs for triple discount modules in 17.0:My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?Please let me know what do you guys think about it.Best regards.camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSAkim JuilleratBusiness solutionsSoftware architect
by Akim Juillerat - 07:06 - 10 Sep 2024-
Re: Triple discount modules refactor and maturity levels
Hi Akim,Thank you for your hard work on the triple discount module. IMO we should merge the 16.0 branch. By bumping the version to the next major level, the signal is clear that this new version contains breaking changes. I'm often reluctant to introduce such deep changes in a ‘stable’ version. In this case, I feel it's justified by the need to introduce a cleaner/simpler approach and remove hacks made necessary by the complexity of the previous one. This cleaner architecture also provides a better basis for all the modules based on this module. Regarding the maturity level, the default one is beta, I would find it logical to prohibit such changes on a ‘stable’/‘mature’ version, but not on a ‘beta’ version.Regards,lmiOn Tue, Sep 10, 2024 at 7:08 PM Akim Juillerat <notifications@odoo-community.org> wrote:Hello communityA few months ago, I started a big refactor of triple discount modules in v16.0 that ended up with the following PRs:Since this is a BIG breaking change I'm wondering if these should be merged only in v17.0 instead of 16.0.We actually have migration PRs for triple discount modules in 17.0:My feeling is we must probably leverage the maturity levels to define what can be merged in a released version, and avoid such breaking change when the maturity level is stable/mature. But then, if there is no maturity level in manifest, as is the case here, it seems to default to Beta in readme generation. Should we consider this as a rule?Do we then want to move forward with this refactor in 16.0 or keep it for 17.0 and eventually define a stable maturity level for 17.0?Please let me know what do you guys think about it.Best regards.camptocampINNOVATIVE SOLUTIONSBY OPEN SOURCE EXPERTSAkim JuilleratBusiness solutionsSoftware architect_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Laurent MignonTechnical lead / Management TeamT: +32 2 8883148Atrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumVal Benoit, Quai Banning 6 | B-4000 Liège | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg
by Laurent Mignon - 08:56 - 11 Sep 2024
-
-
Management System Odoo 17
Hello, I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?Thanks..
PT Laris ChandraSole Distributor of :STP - PENRAY - TURTLE WAX - SIP - PRESTONE (Radiator Products) - ARMOR ALL - CHW - AUTOGARDJl. Pluit Utara Raya Blok B-VIII No. 47 RT 05/04 Penjaringan Jak-Ut 14450 – IndonesiaPhone: +62 21 667 6699 | Fax: +62 21 667 6789Visit PT Laris Chandra at : larischandra.comThis email and any attachments are confidential. If you are not the addressee or have received this message in error, please delete all copies from your system and notify the sender immediately. The sender does not accept liability for any problems that may arise from this email transmission.
by Lingga Pratama - 11:17 - 4 Sep 2024-
Re: Management System Odoo 17
Hello Lingga,If you can't wait and have some budget, we can discuss speeding up the process.Please email me privately if you are interested.Cheers,MAXIME CHAMBREUIL
DIRECTOR GENERAL LATAMCalendario
T: +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.On Wed, Sep 4, 2024 at 4:22 AM Stefano Consolaro <notifications@odoo-community.org> wrote:Hi,v17.0 is being ported (migrated from 16.0) and you can see the available modules here https://github.com/OCA/management-system/tree/17.0The modules that will be migrated are (probably) in v16.0, see here https://github.com/OCA/management-system/tree/16.0Porting works in progress are here https://github.com/OCA/management-system/pulls?q=is%3Apr+is%3Aopen++17.0+migIt takes a little patience...Da "Lingga Pratama" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Wed, 04 Sep 2024 09:18:34 -0000Oggetto Management System Odoo 17
Hello, I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?Thanks..Stefano Consolaro_______________________________________________
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 - 07:00 - 7 Sep 2024 -
Re:Management System Odoo 17
Hi,v17.0 is being ported (migrated from 16.0) and you can see the available modules here https://github.com/OCA/management-system/tree/17.0The modules that will be migrated are (probably) in v16.0, see here https://github.com/OCA/management-system/tree/16.0Porting works in progress are here https://github.com/OCA/management-system/pulls?q=is%3Apr+is%3Aopen++17.0+migIt takes a little patience...Da "Lingga Pratama" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Wed, 04 Sep 2024 09:18:34 -0000Oggetto Management System Odoo 17
Hello, I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?Thanks..Stefano Consolarowww.mymage.it
by Stefano Consolaro - 12:21 - 4 Sep 2024
-
-
Re: Contributors
Hello, I've tried running the management system module from "https://github.com/OCA/management-system" but it's only for the settings page. Is the management system module available for odoo 17? How do I implement it?
Thank You..
PT Laris ChandraSole Distributor of :STP - PENRAY - TURTLE WAX - SIP - PRESTONE (Radiator Products) - ARMOR ALL - CHW - AUTOGARDJl. Pluit Utara Raya Blok B-VIII No. 47 RT 05/04 Penjaringan Jak-Ut 14450 – IndonesiaPhone: +62 21 667 6699 | Fax: +62 21 667 6789Visit PT Laris Chandra at : larischandra.comThis email and any attachments are confidential. If you are not the addressee or have received this message in error, please delete all copies from your system and notify the sender immediately. The sender does not accept liability for any problems that may arise from this email transmission.
by Lingga Pratama - 11:11 - 4 Sep 2024 -
Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event name: Odoo Experience Exhibition 2024
Date: 02 - 04 Oct 2024
Location : Brussels Expo - Exhibition Center, Brussels, Belgium
Attendees/Visitors Count: 7500
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Aria Wells
by Aria.Wells@leadboostershq.com - 08:41 - 4 Sep 2024-
Re: Fwd: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
Unfortunately Virginie, anyone who knows the email address, contributors@odoo-community.org, can write to this list.
Questions is, who is it? Most likely not ... Aria Wells!!
Let's do some Sherlack Homes activities and investigate the original email headers.
Received: from mail-wm1-x361.google.com (mail-wm1-x361.google.com [IPv6:2a00:1450:4864:20::361])
Looks like Aria Wells, or whatever his/her/it name is, is using a Google mail server located in Ireland, see attached screenshot.
Has anyone else other info about this "person"?
Best regards,Michel Stroom
Office EverywhereHello,This is the kind of email I'd like to not receive anymore on the Contributors mailing list, but the person who sent it is not in the mailing list.How is this possible?Can anyone write to the contributors mailing list?I'll dig into this later ^^
---------- Forwarded message ---------
De : Aria.Wells <notifications@odoo-community.org>
Date: mer. 4 sept. 2024 à 08:42
Subject: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
To: Contributors <contributors@odoo-community.org>
Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event name: Odoo Experience Exhibition 2024
Date: 02 - 04 Oct 2024
Location : Brussels Expo - Exhibition Center, Brussels, Belgium
Attendees/Visitors Count: 7500
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Aria Wells_______________________________________________
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 Michel Stroom - 11:41 - 4 Sep 2024 -
Fwd: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
Hello,This is the kind of email I'd like to not receive anymore on the Contributors mailing list, but the person who sent it is not in the mailing list.How is this possible?Can anyone write to the contributors mailing list?I'll dig into this later ^^---------- Forwarded message ---------
De : Aria.Wells <notifications@odoo-community.org>
Date: mer. 4 sept. 2024 à 08:42
Subject: Odoo Experience Exhibition 2024: Comprehensive Attendee Directory
To: Contributors <contributors@odoo-community.org>Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event name: Odoo Experience Exhibition 2024
Date: 02 - 04 Oct 2024
Location : Brussels Expo - Exhibition Center, Brussels, Belgium
Attendees/Visitors Count: 7500
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Aria Wells_______________________________________________
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 - 09:01 - 4 Sep 2024
-
-
OCA Technical Training: 20h online from 16th Sept to 22nd Oct
Hello Contributors,I hope everything is doing great!Did you hear that the OCA launched an Odoo Technical Training?It starts on 16th September for a 5-week journey (2 hours/session, 10 sessions).The full schedule and information are here:To register:In summary, it is aimed at
- new developers hired by Odoo integrator companies, as a complementary technical onboarding
- freelance developers wanting to start a career within the Odoo world
- any developer who has been around for a time but would like to go back to the foundation of Odoo development
The trainers are experienced Odoo developers:- Daniel Reis (Open Source Integrators), author of Odoo Development Essentials book
- Radovan Školník (Data Dance)
- Carmen Bianca Bakker (Coop IT Easy)
- Tom Blauwendraat (Therp)
- Ronald Portier (Therp)
And below is the full schedule of the 10 Sessions.We still have seats available!If you are interested but not available on the dates, let me know (virginie@odoo-community.org)Have a good week,Virginie------Session 1:
* Odoo product overview: versions, licenses, architecture, components
* OCA organization, contribution processes, tooling, coding standards
* You and the OCA: how to use or integrate OCA code in your projects
Sessions 2, 3 and 4:* Odoo architecture - client / server / database
* Database nature of Odoo
* Basic building blocks - models, fields, views, ...
* Installing local Odoo development environment
* Database configuration
* git repositories
* Documentation / Resources
* First module
* Basic building blocks - models and views
* Extension mechanisms
Sessions 5, 6 and 7:
* How the Odoo Object-Relational Mapping (ORM) works* Available data types in the Odoo ORM
* Querying your database using the Odoo ORM
* Debugging Odoo
* Writing tests for your Odoo modules
* How to adjust Odoo views to make them useful and beautifulSessions 8, 9 and 10:
Contributing to the OCA:
* The OCA review process
*The importance of unit tests
* The important of pre-commit
* OCA runboat and CI
* Translations in OCA
* Stale / not stale
* How to contact a PSC member or apply to be one yourself
* Before you submit your PR: checking if similar work already exists, and deciding on which repository to put it
* Python dependencies, dependencies between PR's
* "Rebel modules"
Modules Migration:
*how migrations are part of the OCA model
* data migration and openupgrade
* code migration:
-- The need to keep history
-- Technical method
-- Following all the steps
-- Maintain and increase code quality
-- Improving and adding tests------
by Virginie Dewulf - 12:51 - 2 Sep 2024 -
Seeking References for HR Implementations with Large Companies
Hello Community,
we have a customer based in California and he is looking for a References of large companies using HR Modules, Please share any references that we can use for this customer.
Best Regards,
Manish Mannan
Director - Sales
Sales | O2B Technologies
by Manish Mannan - 09:51 - 2 Sep 2024 -
RFQ for OCA Days 2024 Video Post Production
Hello OCA Contributors,I hope this finds you all well.We are getting the final details ready for OCA Days 2024.If you haven't registered yet, there is still time, you can do so here.I'm sharing the RFQ for Video Post Production of the recorded talks - have you got a digital superstar in your company who could help? Please share it around.Deadline for submission for the RFQ is 18th September 2024.You can find out more on our RFQ process page.If you have any questions please get in touch.Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 01:16 - 28 Aug 2024-
Re: RFQ for OCA Days 2024 Video Post Production
Hello OCA Contributors,Just a reminder this RFQ closes today.If you have the skills within your company to help us out after the OCA Days, we would love to hear from you.Warm regards,RebeccaOn Wed, 28 Aug 2024 at 23:11, Rebecca Gellatly <rebecca@odoo-community.org> wrote:Hello OCA Contributors,I hope this finds you all well.We are getting the final details ready for OCA Days 2024.If you haven't registered yet, there is still time, you can do so here.I'm sharing the RFQ for Video Post Production of the recorded talks - have you got a digital superstar in your company who could help? Please share it around.Deadline for submission for the RFQ is 18th September 2024.You can find out more on our RFQ process page.If you have any questions please get in touch.Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 12:21 - 18 Sep 2024
-
-
odoo-community.org has a new home
Hi everyone,https://odoo-community.org has found a new home on a more powerful server.Everything should work as before, just faster. Let me know if you notice anything is off.Best regards,-Stéphane--Stéphane Bidoul
by Stéphane Bidoul - 12:06 - 22 Aug 2024-
Re: odoo-community.org has a new home
thanks :)
From: Rafael Blasco <notifications@odoo-community.org>
Sent: Wednesday, August 28, 2024 12:07 PM
To: Contributors <contributors@odoo-community.org>
Subject: RE: odoo-community.org has a new homeThank you very much Stéphane!
De: Stéphane Bidoul <notifications@odoo-community.org>
Enviado el: jueves, 22 de agosto de 2024 0:08
Para: Contributors <contributors@odoo-community.org>
Asunto: odoo-community.org has a new homeHi everyone,
https://odoo-community.org has found a new home on a more powerful server.
Everything should work as before, just faster. Let me know if you notice anything is off.
Best regards,
-Stéphane
--
Stéphane Bidoul
_______________________________________________
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 Manish Bohra. - 09:51 - 28 Aug 2024 -
RE: odoo-community.org has a new home
Thank you very much Stéphane!
De: Stéphane Bidoul <notifications@odoo-community.org>
Enviado el: jueves, 22 de agosto de 2024 0:08
Para: Contributors <contributors@odoo-community.org>
Asunto: odoo-community.org has a new homeHi everyone,
https://odoo-community.org has found a new home on a more powerful server.
Everything should work as before, just faster. Let me know if you notice anything is off.
Best regards,
-Stéphane
--
Stéphane Bidoul
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (Moduon) - 08:36 - 28 Aug 2024 -
Re: odoo-community.org has a new home
Super cool! Thank you Stéphane! :)On Thu, Aug 22, 2024 at 12:07 AM Stéphane Bidoul <notifications@odoo-community.org> wrote:Hi everyone,https://odoo-community.org has found a new home on a more powerful server.Everything should work as before, just faster. Let me know if you notice anything is off.Best regards,-Stéphane--Stéphane Bidoul
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 08:26 - 27 Aug 2024 -
Re: odoo-community.org has a new home
Very awesome and very appreciated!On Tue, 27 Aug 2024 at 02:38, Francesco Ballerini <notifications@odoo-community.org> wrote:Nice! Thanks--Francesco BalleriniIl giorno lun 26 ago 2024 alle ore 14:18 Antonio M. Vigliotti <notifications@odoo-community.org> ha scritto:
Great job!
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 26/08/2024 10:02, Virginie Dewulf ha scritto:
Many thanks, it changes a lot on the backend side as well :)
Le lun. 26 août 2024 à 08:43, David Beal <notifications@odoo-community.org> a écrit :
Le lun. 26 août 2024 à 08:32, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
Thanks :) Alexandre On 22/08/2024 00:07, Stéphane Bidoul wrote: > Hi everyone, > > https://odoo-community.org <https://odoo-community.org> has found a new > home on a more powerful server. > > Everything should work as before, just faster. Let me know if you notice > anything is off. > > Best regards, > > -Stéphane > > -- > Stéphane Bidoul > http://acsone.eu/ <http://acsone.eu/> > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
_______________________________________________
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
--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly (OCA) - 03:53 - 27 Aug 2024 -
Re: odoo-community.org has a new home
Nice! Thanks--Francesco BalleriniIl giorno lun 26 ago 2024 alle ore 14:18 Antonio M. Vigliotti <notifications@odoo-community.org> ha scritto:
Great job!
Antonio M. Vigliotti
Mobile (+39) 342.8740910
Il 26/08/2024 10:02, Virginie Dewulf ha scritto:
Many thanks, it changes a lot on the backend side as well :)
Le lun. 26 août 2024 à 08:43, David Beal <notifications@odoo-community.org> a écrit :
Le lun. 26 août 2024 à 08:32, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
Thanks :) Alexandre On 22/08/2024 00:07, Stéphane Bidoul wrote: > Hi everyone, > > https://odoo-community.org <https://odoo-community.org> has found a new > home on a more powerful server. > > Everything should work as before, just faster. Let me know if you notice > anything is off. > > Best regards, > > -Stéphane > > -- > Stéphane Bidoul > http://acsone.eu/ <http://acsone.eu/> > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
_______________________________________________
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 Francesco Ballerini - 04:36 - 26 Aug 2024
-
-
Test
This is a test message, preparing for the migration of the OCA Odoo instance to a new server.-sbi
by Stéphane Bidoul - 10:41 - 20 Aug 2024-
Re: Test
Success again!Regards,Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inOn Wed, 21 Aug 2024 at 5:28 PM, Stéphane Bidoul <notifications@odoo-community.org> wrote:And testing again from the other side.On Tue, Aug 20, 2024 at 11:12 PM Pierre Verkest <notifications@odoo-community.org> wrote:It's wirking !Le mar. 20 août 2024 à 22:43, Stéphane Bidoul <notifications@odoo-community.org> a écrit :This is a test message, preparing for the migration of the OCA Odoo instance to a new server.-sbi
_______________________________________________
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 Jay Vora - 11:41 - 21 Aug 2024 -
Re: Test
And testing again from the other side.On Tue, Aug 20, 2024 at 11:12 PM Pierre Verkest <notifications@odoo-community.org> wrote:It's wirking !Le mar. 20 août 2024 à 22:43, Stéphane Bidoul <notifications@odoo-community.org> a écrit :This is a test message, preparing for the migration of the OCA Odoo instance to a new server.-sbi
_______________________________________________
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 Stéphane Bidoul - 11:26 - 21 Aug 2024 -
Re: Test
It's wirking !Le mar. 20 août 2024 à 22:43, Stéphane Bidoul <notifications@odoo-community.org> a écrit :This is a test message, preparing for the migration of the OCA Odoo instance to a new server.-sbi_______________________________________________
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 - 11:11 - 20 Aug 2024
-
-
Large Data Files
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
by "Jerôme Dewandre" <jerome.dewandre.mail@gmail.com> - 05:31 - 20 Aug 2024-
Re: Large Data Files
Sorry for the wrong urlHere is the good oneLe mer. 7 mai 2025 à 10:16, David Beal <david.beal@akretion.com> a écrit :Hi Jérome,Additionally you may reach more performance with https://github.com/yanyanren123hotmailcom/connectorxHere is the explanationI experimented successfully connectorx with polars (but not benchmark it myself with other solutions)RegardsLe ven. 2 mai 2025 à 23:57, Jerôme Dewandre <notifications@odoo-community.org> a écrit :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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 10:26 - 7 May 2025 -
Re: Large Data Files
Hi Jérome,Additionally you may reach more performance with https://github.com/yanyanren123hotmailcom/connectorxHere is the explanationI experimented successfully connectorx with polars (but not benchmark it myself with other solutions)RegardsLe ven. 2 mai 2025 à 23:57, Jerôme Dewandre <notifications@odoo-community.org> a écrit :
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
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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David BEAL - 10:21 - 7 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
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: Large Data Files
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
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
by David BEAL - 09:16 - 21 Aug 2024 -
Re: Large Data Files
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
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
by "Graeme Gellatly" <graeme@moahub.nz> - 01:56 - 21 Aug 2024
-
-
Visitors Database of Odoo Website Day 2024
Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event Details:
Event Name: Odoo Website Day 2024
Date:03 Oct 2024
Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium
Visitors/Attendees:5,000
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Ivy Rodriguez
by Ivy.Rodriguez@galaxileadshq.com - 03:01 - 15 Aug 2024-
Re: Visitors Database of Odoo Website Day 2024
Hello everyone,We are trying to find a way to stop receiving this kind of spam on the OCA Contributors Mailing List.Please, don't answer to this person by answering to its first email, this spams everyone in the mailing list.Thanks!Le ven. 16 août 2024 à 13:57, DIALLO Innah <notifications@odoo-community.org> a écrit :
Hello,
Thank you so much, but actually i am not interested, thank you very much.
Have a nice day.Le jeu. 15 août 2024 à 13:02, Ivy.Rodriguez <notifications@odoo-community.org> a écrit :Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event Details:
Event Name: Odoo Website Day 2024
Date:03 Oct 2024
Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium
Visitors/Attendees:5,000
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Ivy Rodriguez_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf - 02:30 - 16 Aug 2024 -
Re: Visitors Database of Odoo Website Day 2024
Hello,
Thank you so much, but actually i am not interested, thank you very much.
Have a nice day.Le jeu. 15 août 2024 à 13:02, Ivy.Rodriguez <notifications@odoo-community.org> a écrit :Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event Details:
Event Name: Odoo Website Day 2024
Date:03 Oct 2024
Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium
Visitors/Attendees:5,000
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Ivy Rodriguez_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by hawa1 - 01:54 - 16 Aug 2024 -
Re: Visitors Database of Odoo Website Day 2024
How much ?
On Thu, 15 Aug 2024, 20:02 Ivy.Rodriguez, <notifications@odoo-community.org> wrote:Hi,
Hope all is well with you!
We're offering a special deal: discounted cost and extra information.
We're following up to see if you're interested in getting the Visitors/Attendees List.
Event Details:
Event Name: Odoo Website Day 2024
Date:03 Oct 2024
Location: Brussels Exhibition Centre at the Brussels Expo, Brussels, Belgium
Visitors/Attendees:5,000
Each record contains: Contact Name, Email Address, Company Name, URL/Website, Phone No, Title/Designation.
Could you let us know if you're interested? We'll then send you the discounted cost and more details.
Waiting for your positive response.
Thanks and Regards
Ivy Rodriguez_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by milori2006 - 04:45 - 15 Aug 2024
-
-
pre-commit help
I'm having trouble with pre-commit. Can someone give me a few tips?I tried to follow the instructions in the README for maintainer-tools:I installed maintainer-tools and activated the venv, then ran the following.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=alwaysStill failing the pre-commit test on pull request.Maybe there is more documentation that I am missing?Matt
by Matt - 11:00 - 14 Aug 2024-
Re: pre-commit help
Not all the errors that precommit gives are automatically solved, some you have to solve them manually.
Usually the precommit log as displayed on the PR is pretty clear about what the problem is.
14 aug. 2024 23:01:57 Matt Taylor <notifications@odoo-community.org>:
I'm having trouble with pre-commit. Can someone give me a few tips?
I tried to follow the instructions in the README for maintainer-tools:
I installed maintainer-tools and activated the venv, then ran the following
.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always
Still failing the pre-commit test on pull request.
Maybe there is more documentation that I am missing?
Matt
_______________________________________________
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 - 08:31 - 15 Aug 2024 -
-
Re: pre-commit help
To run pre-commit, you first need to install it:
$ pip install pre-commit
And then in (each) cloned repo, install the pre-commit hooks with:
$ pre-commit install
Now you can run :
$ pre-commit run -a
At least that's what works for me.
--Daniel
On 14/08/2024 22:01, Matt Taylor wrote:
I'm having trouble with pre-commit. Can someone give me a few tips?
I tried to follow the instructions in the README for maintainer-tools:
I installed maintainer-tools and activated the venv, then ran the following
.../repo/module$ pre-commit run --all-files --show-diff-on-failure --color=always
Still failing the pre-commit test on pull request.
Maybe there is more documentation that I am missing?
Matt
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
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
by Daniel Reis - 11:22 - 14 Aug 2024
-
-
Highlights on my contributions to Odoo Community Association
Here is my experience with my first contribution to OCA:I hope it will be useful to the new contributors.
Thanks all,
by Mohamed Alkobrosly - 04:16 - 13 Aug 2024-
Re: Highlights on my contributions to Odoo Community Association
Ok, it is really good and useful to refer to all the points that I still miss.
Some of this information is very new to me like mentioning the PR in a comment of the "Migration to version 17.0 #1446" PR.
In addition to this, I am not aware of what still missing to merge the PR, I only know that there should be two reviews, only!
But if there is still something that I do not know please help me to get it and fill the gap.
As all of that will be mentioned on the same blog post, and we all will benefit and the rest of the world.
Thanks.On Tue, Aug 13, 2024 at 5:51 PM Radovan Skolnik <notifications@odoo-community.org> wrote:Hi,
first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.
I did quick review of your blog post. Few suggestions:
*) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:
*) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.
*) "(7) After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.
*) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.
*) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0" - in your case https://github.com/OCA/product-attribute/issues/1446
One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.
So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.
Best luck and regards
Radovan Skolnik
On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:
> Here is my experience with my first contribution to OCA:
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [1] I hope it will be useful to the new contributors.
> Thanks all,
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [2]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]
>
>
>
> [1]
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [2] https://odoo-community.org/groups/contributors-15
> [3] 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 Mohamed Alkobrosly - 05:11 - 13 Aug 2024 -
Re: Highlights on my contributions to Odoo Community Association
Hi,
first of all thank you for your effort. New contrinutors are always welcome. We all know the learning curve is quite steep from beginning but try to help.
I did quick review of your blog post. Few suggestions:
*) Update the formatting to make it more readable. After the first paragraph the font gets quite small and colors hard to see:
*) There is no need in my opinion to repeat contents of the links that ar provided. Rather focus on things that were not so obvious (if any) from the instructions.
*) "(7) After pushing changes to your copy of the original repository on GitHub, compare your version ..." - you're describing standard PR functionality of GitHub. It would be better to say so.
*) "After that you can send an email on OCA mailing list, and you can ask if someone is ready to review your upgraded module and make testing on it." This actually is not really the way most modules are migrated - people usually do not announce their PR in mailing list. Instead they may mention (through @ in comments) the maintainer(s) of the module/repository to draw their attention.
*) One more think you could have done (and is a good practice) is mentioning your PR in the comments of "Migration to version XX.0" - in your case https://github.com/OCA/product-attribute/issues/1446
One more thing you may decide to include into your article and/or realize yourself: In your email you mention "you succeeded after a huge effort" and your "successful pull request". So far you have succeeded partially only - your PR passes required automated tests which is absolute necessity for it to be considered worth merging. You do not yet have enough approvals (you actually have none so far) and the required time limit has not been reached after that. I can't quickly find the document that describes this. Only after you gather enough (2 I think) approvals and that time limit passes the PR can be merged and considered successfull.
So I'd suggest working the additional steps till you reach the end of the process for your blog post (and first migration) to be complete.
Best luck and regards
Radovan Skolnik
On utorok 13. augusta 2024 16:17:08 CEST mohamed alkobrosly wrote:
> Here is my experience with my first contribution to OCA:
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [1] I hope it will be useful to the new contributors.
> Thanks all,
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [2]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [3]
>
>
>
> [1]
> https://blog.kobros-tech.com/2024/08/highlights-on-my-contributions-to-odoo
> .html [2] https://odoo-community.org/groups/contributors-15
> [3] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 04:50 - 13 Aug 2024
-
