Contributors

• 1
• 2
• 3
• 4
• 5

• Re: Prepaid Services & Timesheets

  Can an upfront Advance Payment address this?
  
  

  On 01/02/2024 14:31, Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT wrote:
  

  Hi OCA Contributors,

  i was asked, if it is possible to manage prepaid service hours in the following way..

   

  Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.

  If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.

   

  Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…

   

  All the best

  Nils

  Mit freundlichen Grüßen Nils Coenen -------- Nils Coenen Inhaber

  NICO SOLUTIONS - ENGINEERING & IT Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal Tel. +49 (0)4298-4667492

  Website | Map | Email

  Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.

  _______________________________________________
  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 PARTNER

  M: +351 919 991 307
  E: dreis@OpenSourceIntegrators.com
  A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais

  

  ---

  by Daniel Reis - 07:13 - 1 Feb 2024

• Re: Prepaid Services & Timesheets

  Hi Nils,
  

  probably not, no. If your customer starts out with Enterprise Subscription than you might be tied into changing this. But this part underwent substantial changes in Enterprise throughout previous versions.
  

  Best Frederik
  

  Am 01.02.24 um 15:56 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
  

  Hi Frederik,

  thanks for your prompt reply…

  It is quite clear to me, that this is nothing for „hey, lets dattack this right now and it will work tomorrow“.

  I do have an idea of the complexity. But as time is a rare good at the moment… (due to another project ;P) I decided to ask you before approaching anything.

   

  So if this a common need for many users… a proper project seem to make sense…

  As the customer wants to use the enterprise subscription app…. I dont know if contract is the right place to start…

   

  But i´ll start diving into it.

   

  Schöne Grüße aus dem Norden ;P

   

  All the best

  Nils

   

  Von: Graeme Gellatly <notifications@odoo-community.org>
  Antworten an: OCA Contributors <contributors@odoo-community.org>
  Datum: Donnerstag, 1. Februar 2024 um 15:47
  An: OCA Contributors <contributors@odoo-community.org>
  Betreff: Re: Prepaid Services & Timesheets

   

  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.

  Hi Nils,

  afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules. 

  I think that is also a quite common requirement, though differs in detail from service company to service company. 

  Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think). 

  Ususally you proably would start out with something from https://github.com/OCA/contract to build this process. 

  Best Frederik

  Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:

  Hi OCA Contributors,

  i was asked, if it is possible to manage prepaid service hours in the following way..

   

  Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.

  If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.

   

  Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…

   

  All the best

  Nils

  Mit freundlichen Grüßen Nils Coenen -------- Nils Coenen Inhaber

   

  NICO SOLUTIONS - ENGINEERING & IT Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal Tel. +49 (0)4298-4667492

  Website | Map | Email

  Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.

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

  -- 

  Dr.-Ing. Frederik Kramer

  Geschäftsführer

  initOS GmbH

  Innungsstraße 7

  21244 Buchholz i.d.N.

  Tel:   +49 (0) 4181 13503 12

  Fax:   +49 (0) 4181 13503 10

  Mobil: +49 (0) 179 3901819

  Email: frederik.kramer@initos.com

  Internet: www.initos.com

  Geschäftsführung:

  Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

  Sitz der Gesellschaft: Buchholz i.d.N.

  Amtsgericht Tostedt, HRB 205226

  USt-IdNr.: DE815580155

  Steuer-Nr: 15/200/53247

  _______________________________________________
  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
  

  -- 
  Dr.-Ing. Frederik Kramer
  Geschäftsführer
  
  initOS GmbH
  Innungsstraße 7
  21244 Buchholz i.d.N.
  
  Tel:   +49 (0) 4181 13503 12
  Fax:   +49 (0) 4181 13503 10
  Mobil: +49 (0) 179 3901819
  
  Email: frederik.kramer@initos.com
  Internet: www.initos.com
  
  Geschäftsführung:
  Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
  
  Sitz der Gesellschaft: Buchholz i.d.N.
  Amtsgericht Tostedt, HRB 205226
  USt-IdNr.: DE815580155
  Steuer-Nr: 15/200/53247

  ---

  by Frederik Kramer - 04:13 - 1 Feb 2024

• Re: Prepaid Services & Timesheets

  Hi Frederik,

  thanks for your prompt reply…

  It is quite clear to me, that this is nothing for „hey, lets dattack this right now and it will work tomorrow“.

  I do have an idea of the complexity. But as time is a rare good at the moment… (due to another project ;P) I decided to ask you before approaching anything.

   

  So if this a common need for many users… a proper project seem to make sense…

  As the customer wants to use the enterprise subscription app…. I dont know if contract is the right place to start…

   

  But i´ll start diving into it.

   

  Schöne Grüße aus dem Norden ;P

   

  All the best

  Nils

   

  Von: Graeme Gellatly <notifications@odoo-community.org>
  Antworten an: OCA Contributors <contributors@odoo-community.org>
  Datum: Donnerstag, 1. Februar 2024 um 15:47
  An: OCA Contributors <contributors@odoo-community.org>
  Betreff: Re: Prepaid Services & Timesheets

   

  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.

  Hi Nils,

  afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules. 

  I think that is also a quite common requirement, though differs in detail from service company to service company. 

  Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think). 

  Ususally you proably would start out with something from https://github.com/OCA/contract to build this process. 

  Best Frederik

  Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:

  Hi OCA Contributors,

  i was asked, if it is possible to manage prepaid service hours in the following way..

   

  Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.

  If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.

   

  Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…

   

  All the best

  Nils

  Mit freundlichen Grüßen Nils Coenen -------- Nils Coenen Inhaber

   

  NICO SOLUTIONS - ENGINEERING & IT Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal Tel. +49 (0)4298-4667492

  Website | Map | Email

  Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.

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

  -- 
  

  Dr.-Ing. Frederik Kramer
  

  Geschäftsführer
  

  initOS GmbH
  

  Innungsstraße 7
  

  21244 Buchholz i.d.N.
  

  Tel:   +49 (0) 4181 13503 12
  

  Fax:   +49 (0) 4181 13503 10
  

  Mobil: +49 (0) 179 3901819
  

  Email: frederik.kramer@initos.com
  

  Internet: www.initos.com
  

  Geschäftsführung:
  

  Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
  

  Sitz der Gesellschaft: Buchholz i.d.N.
  

  Amtsgericht Tostedt, HRB 205226
  

  USt-IdNr.: DE815580155
  

  Steuer-Nr: 15/200/53247
  

  _______________________________________________
  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 - 03:56 - 1 Feb 2024

• Re: Prepaid Services & Timesheets

  Hi Nils,
  

  afaik exactly such a function doesn't exist so far. I would be interested in something similar though as well / or lets say in expierence how to set that up with a minimal set of additional modules. 

  I think that is also a quite common requirement, though differs in detail from service company to service company. 

  Furthermore you need to consider what type of module to reflect the "recurrency" and the downstream invoice generation (in detail your requirement is more complex than you might think). 

  Ususally you proably would start out with something from https://github.com/OCA/contract to build this process. 

  Best Frederik
  

  Am 01.02.24 um 15:31 schrieb Nils Coenen | NICO SOLUTIONS - ENGINEERING & IT:
  

  Hi OCA Contributors,

  i was asked, if it is possible to manage prepaid service hours in the following way..

   

  Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.

  If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.

   

  Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…

   

  All the best

  Nils

  Mit freundlichen Grüßen Nils Coenen -------- Nils Coenen Inhaber

  NICO SOLUTIONS - ENGINEERING & IT Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal Tel. +49 (0)4298-4667492

  Website | Map | Email

  Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.

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

  -- 
  Dr.-Ing. Frederik Kramer
  Geschäftsführer
  
  initOS GmbH
  Innungsstraße 7
  21244 Buchholz i.d.N.
  
  Tel:   +49 (0) 4181 13503 12
  Fax:   +49 (0) 4181 13503 10
  Mobil: +49 (0) 179 3901819
  
  Email: frederik.kramer@initos.com
  Internet: www.initos.com
  
  Geschäftsführung:
  Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
  
  Sitz der Gesellschaft: Buchholz i.d.N.
  Amtsgericht Tostedt, HRB 205226
  USt-IdNr.: DE815580155
  Steuer-Nr: 15/200/53247

  ---

  by Frederik Kramer - 03:46 - 1 Feb 2024

• Prepaid Services & Timesheets

  Hi OCA Contributors,

  i was asked, if it is possible to manage prepaid service hours in the following way..

   

  Prepaid service is sold on a montly basis. If the sold or more hours are used, then of course it is quite clear and simple.

  If there are non-used hours, they should be transferred to a customer „hours“-account to reflect the non -used hours. As mentioned… After a period of 6 month, the non-used hours should be dropped from the „hours“-account.

   

  Does somebody tackled this kind of issue already? I would start digging now. If someone was facing a similar issue, it would be great to push me into the right direction…

   

  All the best

  Nils

  Mit freundlichen Grüßen Nils Coenen -------- Nils Coenen Inhaber

  NICO SOLUTIONS - ENGINEERING & IT Dr.-Ruckert-Str. 1G | DE 28865 Lilienthal Tel. +49 (0)4298-4667492

  Website | Map | Email

  Confidentiality Note: This email may contain confidential and/or private information. If you received this email in error please delete and notify sender.

  ---

  by Nils Coenen - 03:31 - 1 Feb 2024

• RE: New Odoo17 translated fields

  Thank you Silvio, I didn’t know this way also -) I’ll try this to.

   

  With kind regards,

   

  Van Hirtum Johan

   

  Van: Silvio Gregorini [mailto:notifications@odoo-community.org]
  Verzonden: donderdag 1 februari 2024 14:08
  Aan: Contributors
  Onderwerp: Re: New Odoo17 translated fields

   

  Since v16, there's also a method made available by the ORM to update translations without overriding the context:

   

  https://github.com/odoo/odoo/blob/ef00294e7189359c47638c4a71626f1937395edb/odoo/models.py#L3465

   

  On Thu, Feb 1, 2024 at 1:52 PM Johan Van Hirtum <notifications@odoo-community.org> wrote:

  Beautiful ! Thank you very much David -)

   

  With kind regards,

   

  Van Hirtum Johan

   

  Van: David Vidal [mailto:notifications@odoo-community.org]
  Verzonden: donderdag 1 februari 2024 13:08
  Aan: Contributors
  Onderwerp: Re: New Odoo17 translated fields

   

  The ORM does it for you. Simply use the `lang` context:

   

  ```python

  record.with_context(lang='es_ES`).field_name = translated_string

  ```

   

  You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

   

  El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

  Dears,

   

  Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

  I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

   

  Thanks for helping me out.

   

  With kind regards,

   

   

  Van Hirtum Johan

  _______________________________________________
  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 johan - 02:35 - 1 Feb 2024

• Re: New Odoo17 translated fields

  Since v16, there's also a method made available by the ORM to update translations without overriding the context:

  
  

  https://github.com/odoo/odoo/blob/ef00294e7189359c47638c4a71626f1937395edb/odoo/models.py#L3465

  
  

  On Thu, Feb 1, 2024 at 1:52 PM Johan Van Hirtum <notifications@odoo-community.org> wrote:
  

  Beautiful ! Thank you very much David -)

   

  With kind regards,

   

  Van Hirtum Johan

   

  Van: David Vidal [mailto:notifications@odoo-community.org]
  Verzonden: donderdag 1 februari 2024 13:08
  Aan: Contributors
  Onderwerp: Re: New Odoo17 translated fields

   

  The ORM does it for you. Simply use the `lang` context:

   

  ```python

  record.with_context(lang='es_ES`).field_name = translated_string

  ```

   

  You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

   

  El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

  Dears,

   

  Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

  I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

   

  Thanks for helping me out.

   

  With kind regards,

   

   

  Van Hirtum Johan

  _______________________________________________
  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 Silvio Gregorini - 02:06 - 1 Feb 2024

• RE: New Odoo17 translated fields

  Beautiful ! Thank you very much David -)

   

  With kind regards,

   

  Van Hirtum Johan

   

  Van: David Vidal [mailto:notifications@odoo-community.org]
  Verzonden: donderdag 1 februari 2024 13:08
  Aan: Contributors
  Onderwerp: Re: New Odoo17 translated fields

   

  The ORM does it for you. Simply use the `lang` context:

   

  ```python

  record.with_context(lang='es_ES`).field_name = translated_string

  ```

   

  You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

   

  El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:

  Dears,

   

  Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

  I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

   

  Thanks for helping me out.

   

  With kind regards,

   

   

  Van Hirtum Johan

  _______________________________________________
  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 johan - 01:50 - 1 Feb 2024

• Re: OCA/connector-telephony Mantainers/PSC

  +1
  Thanks for stepping up Nicolas.
  I did some contributions there a while ago,  but haven't been active on it.
  
  /Daniel
  
  

  On 30/01/2024 12:46, Simone Orsi wrote:
  

  Is great to see people stepping up to take over. 

  Thanks! :thumbs-up:
  

  Just open a PR against https://github.com/OCA/repo-maintainer-conf to change this https://github.com/OCA/repo-maintainer-conf/blob/master/conf/psc/connector.yml#L91

  
  

  
  

  
  

  On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
  

  Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

  
  

  El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
  

  OK for me.
  

  _______________________________________________
  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 Alomar

  CEO & Founder
  

  
  

  www.dixmit.com

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

  
  
  --
  

  Simone Orsi

  
  

  Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

  _______________________________________________
  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 PARTNER

  M: +351 919 991 307
  E: dreis@OpenSourceIntegrators.com
  A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais

  

  ---

  by Daniel Reis - 01:21 - 1 Feb 2024

• Re: New Odoo17 translated fields

  The ORM does it for you. Simply use the `lang` context:

  
  

  ```python

  record.with_context(lang='es_ES`).field_name = translated_string

  ```

  
  

  You can get your active languages with `self.env['res.lang'].get_installed()` and loop over them if you want to do it at once.

  
  

  El jue, 1 feb 2024 a las 12:52, Johan Van Hirtum (<notifications@odoo-community.org>) escribió:
  

  Dears,

   

  Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

  I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

   

  Thanks for helping me out.

   

  With kind regards,

   

   

  Van Hirtum Johan

  _______________________________________________
  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 Vidal - 01:05 - 1 Feb 2024

• New Odoo17 translated fields

  Dears,

   

  Knows someone good developer documentation around the new translated fields in Odoo17 ? That there are stored in de database as jsonB field is clear. But I see nowhere how to set de translated terms for a field in a python method ( an on change or depends structure for ex. ). There must normally be a some variables where the translation are stored till the create method creates the model ? But I see nothing there.

  I want to use a python translation package ( deepL, deep-translator ) to give a first translation automatically when the translatable field is typed in the ID. Users can adapt, if they want to, but mostly, these translation are simply good -)

   

  Thanks for helping me out.

   

  With kind regards,

   

   

  Van Hirtum Johan

  ---

  by johan - 12:51 - 1 Feb 2024

• Re: OCA/connector-telephony Mantainers/PSC

  Great, I didn't know about the new repository to manage these things. It seems like a good idea to manage this in a repo. 
  The PR is ready: https://github.com/OCA/repo-maintainer-conf/pull/15

  
  

  Thanks!! 

  
  

  On Tue, Jan 30, 2024 at 9:47 AM Simone Orsi <notifications@odoo-community.org> wrote:
  

  Is great to see people stepping up to take over. 

  Thanks! :thumbs-up:
  

  Just open a PR against https://github.com/OCA/repo-maintainer-conf to change this https://github.com/OCA/repo-maintainer-conf/blob/master/conf/psc/connector.yml#L91

  
  

  
  

  
  

  On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
  

  Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

  
  

  El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
  

  OK for me.
  

  _______________________________________________
  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 Alomar

  CEO & Founder
  

  
  

  www.dixmit.com

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

  
  
  --
  

  Simone Orsi

  
  

  Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

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

  ---

  by Nicolas Rodriguez Sande - 02:30 - 30 Jan 2024

• Re: OCA/connector-telephony Mantainers/PSC

  Is great to see people stepping up to take over. 

  Thanks! :thumbs-up:
  

  Just open a PR against https://github.com/OCA/repo-maintainer-conf to change this https://github.com/OCA/repo-maintainer-conf/blob/master/conf/psc/connector.yml#L91

  
  

  
  

  
  

  On Tue, Jan 30, 2024 at 1:22 PM Enric Tobella Alomar <notifications@odoo-community.org> wrote:
  

  Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

  
  

  El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
  

  OK for me.
  

  _______________________________________________
  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 Alomar

  CEO & Founder
  

  
  

  www.dixmit.com

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

  
  
  --
  

  Simone Orsi

  
  

  Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

  ---

  by Simone Orsi - 01:45 - 30 Jan 2024

• Re: OCA/connector-telephony Mantainers/PSC

  Open a PR on https://github.com/OCA/repo-maintainer-conf adding you the right teams

  
  

  El mar, 30 ene 2024 a las 13:17, Pedro M. Baeza (<notifications@odoo-community.org>) escribió:
  

  OK for me.
  

  _______________________________________________
  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 Alomar

  CEO & Founder
  

  
  

  www.dixmit.com

  ---

  by Enric Tobella Alomar - 01:21 - 30 Jan 2024

• Re: OCA/connector-telephony Mantainers/PSC

  OK for me.
  

  ---

  by Pedro M. Baeza - 01:16 - 30 Jan 2024

• OCA/connector-telephony Mantainers/PSC

  Hello, is there an active maintainer of the OCA/connector-telephony repo? I saw that there are some people trying to migrate modules but no one is active to review/merge them. 

  
  

  If there is no active PSC i volunteer as PSC of the repository, since i use these modules in v14.0 and now i need them in v16.0. So I volunteer to be the PSC and bring the repository back to life since it appears to be abandoned.  

  
  

  I'm currently PSC of OCA/payroll and the other HR repositories, you can see some of my work there. 

  
  

  Hope this week finds you well. 
  Kind regards. 

  ---

  by Nicolas Rodriguez Sande - 01:10 - 30 Jan 2024

• Re: Reducing the size of a database

  Mail message table is typically 50 per cent of database or more. Frankly 6 years is not a lot. In my country fiscal authorities require 7 years, some other legal requirements need 50 years.

  
  

  On Wed, 24 Jan 2024, 5:36 am Holger Brunn, <notifications@odoo-community.org> wrote:
  

  > In my experience a
  
  
  > huge amount of records can be deleted by deleting old chatter
  
  
  > records.
  
  similar experience here, and for that we have
  https://github.com/OCA/server-tools/tree/14.0/autovacuum_message_attachment
  and its migrations to higher versions in the PRs.
  
  You should run the third query from
  https://wiki.postgresql.org/wiki/Disk_Usage
  anyways to first get an impression where the space goes.
  
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  _______________________________________________
  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> - 09:25 - 23 Jan 2024

• Re: Reducing the size of a database

  > In my experience a
  
  > huge amount of records can be deleted by deleting old chatter
  
  > records.
  
  similar experience here, and for that we have
  https://github.com/OCA/server-tools/tree/14.0/autovacuum_message_attachment
  and its migrations to higher versions in the PRs.
  
  You should run the third query from
  https://wiki.postgresql.org/wiki/Disk_Usage
  anyways to first get an impression where the space goes.
  
  
  -- 
  Your partner for the hard Odoo problems
  https://hunki-enterprises.com

  ---

  by Holger Brunn - 05:35 - 23 Jan 2024

  1 attachments 1 attachments

  signature.asc

• Re: Reducing the size of a database

  Hi,

  
  

  In my experience a huge amount of records can be deleted by deleting old chatter records.

  
  

  Kind regards, Ronald

  
  

  On 23-01-2024 15:57, Florian Laporte wrote:
  

  Dear Victor,

  How large are these databases? Database size usually does not become problematic as a result of too many sale orders or stock movements. You would need an insane amount.
  If this is the case, and you’ve verified that the size is not caused by large blobs/filestore, the only thing you can do is mass-delete records based on some arbitrary parameter like their create_date or write_date. There are many records Odoo won’t let you delete, though. It will ask you to archive them instead, because they are still referenced elsewhere. Archiving will obviously do nothing for database size.

  Sincerely,
  

  Florian L
  

  
  

  On Tue, 23 Jan 2024 at 15:22, Victor Champonnois <notifications@odoo-community.org> wrote:
  

  Dear contributors,

  Some of our customers have been using their database for more than 6 years. They want to reduce the size of the database, by archiving/aggregating old data (accounting entries, sales lines, stock movements, etc.). It would also be easier to do exports, pivot tables and so on.
  

  I see different solutions :
  

  1. Manually aggregate old data, with a specific method  by type of tables (account move lines, stock picking, sale order lines). For instance, aggregate old accounting entries with annual miscellaneous operations. Of course, we should keep a backup of the old data somewhere.
  

  2. Mass delete all the old and unused records, such as canceled POs, articles created by mistake. I don't see a way to do this quickly.
  

  Maybe an alternative solution would be a module that sets a "limit date" that acts as an automatic filter when doing exports, pivots, etc.
  

  Do you know any tool or procedure that would help with this ?
  

  Best regards,
  

  -- 
  Victor Champonnois - Coop IT Easy
  Tel : +32 475 81 01 12

  _______________________________________________
  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 "Ronald Portier" <rportier@therp.nl> - 04:21 - 23 Jan 2024

• Re: Reducing the size of a database

  I've seen this module:
  
  https://apps.odoo.com/apps/modules/13.0/muk_autovacuum/
  
  Obviously this can't be used on just any models, but for some models I 
  guess such an approach can work.
  
  Another idea I've proposed to a customer once, was to have a moment at 
  end of year where you create an "archive copy instance" for that year, 
  where people can login but not change anything. The code at that point 
  is also frozen and copied with. It's a dirty approach, as you'll after N 
  years be sitting with N archive instances, but there's a chance that at 
  some point they'll start agreeing to delete the oldest instance (as at 
  least here in NL, there's a year limit to which you are obliged to keep 
  financial history). The upside to this approach is that you can 
  aggressively start deleting records from live.
  
  -Tom
  
  
  

  ---

  by Tom Blauwendraat - 04:20 - 23 Jan 2024

• 1
• 2
• 3
• 4
• 5