Archives
Contributors
-
Re: Laboratory Information Management System (LIMS)
I won't be going to Belgium this year... 😢
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
De: Cyril VINH-TUNG <notifications@odoo-community.org>
Enviado: viernes, 29 de agosto de 2025 12:11 p. m.
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Laboratory Information Management System (LIMS)Hi Max
As you might know, I have a 10 years experience in LIMS market in France ;-)
Actually, the market is almost trusted by a unique very big medical company (www.dedalus.com).An opensource project would be a revolution indeed... but there's a looooot of work.I remember a talk at OXP2024, but it looked very 'vertical' and closed https://www.odoo.com/event/odoo-experience-2024-4662/track/where-labs-meet-their-match-introducing-the-first-fully-integrated-lims-in-odoo-6720
I know a guy (one of my employees in that life) who would be a killer on that project but he just join Centreon Company...
Let's discuss that at Liège Sunday eve ?
Cheers
--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.com
Le jeu. 28 août 2025, 11:46, Maxime Chambreuil <notifications@odoo-community.org> a écrit :
Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Maxime Chambreuil - 12:16 - 30 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe ven. 29 août 2025, 08:29, Cyril VINH-TUNG <cyril@invitu.com> a écrit :Hi @Graeme 'laboratory' is too wide, it can be a laboratory outside medicalAFAIK in Europe, LIMS is specific to biological analysis...And even with that denomination, we have at least 3 sub-markets (industrial, public labs like in hospitals, private labs outside hospitals...)And of course, those 3 submarkets have very different needs !!!My2cents--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe ven. 29 août 2025, 08:22, Graeme Gellatly <notifications@odoo-community.org> a écrit :I would prefer to call it laboratory, only reason is lims means something completely different in my industry. But I don't really care, just making point that abbreviations are often vertical specificLe ven. 29 août 2025, 22:27, Roussel, Denis <notifications@odoo-community.org> a écrit :Great!Agree with Pedro, simpler is better.Le ven. 29 août 2025 à 09:11, Pedro M. Baeza <notifications@odoo-community.org> a écrit :About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?_______________________________________________
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 Cyril VINH-TUNG - 08:36 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Hi @Graeme 'laboratory' is too wide, it can be a laboratory outside medicalAFAIK in Europe, LIMS is specific to biological analysis...And even with that denomination, we have at least 3 sub-markets (industrial, public labs like in hospitals, private labs outside hospitals...)And of course, those 3 submarkets have very different needs !!!My2cents--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe ven. 29 août 2025, 08:22, Graeme Gellatly <notifications@odoo-community.org> a écrit :I would prefer to call it laboratory, only reason is lims means something completely different in my industry. But I don't really care, just making point that abbreviations are often vertical specificLe ven. 29 août 2025, 22:27, Roussel, Denis <notifications@odoo-community.org> a écrit :Great!Agree with Pedro, simpler is better.Le ven. 29 août 2025 à 09:11, Pedro M. Baeza <notifications@odoo-community.org> a écrit :About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?_______________________________________________
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 Cyril VINH-TUNG - 08:31 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
I would prefer to call it laboratory, only reason is lims means something completely different in my industry. But I don't really care, just making point that abbreviations are often vertical specificLe ven. 29 août 2025, 22:27, Roussel, Denis <notifications@odoo-community.org> a écrit :Great!Agree with Pedro, simpler is better.Le ven. 29 août 2025 à 09:11, Pedro M. Baeza <notifications@odoo-community.org> a écrit :About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?_______________________________________________
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 - 08:21 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Hi MaxAs you might know, I have a 10 years experience in LIMS market in France ;-)Actually, the market is almost trusted by a unique very big medical company (www.dedalus.com).An opensource project would be a revolution indeed... but there's a looooot of work.I remember a talk at OXP2024, but it looked very 'vertical' and closed https://www.odoo.com/event/odoo-experience-2024-4662/track/where-labs-meet-their-match-introducing-the-first-fully-integrated-lims-in-odoo-6720I know a guy (one of my employees in that life) who would be a killer on that project but he just join Centreon Company...Let's discuss that at Liège Sunday eve ?Cheers--------------------------------
Cyril VINH-TUNG
INVITU
Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99
contact@invitu.comLe jeu. 28 août 2025, 11:46, Maxime Chambreuil <notifications@odoo-community.org> a écrit :Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
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 - 08:11 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Thank you Enric!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
De: Enric Tobella Alomar <notifications@odoo-community.org>
Enviado: jueves, 28 de agosto de 2025 11:51 p. m.
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Laboratory Information Management System (LIMS)Hi Max,
Some years ago we made a proof of concept based on existent LIMS OpenSource software (SEINATE)
It has a lot of work to do yet, but it can be used as a base. It is 13, but could be migrated easily.
It would be nice to review it from a medical perspective too. We have a medical vertical that would help on that topic (at least partially) in order to know how the structure should go and reuse code. From an standard perspective: https://hl7.org/fhir/diagnosticreport.html
We have the modules for that. It is just necessary to get some of the code in order to fill some of the gaps of the PoC. For example, the medical modules has a complete reporting enginge that would allow to make nice reports easily.
One last topic is the integration with external machines. We did a PoC too based two protocols (HL7v2 and ASTM if I remember properly)
Contact me if you need some more information.
El jue, 28 ago 2025 a las 23:46, Maxime Chambreuil (<notifications@odoo-community.org>) escribió:
Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Enric Tobella AlomarCEO & Founder
_______________________________________________
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 - 04:51 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
ok, works for me!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
De: Pedro M. Baeza <notifications@odoo-community.org>
Enviado: viernes, 29 de agosto de 2025 1:11 a. m.
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Laboratory Information Management System (LIMS)About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?_______________________________________________
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 - 04:51 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Hey Maxime,I’m definitely interested in the topic of LIMS.
Some time ago, I had already started an approach focusing on geochemical analyses for isotope ratio measurements. Unfortunately, for several reasons, we had to stop the project back then.If you’re starting this initiative, I’ll certainly follow the repository. And if there’s any way I can contribute, I’d be happy to add my two cents as well. Should any discussions come up, please don’t hesitate to reach out to me.
All the bestNils
Von: Maxime Chambreuil <notifications@odoo-community.org>
Gesendet: Thursday, August 28, 2025 11:47:01 PM
An: Contributors <contributors@odoo-community.org>
Betreff: Laboratory Information Management System (LIMS)ACHTUNG! Diese E-Mail stammt von außerhalb der Organisation. Klicken Sie nicht auf Links und öffnen Sie keine Anhänge, es sei denn, Sie kennen den Absender und wissen, dass der Inhalt sicher ist.
Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 02:21 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Great!Agree with Pedro, simpler is better.Le ven. 29 août 2025 à 09:11, Pedro M. Baeza <notifications@odoo-community.org> a écrit :About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel - 12:26 - 29 Aug 2025 -
Multi-Company + Website Issue
Hi everyone,I'm reaching out to get some insights from the community on a multi-company scenario we're running into with Odoo.The Issue:We have a setup where multiple companies share the same website. Odoo currently ties a website to a single company, which is fine for pricing (we use GeoIP to show region-specific pricelists). But when a customer places an order, Odoo assigns that order to the company linked to the website, not necessarily the customer's regional company.Example:A US customer sees US pricing, but the order still gets created under the LATAM company because that's how the website is configured. This leads to accounting and operational misalignment.Any guidance, existing OCA modules, or suggestions on how to approach this would be greatly appreciated. If there's interest, I'd also be happy to help spec out a solution we will contribute back to the community.Best regards,
Jorge Elena Poblet
Founder & CEO
Binhex
j.elena@binhex.cloud
Office (Spain) : +34 622 40 08 08
Office (USA): +1 561 403 4406Offices:
Miami | 8325 NE 2nd Ave, Miami, FL 33138, United States
Texas | 27027 Westheimer Pkwy Katy, TX 77494, United States
Tenerife | Street Subida al Mayorazgo, 13, Office 15-2
Las Palmas | Edificio Polivalente IV Campus de Tafira Parque Tecnológico de Gran Canaria
Start for free: Try Odoo Community in the cloud This email is confidential and intended only for the recipient. If you are not the intended recipient, please notify the sender and delete it immediately.
Privacy Policy
by Jorge Elena Poblet - 10:41 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
About renaming the repository, why not call it directly "lims" instead of "vertical-lims"?
by Pedro M. Baeza - 09:11 - 29 Aug 2025 -
Re: Laboratory Information Management System (LIMS)
Hi Max,Some years ago we made a proof of concept based on existent LIMS OpenSource software (SEINATE)It has a lot of work to do yet, but it can be used as a base. It is 13, but could be migrated easily.It would be nice to review it from a medical perspective too. We have a medical vertical that would help on that topic (at least partially) in order to know how the structure should go and reuse code. From an standard perspective: https://hl7.org/fhir/diagnosticreport.htmlWe have the modules for that. It is just necessary to get some of the code in order to fill some of the gaps of the PoC. For example, the medical modules has a complete reporting enginge that would allow to make nice reports easily.One last topic is the integration with external machines. We did a PoC too based two protocols (HL7v2 and ASTM if I remember properly)Contact me if you need some more information.El jue, 28 ago 2025 a las 23:46, Maxime Chambreuil (<notifications@odoo-community.org>) escribió:Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 07:51 - 29 Aug 2025 -
Re: Stock location state
Hi Maxime,Le jeu. 28 août 2025 à 23:37, Maxime Chambreuil <notifications@odoo-community.org> a écrit :Hello everyone,
I am using Odoo 18 and the inventory module to manage a stock of products stored in bulk in silos.
The requirement is about having a state on the stock location (empty, full, filling, empyting) and keeping the logs of the state changes, including the timestamp of when the filling/empyting starts and stops.
Do we have a solution for this? In previous versions?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Denis Roussel - 07:36 - 29 Aug 2025 -
Laboratory Information Management System (LIMS)
Hello,
We have the opportunity to start developing a basic LIMS module and its extensions within the OCA with 2 customers.
Since https://github.com/OCA/connector-lims seems to be empty and not used, I would like to rename it to "vertical-lims" and start documenting our effort there.
What do you think? Anyone interested?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
by Maxime Chambreuil - 11:45 - 28 Aug 2025 -
Stock location state
Hello everyone,
I am using Odoo 18 and the inventory module to manage a stock of products stored in bulk in silos.
The requirement is about having a state on the stock location (empty, full, filling, empyting) and keeping the logs of the state changes, including the timestamp of when the filling/empyting starts and stops.
Do we have a solution for this? In previous versions?
Thank you!
MAXIME CHAMBREUIL
DIRECTOR INTERNACIONALT: +52 (800) 953-2012 #5200
M: +52 (442) 114-9164 | WhatsApp
C: MChambreuil@OpenSourceIntegrators.comAv. Antea 1032, Piso 4 Local 8, Colonia Jurica
Santiago de Querétaro, Querétaro, 76100, México
Analizar. Optimizar. Automatizar. Transicionar.
by Maxime Chambreuil - 11:34 - 28 Aug 2025 -
Re: Adding Job Dependency support in o13 queue_job module?
Hi,if you do not find any other option, we can port it for you. Drop me an email if needed.Best regardsRadovan SkolnikOn Aug 26, 2025 18:21, Gilbert Gagnon <notifications@odoo-community.org> wrote:Dear contributors of the queue_job (v13.0) module,We are utilizing the Job Queue module in Odoo 13 to fulfill our asynchronous processing requirements. However, we have recently encountered a situation where we require support for Job Dependency.It appears that job dependency support was only introduced in the Job Queue starting from Odoo 14, however currently, we are unable to migrate to a higher version of Odoo immediately and are seeking Job Dependency support within Odoo 13.
If it is feasible for you to backport Job Dependency support from Odoo 14 to Odoo 13, that would represent the optimal solution for our needs?
Alternatively, we could consider modifying the Odoo 13 Job Queue code to incorporate Job Dependency ourselves, potentially using the same syntax as Odoo 14, however if we have to do it ourselves would you have any advice for us that would help, ex. was there a technical reason you started at v14, or you just had to start somewhere?
Any help would be greatly appreciated, thank you!
Gilbert GagnonTechnology Leader | Leader technologique
gilbertg@blackwaretech.com
888.228.5755
Blackware Technologies | www.blackwaretech.com
Le présent courriel, incluant tout fichier qui y est joint, est envoyé à l’intention exclusive de son destinataire et est confidentiel. Si vous recevez ce courriel par erreur, notez que vous ne devez ni l’utiliser, ni le divulguer, ni le distribuer, ni le copier et tout fichier qui y est joint, ni vous en servir à quelque fin que ce soit. Merci d’en aviser l’expéditeur par courriel et de supprimer ce courriel ainsi que tout fichier joint.------------The information, including any attached file, transmitted by this email is intended only for the person to which it is addressed and is confidential. If you have received this email by mistake, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this email or the attached file is strictly prohibited. Please contact the sender and delete the email and any attached file._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 06:51 - 26 Aug 2025 -
Re: Adding Job Dependency support in o13 queue_job module?
Hi,You have two options:1- Make the migration yourself (You can try to cherry-pick the changes and check if everything works fine)2- Pay a major contributor for doing this and ensuring that everything works perfectly.Just to be clear, the change was made on 12 and ported to 14, but it was never ported to 13. It shouldn't be a problem to do that.Kind regards,El mar, 26 ago 2025 a las 18:21, Gilbert Gagnon (<notifications@odoo-community.org>) escribió:Dear contributors of the queue_job (v13.0) module,We are utilizing the Job Queue module in Odoo 13 to fulfill our asynchronous processing requirements. However, we have recently encountered a situation where we require support for Job Dependency.
It appears that job dependency support was only introduced in the Job Queue starting from Odoo 14, however currently, we are unable to migrate to a higher version of Odoo immediately and are seeking Job Dependency support within Odoo 13.
If it is feasible for you to backport Job Dependency support from Odoo 14 to Odoo 13, that would represent the optimal solution for our needs?
Alternatively, we could consider modifying the Odoo 13 Job Queue code to incorporate Job Dependency ourselves, potentially using the same syntax as Odoo 14, however if we have to do it ourselves would you have any advice for us that would help, ex. was there a technical reason you started at v14, or you just had to start somewhere?
Any help would be greatly appreciated, thank you!Gilbert GagnonTechnology Leader | Leader technologique
gilbertg@blackwaretech.com
888.228.5755
Blackware Technologies | www.blackwaretech.com
Le présent courriel, incluant tout fichier qui y est joint, est envoyé à l’intention exclusive de son destinataire et est confidentiel. Si vous recevez ce courriel par erreur, notez que vous ne devez ni l’utiliser, ni le divulguer, ni le distribuer, ni le copier et tout fichier qui y est joint, ni vous en servir à quelque fin que ce soit. Merci d’en aviser l’expéditeur par courriel et de supprimer ce courriel ainsi que tout fichier joint.------------The information, including any attached file, transmitted by this email is intended only for the person to which it is addressed and is confidential. If you have received this email by mistake, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this email or the attached file is strictly prohibited. Please contact the sender and delete the email and any attached file._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Enric Tobella AlomarCEO & Founder
by Enric Tobella Alomar - 06:35 - 26 Aug 2025 -
Adding Job Dependency support in o13 queue_job module?
Dear contributors of the queue_job (v13.0) module,We are utilizing the Job Queue module in Odoo 13 to fulfill our asynchronous processing requirements. However, we have recently encountered a situation where we require support for Job Dependency.It appears that job dependency support was only introduced in the Job Queue starting from Odoo 14, however currently, we are unable to migrate to a higher version of Odoo immediately and are seeking Job Dependency support within Odoo 13.
If it is feasible for you to backport Job Dependency support from Odoo 14 to Odoo 13, that would represent the optimal solution for our needs?
Alternatively, we could consider modifying the Odoo 13 Job Queue code to incorporate Job Dependency ourselves, potentially using the same syntax as Odoo 14, however if we have to do it ourselves would you have any advice for us that would help, ex. was there a technical reason you started at v14, or you just had to start somewhere?
Any help would be greatly appreciated, thank you!Gilbert GagnonTechnology Leader | Leader technologique
gilbertg@blackwaretech.com
888.228.5755
Blackware Technologies | www.blackwaretech.com
Le présent courriel, incluant tout fichier qui y est joint, est envoyé à l’intention exclusive de son destinataire et est confidentiel. Si vous recevez ce courriel par erreur, notez que vous ne devez ni l’utiliser, ni le divulguer, ni le distribuer, ni le copier et tout fichier qui y est joint, ni vous en servir à quelque fin que ce soit. Merci d’en aviser l’expéditeur par courriel et de supprimer ce courriel ainsi que tout fichier joint.------------The information, including any attached file, transmitted by this email is intended only for the person to which it is addressed and is confidential. If you have received this email by mistake, be aware that any use, review, retransmission, distribution, reproduction or any action taken in reliance upon this email or the attached file is strictly prohibited. Please contact the sender and delete the email and any attached file.
by "Gilbert Gagnon" <gilbertg@blackwaretech.com> - 06:21 - 26 Aug 2025 -
Re: Odoo 18
The discount in purchase orders is now native, so no need of that module.Regards.
by Pedro M. Baeza - 12:06 - 26 Aug 2025 -
Odoo 18
Hello everyone,
will there be an upgrade to Odoo 18 for the purchase_discount module?
Please do not hesitate to contact us if you have any questions.
With kind regards
Martin Bando
Computer Science Expert - Software Development | OPAL Solutions GmbH
martin.bando@opal-solutions.de | https://opal-solutions.de
Niederlassung Bochum | T +49 (0) 23460140231
Technische Probleme?:
Schreiben Sie direkt eine Email an helpdesk@opal-solutions.de.
Hauptsitz Rheinland | Karl-Heinz-Beckurts-Straße 13 | 52428 Jülich
Niederlassung Ruhrgebiet/Sauerland | Heinrichstraße 67 | 44805 Bochum
Niederlassung Münster/Osnabrück | Gewerbepark 18 | 49143 Bissendorf
T +49 (0)2461 9169 960 | F +49 (0)2461 9169 969
Amtsgericht Düren | HRB 5889 | Geschäftsführung: Michael von Steht, Frank Stechel
OPAL Solutions GmbH ist ein Unternehmen der OPAL Associates Holding AGAGB | Impressum | Informationen zum Datenschutz
Follow us on
WICHTIGE MITTEILUNG
Diese E-Mail und deren Anlagen enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. Das unerlaubte Kopieren, sowie die unbefugte Weitergabe dieser E-Mail und deren Anlagen sind nicht gestattet. OPAL haftet nicht für Schäden, die durch den unerlaubten Gebrauch dieser E-Mail und deren Anlagen entstehen.
IMPORTANT MESSAGE
This e-mail and their attachments may contain confidential and / or privileged information. If you are not the intended recipient or have received this email in error, please notify the sender immediately and destroy this e-mail. Unauthorized copying and unauthorized distribution of this e-mail and their attachments are not allowed. OPAL is not liable for damages caused by unauthorized use of this e-mail and attachments.
by Martin Bando - 12:01 - 26 Aug 2025
