Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
Re: Help promoting the OCA
Hi Radovan,
Thanks for your email. Noted.
Habit, but fault. While, I disagree with your point entirely, for ease of argument, I will refrain in the future.
Thanks, have a good week.
Kind regards,
Jordan Kinsella
Head of Marketing | Gravitai
jordan@gravitai.com | +44 (0) 1233 801 330
314 Regents Park Road, Finchley, London N3 2LT
www.gravitai.com
Support | hello@gravitai.com
----
CONFIDENTIAL: Within this email, any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify the sender. This message contains confidential information and is intended only for the individual(s) named. If you are not the named addressee, you should not disclose, distribute or copy this email. Please notify the sender immediately by email if you have received this email by mistake and delete this email from your system. If you are not the intended recipient, you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. For more information on how we operate and deal with your data, please visit our website to have a look at our Privacy Policy and Terms & Conditions pages.
WARNING: Whilst we run antivirus software on all internet emails, we are not liable for any loss or damage. The recipient is advised to run their own antivirus software while operating and viewing emails directed at them from Gravitai.
From: Radovan Skolnik <notifications@odoo-community.org>
Sent: 22 October 2024 12:47
To: Contributors <contributors@odoo-community.org>
Subject: Re: Help promoting the OCACaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your Department Manager
Jordan,
while I like your enthusiasm I would ask you (if there's not a opposite opinion) not to add reactions to mailing lists - this is not Facebook or LinkedIn. It pollutes the mailing list with emails that really do not bring any additional value. This is a sample of the last one that was sent to all subscribers:
Hope you understand. Thank you.
Best regards
Radovan Skolnik
On utorok 22. októbra 2024 12:13:08 CEST Jordan Kinsella wrote:
> Jordan Kinsella
> reacted to your message:
>
>
>
>
>
>
> *From:* Michel Stroom <notifications@odoo-community.org>
> *Sent:* Tuesday, October 22, 2024 9:52:38 AM
> *To:* Contributors <contributors@odoo-community.org>
> *Subject:* Help promoting the OCA
>
>
>
>
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, contact your Department Manager
>
>
>
>
>
> Hi OCA members and fellow Odooers,
>
> I wasn’t able to attend the recent OCA Days in Liège, so I began watching
> the videos online. One of them highlighted the need for more OCA members.
>
> Since then, I’ve made it a daily routine to watch one OCA video each morning
> and share my thoughts on LinkedIn, encouraging readers to consider applying
> for membership.
>
> This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project."
> In my opinion, it’s a must-see for anyone involved in selling Odoo.
>
>
> Read my latest post on LinkedIn and click the link below:
> https://tinyurl.com/ytndcmst
>
> I hope this inspires more people to write about the OCA.
> Feel free to reach out if you need help creating content.
>
> Best regards,
>
>
>
> Michel Stroom
> LinkedIn: https://linkedin.com/in/stroom
>
>
>
>
> _______________________________________________
> 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]
>
>
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [3]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
> [3] https://odoo-community.org/groups/contributors-15
> [4] 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 Jordan Kinsella - 02:06 - 22 Oct 2024 -
Re: Help promoting the OCA
Jordan,
while I like your enthusiasm I would ask you (if there's not a opposite opinion) not to add reactions to mailing lists - this is not Facebook or LinkedIn. It pollutes the mailing list with emails that really do not bring any additional value. This is a sample of the last one that was sent to all subscribers:
Hope you understand. Thank you.
Best regards
Radovan Skolnik
On utorok 22. októbra 2024 12:13:08 CEST Jordan Kinsella wrote:
> Jordan Kinsella
> reacted to your message:
>
>
>
>
>
>
> *From:* Michel Stroom <notifications@odoo-community.org>
> *Sent:* Tuesday, October 22, 2024 9:52:38 AM
> *To:* Contributors <contributors@odoo-community.org>
> *Subject:* Help promoting the OCA
>
>
>
>
> Caution: This is an external email. Please take care when clicking links or
> opening attachments. When in doubt, contact your Department Manager
>
>
>
>
>
> Hi OCA members and fellow Odooers,
>
> I wasn’t able to attend the recent OCA Days in Liège, so I began watching
> the videos online. One of them highlighted the need for more OCA members.
>
> Since then, I’ve made it a daily routine to watch one OCA video each morning
> and share my thoughts on LinkedIn, encouraging readers to consider applying
> for membership.
>
> This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project."
> In my opinion, it’s a must-see for anyone involved in selling Odoo.
>
>
> Read my latest post on LinkedIn and click the link below:
> https://tinyurl.com/ytndcmst
>
> I hope this inspires more people to write about the OCA.
> Feel free to reach out if you need help creating content.
>
> Best regards,
>
>
>
> Michel Stroom
> LinkedIn: https://linkedin.com/in/stroom
>
>
>
>
> _______________________________________________
> 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]
>
>
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [3]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
> [3] https://odoo-community.org/groups/contributors-15
> [4] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 01:45 - 22 Oct 2024 -
Re: Help promoting the OCA
Hello Michel,Thanks a lot for your help here, it is very appreciated!There is currently no "marketing" working group in the community but as you suggested, we will create one to coordinate those kind of initiatives. In parallel, we will need to improve the "new member journey" as well (and the contributor's journey afterwards).For those reading this message, if you want to join as well, let me know by emailing me directly (do not reply to the whole mailing list):Best regards,Le mar. 22 oct. 2024 à 11:52, Michel Stroom <notifications@odoo-community.org> a écrit :Hi OCA members and fellow Odooers,I wasn’t able to attend the recent OCA Days in Liège, so I began watching the videos online. One of them highlighted the need for more OCA members.
Since then, I’ve made it a daily routine to watch one OCA video each morning and share my thoughts on LinkedIn, encouraging readers to consider applying for membership.
This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project." In my opinion, it’s a must-see for anyone involved in selling Odoo.Read my latest post on LinkedIn and click the link below:
I hope this inspires more people to write about the OCA.Feel free to reach out if you need help creating content.Best regards,_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf - 01:45 - 22 Oct 2024 -
RE: Help promoting the OCA
Jordan Kinsella reacted to your message:
From: Michel Stroom <notifications@odoo-community.org>
Sent: Tuesday, October 22, 2024 9:52:38 AM
To: Contributors <contributors@odoo-community.org>
Subject: Help promoting the OCACaution: This is an external email. Please take care when clicking links or opening attachments. When in doubt, contact your Department Manager
Hi OCA members and fellow Odooers,
I wasn’t able to attend the recent OCA Days in Liège, so I began watching the videos online. One of them highlighted the need for more OCA members.
Since then, I’ve made it a daily routine to watch one OCA video each morning and share my thoughts on LinkedIn, encouraging readers to consider applying for membership.
This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project." In my opinion, it’s a must-see for anyone involved in selling Odoo.
Read my latest post on LinkedIn and click the link below:https://tinyurl.com/ytndcmst
I hope this inspires more people to write about the OCA.Feel free to reach out if you need help creating content.
Best regards,
Michel StroomLinkedIn: https://linkedin.com/in/stroom
_______________________________________________
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 - 12:11 - 22 Oct 2024 -
Help promoting the OCA
Hi OCA members and fellow Odooers,I wasn’t able to attend the recent OCA Days in Liège, so I began watching the videos online. One of them highlighted the need for more OCA members.
Since then, I’ve made it a daily routine to watch one OCA video each morning and share my thoughts on LinkedIn, encouraging readers to consider applying for membership.
This morning, I posted Gonzalo Ruzafa talk, "How to Sell an Odoo Project." In my opinion, it’s a must-see for anyone involved in selling Odoo.Read my latest post on LinkedIn and click the link below:https://tinyurl.com/ytndcmst
I hope this inspires more people to write about the OCA.Feel free to reach out if you need help creating content.Best regards,Michel StroomLinkedIn: https://linkedin.com/in/stroom
by Michel Stroom - 11:50 - 22 Oct 2024 -
Re: Invoicing addresses
I experimented with it some time ago, but I’m sure someone from my team has worked on a similar scenario more recently. I’ll check with the team at the office tomorrow.On 10/20/2024 3:52 PM Aymerick G. <notifications@odoo-community.org> wrote:
Have you tried the standard setting « service subcontractor » ? I know it was the in V15. It’d like an MTO but for services.
Aymerick Glowacki
Le dim. 20 oct. 2024 à 10:42, Jorge Elena Poblet <notifications@odoo-community.org> a écrit :
There are several OCA modules that may help automate part of the invoicing logic you're seeking, although a completely packaged solution for splitting invoices in the exact scenario you described might not be available. One useful module is from the OCA’s account-invoice-reporting repository, which offers addons to enhance invoice reporting. These modules can help manage and automate aspects of invoice handling, like grouping invoice lines by picking, managing sales line positions, and showing specific data points like due dates or serial numbers in invoices.
To address your specific case you might need to look into customizing Odoo with logic to split invoicing based on the type of service or product provided.
Good luck!On 10/20/2024 1:47 PM Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT <notifications@odoo-community.org> wrote:
Dear Community,
i do have a use case, where the following scenario should be covered.
Company A (using odoo) is a subcontractor of Company B. Company B is handing over work to Company A to perform some service (lets say Product “Service on behalf of Company B”) for Customer X.
Company A is performing the service @Customer X and also sells some items to Customer X.
When Company A is creating an invoice, the invoice for “Service on behalf of Company B” should be addressed to company A, while the sold items should be invoiced to Customer X.
Is any body aware of a solution, that covers this scenario and automating this logic? Separating this manually can be pretty time consuming.
All the best
Nils
_______________________________________________
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 Jorge Elena Poblet - 05:11 - 20 Oct 2024 -
Re: Invoicing addresses
Have you tried the standard setting « service subcontractor » ? I know it was the in V15. It’d like an MTO but for services.Aymerick GlowackiLe dim. 20 oct. 2024 à 10:42, Jorge Elena Poblet <notifications@odoo-community.org> a écrit :There are several OCA modules that may help automate part of the invoicing logic you're seeking, although a completely packaged solution for splitting invoices in the exact scenario you described might not be available. One useful module is from the OCA’s account-invoice-reporting repository, which offers addons to enhance invoice reporting. These modules can help manage and automate aspects of invoice handling, like grouping invoice lines by picking, managing sales line positions, and showing specific data points like due dates or serial numbers in invoices.
To address your specific case you might need to look into customizing Odoo with logic to split invoicing based on the type of service or product provided.
Good luck!On 10/20/2024 1:47 PM Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT <notifications@odoo-community.org> wrote:
Dear Community,
i do have a use case, where the following scenario should be covered.
Company A (using odoo) is a subcontractor of Company B. Company B is handing over work to Company A to perform some service (lets say Product “Service on behalf of Company B”) for Customer X.
Company A is performing the service @Customer X and also sells some items to Customer X.
When Company A is creating an invoice, the invoice for “Service on behalf of Company B” should be addressed to company A, while the sold items should be invoiced to Customer X.
Is any body aware of a solution, that covers this scenario and automating this logic? Separating this manually can be pretty time consuming.
All the best
Nils
_______________________________________________
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 glowacki.aymerick - 04:51 - 20 Oct 2024 -
Re: Invoicing addresses
There are several OCA modules that may help automate part of the invoicing logic you're seeking, although a completely packaged solution for splitting invoices in the exact scenario you described might not be available. One useful module is from the OCA’s account-invoice-reporting repository, which offers addons to enhance invoice reporting. These modules can help manage and automate aspects of invoice handling, like grouping invoice lines by picking, managing sales line positions, and showing specific data points like due dates or serial numbers in invoices.
To address your specific case you might need to look into customizing Odoo with logic to split invoicing based on the type of service or product provided.
Good luck!On 10/20/2024 1:47 PM Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT <notifications@odoo-community.org> wrote:
Dear Community,
i do have a use case, where the following scenario should be covered.
Company A (using odoo) is a subcontractor of Company B. Company B is handing over work to Company A to perform some service (lets say Product “Service on behalf of Company B”) for Customer X.
Company A is performing the service @Customer X and also sells some items to Customer X.
When Company A is creating an invoice, the invoice for “Service on behalf of Company B” should be addressed to company A, while the sold items should be invoiced to Customer X.
Is any body aware of a solution, that covers this scenario and automating this logic? Separating this manually can be pretty time consuming.
All the best
Nils
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Jorge Elena Poblet - 04:40 - 20 Oct 2024 -
Invoicing addresses
Dear Community,
i do have a use case, where the following scenario should be covered.
Company A (using odoo) is a subcontractor of Company B. Company B is handing over work to Company A to perform some service (lets say Product “Service on behalf of Company B”) for Customer X.
Company A is performing the service @Customer X and also sells some items to Customer X.
When Company A is creating an invoice, the invoice for “Service on behalf of Company B” should be addressed to company A, while the sold items should be invoiced to Customer X.
Is any body aware of a solution, that covers this scenario and automating this logic? Separating this manually can be pretty time consuming.
All the best
Nils
by Nils Coenen - 02:46 - 20 Oct 2024 -
Re: [14.0] Change warehouse and location on picking
Sorry for bottom posting but actually another thing I don't understand is:when I choose a different "Destination Location" and apply with "SELECT ALL" I don't see any Destination change on stock move lines, but the value is correctly retrieved if I open the wizard. How is it possible?Il giorno ven 18 ott 2024 alle ore 19:17 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:Hi,We have a customer who needs to change the warehouse and destination location for some incoming pickings.Can this be done manually? I'm watching for this module which has an opened PR for odoo14 https://github.com/OCA/stock-logistics-workflow/pull/1668but I don't understand some of modules restrictions, maybe I've misunderstood the purpose of this module.The part I don't understand is the domain of `new_location_dest_id` field : is there any important reason for the New Location Destination to be restricted as child of "location_dest_id" ?Do you suggest other modules to achieve this goal?Thank you as always for your help--Francesco Ballerini
by Francesco Ballerini - 08:31 - 18 Oct 2024 -
[14.0] Change warehouse and location on picking
Hi,We have a customer who needs to change the warehouse and destination location for some incoming pickings.Can this be done manually? I'm watching for this module which has an opened PR for odoo14 https://github.com/OCA/stock-logistics-workflow/pull/1668but I don't understand some of modules restrictions, maybe I've misunderstood the purpose of this module.The part I don't understand is the domain of `new_location_dest_id` field : is there any important reason for the New Location Destination to be restricted as child of "location_dest_id" ?Do you suggest other modules to achieve this goal?Thank you as always for your help--Francesco Ballerini
by Francesco Ballerini - 07:21 - 18 Oct 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: [16.0] how to deal with locked journal items with wrong currency
Looks interesting, thank U. I'll check it out. On 10/18/24 02:13, Pedro M. Baeza wrote: > Isn't this patch what you need? > https://github.com/OCA/account-financial-reporting/pull/1232 > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
by Ing. Rolando Pérez Rebollo - 02: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: [16.0] how to deal with locked journal items with wrong currency
Isn't this patch what you need? https://github.com/OCA/account-financial-reporting/pull/1232Regards.
by Pedro M. Baeza - 08: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_______________________________________________
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_______________________________________________
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 -
Re: Manage Product Recall
Le jeudi 17 octobre 2024, 11:32:24 CEST Holger Brunn a écrit : > > price and other fields. With this module, it is not necessary, right ? > > exactly, it's very versatile. All kudos to https://github.com/legalsylvain > for coming up with this in the first place Anyway, thanks for the tip! Have a good day
by "Xavier Brochard" <zaz@chezlesenfants.fr> - 11:45 - 17 Oct 2024 -
Re: Manage Product Recall
> price and other fields. With this module, it is not necessary, right ? exactly, it's very versatile. All kudos to https://github.com/legalsylvain for coming up with this in the first place
by "Holger Brunn" <holger@brunn.email> - 11:31 - 17 Oct 2024