Skip to Content

Contributors

  • Re: Google Analytics Universal to GA4 for versions < 15.0
    Have you consider using Google Tag Manager for the task?:

    Tecnativa

    El vie, 26 may 2023 a las 18:37, Francesco Foresti (<notifications@odoo-community.org>) escribió:
    Hi, 

    has anyone worked on a module to implement the change described here:  

    Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.

    Which according to this post, amounts to

    insert de GA tracker code manually on `website.layout` changing the `async` attribute to `t-att-async="true"`

     ?

    If not, do you think a backporting from v15 is feasible?

    Thanks!

    Francesco
    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

    _______________________________________________
    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 - 11:40 - 1 Jun 2023
  • Re: Issues with outgoing email management in Odoo
    Cyril,

    Thanks for the insights, I will follow the discussion there to be notified if the work is finished.

    Kind regards,


    On Thu, Jun 1, 2023 at 10:58 AM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:
    Hi Lois

    We did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalities

    We will definitely keep mail_body_notified_partner

    Best regards


    --------------------------------
    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.com

    Le mer. 31 mai 2023, 21:42, Lois Rilo Antelo <notifications@odoo-community.org> a écrit :
    Hi all,

    Indeed this is really annoying while dealing with Odoo mailing.

    A bit inline with Cyril's answer, as far as I know mail_tracking does not provide the information of the cc'd recipients to the external people (who only receive the email). In our case we have used mail_show_follower module which is already migrated to recent versions, not sure if there is any big difference with mail_body_notified_partner and maybe they can converge in a single module.

    Kind regards,


    On Wed, May 31, 2023 at 8:27 PM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:
    Hi Alex

    We also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)

    We solved this with :
    - mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'
    - disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern it

    We also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.
    On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)

    We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)
    That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.
    IMHO best configuration is 
    - odoo as the main mail system of the company for almost all the employees (notifications in Odoo)
    - dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partners

    Best regards
    --------------------------------
    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.com

    Le mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
    Hello everyone,
    
    This is a long standing topic in Odoo, but I'm facing it again with an 
    unhappy customer. The way Odoo manages the sending of messages to 
    followers of a "thread" by sending 1 email per follower, loosing all 
    information from people who could have been in CC of an incoming mail, 
    is really lame.
    
    Is there some knowledge hanging around about a way to change this so 
    that Odoo would:
    
    * record the CC in a secondary field (say follower_cc_ids) for incoming 
    message
    * promote a follower_cc to follower in case an incoming mail comes with 
    this person in To: rather than CC:
    * send outgoing mails with 1 single mail with all followers in To: and 
    follower_cc_ids in CC:
    
    I'm not super keen in touching this part of the Odoo source code, which 
    I find quite obscure,  and but maybe some have walked this path and 
    could provide feedback, advice (or even maybe source code).
    
    Thanks for your help,
    
    
    
    
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

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

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



    --
    Lois Rilo Antelo
    ERP Consultant Manager at ForgeFlow S.L.

    _______________________________________________
    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



    --
    Lois Rilo Antelo
    ERP Consultant Manager at ForgeFlow S.L.

    by Lois Rilo Antelo - 11:30 - 1 Jun 2023
  • Re: Issues with outgoing email management in Odoo
    Hi Lois

    We did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalities

    We will definitely keep mail_body_notified_partner

    Best regards


    --------------------------------
    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.com

    Le mer. 31 mai 2023, 21:42, Lois Rilo Antelo <notifications@odoo-community.org> a écrit :
    Hi all,

    Indeed this is really annoying while dealing with Odoo mailing.

    A bit inline with Cyril's answer, as far as I know mail_tracking does not provide the information of the cc'd recipients to the external people (who only receive the email). In our case we have used mail_show_follower module which is already migrated to recent versions, not sure if there is any big difference with mail_body_notified_partner and maybe they can converge in a single module.

    Kind regards,


    On Wed, May 31, 2023 at 8:27 PM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:
    Hi Alex

    We also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)

    We solved this with :
    - mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'
    - disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern it

    We also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.
    On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)

    We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)
    That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.
    IMHO best configuration is 
    - odoo as the main mail system of the company for almost all the employees (notifications in Odoo)
    - dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partners

    Best regards
    --------------------------------
    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.com

    Le mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
    Hello everyone,
    
    This is a long standing topic in Odoo, but I'm facing it again with an 
    unhappy customer. The way Odoo manages the sending of messages to 
    followers of a "thread" by sending 1 email per follower, loosing all 
    information from people who could have been in CC of an incoming mail, 
    is really lame.
    
    Is there some knowledge hanging around about a way to change this so 
    that Odoo would:
    
    * record the CC in a secondary field (say follower_cc_ids) for incoming 
    message
    * promote a follower_cc to follower in case an incoming mail comes with 
    this person in To: rather than CC:
    * send outgoing mails with 1 single mail with all followers in To: and 
    follower_cc_ids in CC:
    
    I'm not super keen in touching this part of the Odoo source code, which 
    I find quite obscure,  and but maybe some have walked this path and 
    could provide feedback, advice (or even maybe source code).
    
    Thanks for your help,
    
    
    
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

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

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



    --
    Lois Rilo Antelo
    ERP Consultant Manager at ForgeFlow S.L.

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


    by Cyril VINH-TUNG - 10:56 - 1 Jun 2023
  • Re: Issues with outgoing email management in Odoo
    Hi all,

    Indeed this is really annoying while dealing with Odoo mailing.

    A bit inline with Cyril's answer, as far as I know mail_tracking does not provide the information of the cc'd recipients to the external people (who only receive the email). In our case we have used mail_show_follower module which is already migrated to recent versions, not sure if there is any big difference with mail_body_notified_partner and maybe they can converge in a single module.

    Kind regards,


    On Wed, May 31, 2023 at 8:27 PM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:
    Hi Alex

    We also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)

    We solved this with :
    - mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'
    - disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern it

    We also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.
    On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)

    We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)
    That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.
    IMHO best configuration is 
    - odoo as the main mail system of the company for almost all the employees (notifications in Odoo)
    - dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partners

    Best regards
    --------------------------------
    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.com

    Le mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
    Hello everyone,
    
    This is a long standing topic in Odoo, but I'm facing it again with an 
    unhappy customer. The way Odoo manages the sending of messages to 
    followers of a "thread" by sending 1 email per follower, loosing all 
    information from people who could have been in CC of an incoming mail, 
    is really lame.
    
    Is there some knowledge hanging around about a way to change this so 
    that Odoo would:
    
    * record the CC in a secondary field (say follower_cc_ids) for incoming 
    message
    * promote a follower_cc to follower in case an incoming mail comes with 
    this person in To: rather than CC:
    * send outgoing mails with 1 single mail with all followers in To: and 
    follower_cc_ids in CC:
    
    I'm not super keen in touching this part of the Odoo source code, which 
    I find quite obscure,  and but maybe some have walked this path and 
    could provide feedback, advice (or even maybe source code).
    
    Thanks for your help,
    
    
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

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

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



    --
    Lois Rilo Antelo
    ERP Consultant Manager at ForgeFlow S.L.

    by Lois Rilo Antelo - 09:39 - 1 Jun 2023
  • Re: Issues with outgoing email management in Odoo
    Hi Alex

    We also faced long time issues with Odoo mail system and the worst part is that someone lost her job because of that 'unsual' email system (https://github.com/OCA/social/pull/855#issuecomment-1068256758)

    We solved this with :
    - mail_footer_notified_partner now renamed mail_body_notified_partner (better because the added text is located at the top of the body) + customization of the message saying 'WARNING if you reply to this email the following people will be cc :...'
    - disclaimer in the signature of every user that also ask people to reply to the mail with information about the subject and not reply with information that does not concern it

    We also use the amazing mail_tracking as mandatory for all our customers but it does not warn the recipients about who will receive the reply.
    On the other hand, for incoming emails, we did a PR to mail_tracking that allows to show in the chatter the aliases who were in to and cc (https://github.com/OCA/social/pull/941/commits/d6443446ceca845792d50fd3daa3d1ebdb06c3f0)

    We think that Odoo's mail system is great because it organizes communication very well but it's also very hard to convince our customers. People have very bad habits with standard mail systems (they reply to email with information that have nothing to see with the subject, they start another thread instead of replying existing discussion... so on)
    That said, we have some customers who use Odoo as 'the' mail system of the company and therefore improve their 'information organization'.
    IMHO best configuration is 
    - odoo as the main mail system of the company for almost all the employees (notifications in Odoo)
    - dedicated standard mailboxes (outside Odoo) for Managers (notifications by email) who might have very sensitive and private information to share directly with partners

    Best regards
    --------------------------------
    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.com

    Le mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :
    Hello everyone,
    
    This is a long standing topic in Odoo, but I'm facing it again with an 
    unhappy customer. The way Odoo manages the sending of messages to 
    followers of a "thread" by sending 1 email per follower, loosing all 
    information from people who could have been in CC of an incoming mail, 
    is really lame.
    
    Is there some knowledge hanging around about a way to change this so 
    that Odoo would:
    
    * record the CC in a secondary field (say follower_cc_ids) for incoming 
    message
    * promote a follower_cc to follower in case an incoming mail comes with 
    this person in To: rather than CC:
    * send outgoing mails with 1 single mail with all followers in To: and 
    follower_cc_ids in CC:
    
    I'm not super keen in touching this part of the Odoo source code, which 
    I find quite obscure,  and but maybe some have walked this path and 
    could provide feedback, advice (or even maybe source code).
    
    Thanks for your help,
    
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

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


    by Cyril VINH-TUNG - 08:26 - 31 May 2023
  • Re: Issues with outgoing email management in Odoo
    This is open source, so you can contribute with that option in the module, via a configurable parameter. AFAIK, this is already being done by some contributor. Just look around.

    Regards.

    by Pedro M. Baeza - 08:11 - 31 May 2023
  • Re: Issues with outgoing email management in Odoo
    As far as I understand mail_tracking does insert a tracking image into 
    emails [1]. This could be unwanted by receivers so I don't want the 
    tracking feature but I want a solution for the issue described by 
    Alexandre. Would it be reasonable to split the module into two or to 
    make the tracking configurable?
    
    [1] 
    https://github.com/OCA/social/blob/12.0/mail_tracking/models/mail_mail.py
    

    by Jan Suhr - 08:01 - 31 May 2023
  • Re: Issues with outgoing email management in Odoo
    Thanks, I'll check this. I had missed some part of the perimeter of that 
    module and thought it was about tracking who opened a given message and 
    the delivery status and such.
    
    Best regards
    
    Alexandre
    
    On 31/05/2023 17:17, Pedro M. Baeza wrote:
    
    > We handled this several years ago in `mail_tracking` module and it does 
    
    > exactly what you want: show those in CC in replies, and suggest them on 
    
    > next messages (even if they are not contacts yet).
    
    > 
    
    > Regards.
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15 
    
    > <https://odoo-community.org/groups/contributors-15>
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe 
    
    > <https://odoo-community.org/groups?unsubscribe>
    
    > 
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    
    

    by Alexandre Fayolle - 05:45 - 31 May 2023
  • Re: Issues with outgoing email management in Odoo
    We handled this several years ago in `mail_tracking` module and it does exactly what you want: show those in CC in replies, and suggest them on next messages (even if they are not contacts yet).

    Regards.

    by Pedro M. Baeza - 05:16 - 31 May 2023
  • Issues with outgoing email management in Odoo
    Hello everyone,
    
    This is a long standing topic in Odoo, but I'm facing it again with an 
    unhappy customer. The way Odoo manages the sending of messages to 
    followers of a "thread" by sending 1 email per follower, loosing all 
    information from people who could have been in CC of an incoming mail, 
    is really lame.
    
    Is there some knowledge hanging around about a way to change this so 
    that Odoo would:
    
    * record the CC in a secondary field (say follower_cc_ids) for incoming 
    message
    * promote a follower_cc to follower in case an incoming mail comes with 
    this person in To: rather than CC:
    * send outgoing mails with 1 single mail with all followers in To: and 
    follower_cc_ids in CC:
    
    I'm not super keen in touching this part of the Odoo source code, which 
    I find quite obscure,  and but maybe some have walked this path and 
    could provide feedback, advice (or even maybe source code).
    
    Thanks for your help,
    
    
    -- 
    Alexandre Fayolle
    Senior Software Engineer
    Tel : +33 4 58 48 20 30
    
    Camptocamp France SAS
    18 rue du Lac Saint André
    73 370 Le Bourget-du-Lac
    France
    
    http://www.camptocamp.com
    

    by Alexandre Fayolle - 05:11 - 31 May 2023
  • New poll in the forum: Add a "Jobs" forum category?
    Please go to https://github.com/orgs/OCA/discussions/95 and share your thoughts.

    by Jairo Llopis - 10:11 - 30 May 2023
  • Google Analytics Universal to GA4 for versions < 15.0
    Hi, 

    has anyone worked on a module to implement the change described here:  

    Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.

    Which according to this post, amounts to

    insert de GA tracker code manually on `website.layout` changing the `async` attribute to `t-att-async="true"`

     ?

    If not, do you think a backporting from v15 is feasible?

    Thanks!

    Francesco
    --

    Francesco Foresti
    Sicurpharma Srl
    +39 333 8123 790

    by Francesco Foresti - 06:31 - 26 May 2023
  • Re: Clear Customer Invoice and Vendor Bills
    Hello Rafael,

    congratulations. That module is quite useful.
    I like it.
    Best regards
    Thorsten Vocks

    openBIG.org
    Dipl. Kaufmann (FH)
    Porscheweg 4-6
    49661 Cloppenburg

    Phone: +49 4471 8409000
    Fax: +49 4471 84090009
    Mail: thorsten.vocks@openbig.org

                  


    Am Do., 25. Mai 2023 um 03:47 Uhr schrieb Rafael Blasco <notifications@odoo-community.org>:

    Sure

     

    https://github.com/OCA/account-invoicing/tree/15.0/account_invoice_clearing

     

     

    De: Daniel Guerrero <notifications@odoo-community.org>
    Enviado el: domingo, 7 de mayo de 2023 1:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Clear Customer Invoice and Vendor Bills

     

    Hello Rafael,

     

    Did you develop the module?

     

    Regards,

    Daniel

     

    From: Rafael Blasco <notifications@odoo-community.org>
    Date: Sunday, 2 April 2023 at 1:47 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: RE: Clear Customer Invoice and Vendor Bills

    Thank you Yoshi but as I said Odoo CE has it for journal items in core.

     

    IMHO account_neeting is not needed anymore in v14+ as can be done with “Automatic Entries” for selected Journal Items.

     

    We will develop this UX Easy module for invoicing user in the next 2 weeks 😊

     

    Best regards

    Rafael

     

     

    De: Yoshi Tashiro <notifications@odoo-community.org>
    Enviado el: sábado, 1 de abril de 2023 14:22
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Clear Customer Invoice and Vendor Bills

     

     

    On Sat, Apr 1, 2023 at 9:12 PM Rafael Blasco <notifications@odoo-community.org> wrote:

    Dear Contributors,

     

    I have been looking for a module which help to clear customer invoices with vendor bill from the invoices in the 2 directions.

     

    I look for it in

     

    We will develop a module account_invoice_clearing

     

    From customer invoice o vendor bill you can bottom clear and a wizard will help you to clear with bill or viceversa

    From list same with an action

     

    Actually,  this can be done by accountants really easy from account.move.lines but the module wants to provide this tool for invoicing department.

     

    If any feedback, thank you!

     

    Regards,

    Rafael

     

    MT-2035

     

    _______________________________________________
    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 Thorsten Vocks - 07:11 - 25 May 2023
  • Invetory : pallete rate per day + picking rate/coli + pallete IN/OUT rate

    Hasllo to everyone,
    I have several questions. We are implementing Odoo WMS here in Czech republic, and have to fix fololowing inventory rates
    1. stored pallete rate per day = example 1€/pallete/day
    2. picking rate/coli = example 0,25€/picked coli
    3. pallete rate IN/OUT = rate pallete IN 0,35€ (receive) + pallete out (delivery)
    Does anyone of you can help with this isuue? Do we have in Odoo some extra applications for inventory rates?

    Thanks in advance
    S pozdravem / Best regards

    MILOŠ MILOJKOVIĆ

    Konzultant MRP/Inventory

    Mobile: +420 725 426 206
    (6) Miloš Milojković | LinkedIn

    26HOUSE s.r.o.
    Karolinská 2, 186 00 Praha 8
    Česká republika
    www.26house.com 


    by Miloš Milojković - 10:01 - 25 May 2023
  • RE: Clear Customer Invoice and Vendor Bills

    Sure

     

    https://github.com/OCA/account-invoicing/tree/15.0/account_invoice_clearing

     

     

    De: Daniel Guerrero <notifications@odoo-community.org>
    Enviado el: domingo, 7 de mayo de 2023 1:57
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Clear Customer Invoice and Vendor Bills

     

    Hello Rafael,

     

    Did you develop the module?

     

    Regards,

    Daniel

     

    From: Rafael Blasco <notifications@odoo-community.org>
    Date: Sunday, 2 April 2023 at 1:47 PM
    To: Contributors <contributors@odoo-community.org>
    Subject: RE: Clear Customer Invoice and Vendor Bills

    Thank you Yoshi but as I said Odoo CE has it for journal items in core.

     

    IMHO account_neeting is not needed anymore in v14+ as can be done with “Automatic Entries” for selected Journal Items.

     

    We will develop this UX Easy module for invoicing user in the next 2 weeks 😊

     

    Best regards

    Rafael

     

     

    De: Yoshi Tashiro <notifications@odoo-community.org>
    Enviado el: sábado, 1 de abril de 2023 14:22
    Para: Contributors <contributors@odoo-community.org>
    Asunto: Re: Clear Customer Invoice and Vendor Bills

     

     

    On Sat, Apr 1, 2023 at 9:12 PM Rafael Blasco <notifications@odoo-community.org> wrote:

    Dear Contributors,

     

    I have been looking for a module which help to clear customer invoices with vendor bill from the invoices in the 2 directions.

     

    I look for it in

     

    We will develop a module account_invoice_clearing

     

    From customer invoice o vendor bill you can bottom clear and a wizard will help you to clear with bill or viceversa

    From list same with an action

     

    Actually,  this can be done by accountants really easy from account.move.lines but the module wants to provide this tool for invoicing department.

     

    If any feedback, thank you!

     

    Regards,

    Rafael

     

    MT-2035

     

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


    by "Rafael Blasco" <rblasco@rbnpro.com> - 03:46 - 25 May 2023
  • Re: Reserved / priority worker
    Maybe a dedicated server for odoo e.g. in a docker - multiple odoo servers, a single postgres database ?
    so all calls for IAP are routed to this specific server

    Dominique 


    On Mon, 22 May 2023 at 21:02, Radovan Skolnik <notifications@odoo-community.org> wrote:
    Hello,
    
    I am going to provide some services very similar to what's available as IAP in 
    Odoo so part of it is checking whether customer has got enough "credits". The 
    easiest way would be to create a controller to handle this but I am afraid of 
    situations where the server is occupied with different things like many users, 
    etc.
    
    Is there a way to "reserve" a worker for such kind of things? Or maybe somehow 
    to give priority for processing such requests?
    
    Any advise is welcome. Thank you
    
    Best regards
    
    	Radovan Skolnik
    
    
    

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


    by dominique.k - 03:21 - 23 May 2023
  • Re: Reserved / priority worker

    and it references:

    https://github.com/dduarte-odoogap/docker_testing_environment/blob/master/docker-compose.yml


    On 2023-05-22 14:16, Radovan Skolnik wrote:
    Erik,
    
    thanks a lot. Will check it out. Best regards,
    
    	Radovan
    
    On pondelok 22. mája 2023 23:12:40 CEST Erik Myllymaki wrote:
    
    > I was just watching this video the other day that I thought did a good job
    
    > of explaining separate odoo instances for erp and cron:
    
    > 
    
    > https://www.youtube.com/watch?v=_q1MhVPKV5g
    
    > 
    
    > 
    
    > 
    
    > 
    
    > On 2023-05-22 14:06, Radovan Skolnik wrote:
    
    > 
    
    > Graeme,
    
    > 
    
    > thanks for the tip. You mean starting another instance over the same
    
    > database? I must admit I haven't poked the internals on how concurrent
    
    > access like this would work but if it worked, that would be quite easy.
    
    > 
    
    > Best regards,
    
    > 
    
    > 	Radovan
    
    > 
    
    > On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote:
    
    > > Should be easy enough, just start another odoo instance listening on a
    
    > > 
    
    > > different port or container. Configure reverse proxy to send those
    
    > > requests
    
    > > 
    
    > > to that instance. Its a fairly common setup already to have a seperate
    
    > > 
    
    > > instance for running crons, particular routes that need extra memory etc.
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > On Tue, 23 May 2023, 1:02 am Radovan Skolnik,
    
    > > 
    
    > > <notifications@odoo-community.org> wrote:
    
    > > 
    
    > > 
    
    > > 
    
    > > Hello,
    
    > > 
    
    > > 
    
    > > 
    
    > > I am going to provide some services very similar to what's available as
    
    > > IAP
    
    > > 
    
    > > in Odoo so part of it is checking whether customer has got enough
    
    > > 
    
    > > "credits". The easiest way would be to create a controller to handle this
    
    > > 
    
    > > but I am afraid of situations where the server is occupied with different
    
    > > 
    
    > > things like many users, etc.
    
    > > 
    
    > > 
    
    > > 
    
    > > Is there a way to "reserve" a worker for such kind of things? Or maybe
    
    > > 
    
    > > somehow to give priority for processing such requests?
    
    > > 
    
    > > 
    
    > > 
    
    > > Any advise is welcome. Thank you
    
    > > 
    
    > > 
    
    > > 
    
    > > Best regards
    
    > > 
    
    > > 	Radovan Skolnik
    
    > > 
    
    > > _______________________________________________
    
    > > 
    
    > > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > > 
    
    > > Post to: mailto:contributors@odoo-community.org
    
    > > 
    
    > > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > _______________________________________________
    
    > > 
    
    > > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > > 
    
    > > Post to: mailto:contributors@odoo-community.org
    
    > > 
    
    > > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    > 
    
    > 
    
    > _______________________________________________
    
    > Mailing-List: https://odoo-community.org/groups/contributors-15
    
    > Post to: mailto:contributors@odoo-community.org
    
    > Unsubscribe: https://odoo-community.org/groups?unsubscribe
    
    
    
    
    

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


    by erik.myllymaki - 11:21 - 22 May 2023
  • Re: Reserved / priority worker
    Erik,
    
    thanks a lot. Will check it out. Best regards,
    
    	Radovan
    
    On pondelok 22. mája 2023 23:12:40 CEST Erik Myllymaki wrote:
    
    > I was just watching this video the other day that I thought did a good job
    
    > of explaining separate odoo instances for erp and cron:
    
    > 
    
    > https://www.youtube.com/watch?v=_q1MhVPKV5g
    
    > 
    
    > 
    
    > 
    
    > 
    
    > On 2023-05-22 14:06, Radovan Skolnik wrote:
    
    > 
    
    > Graeme,
    
    > 
    
    > thanks for the tip. You mean starting another instance over the same
    
    > database? I must admit I haven't poked the internals on how concurrent
    
    > access like this would work but if it worked, that would be quite easy.
    
    > 
    
    > Best regards,
    
    > 
    
    > 	Radovan
    
    > 
    
    > On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote:
    
    > > Should be easy enough, just start another odoo instance listening on a
    
    > > 
    
    > > different port or container. Configure reverse proxy to send those
    
    > > requests
    
    > > 
    
    > > to that instance. Its a fairly common setup already to have a seperate
    
    > > 
    
    > > instance for running crons, particular routes that need extra memory etc.
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > 
    
    > > On Tue, 23 May 2023, 1:02 am Radovan Skolnik,
    
    > > 
    
    > > <notifications@odoo-community.org> wrote:
    
    > > 
    
    > > 
    
    > > 
    
    > > Hello,
    
    > > 
    
    > > 
    
    > > 
    
    > > I am going to provide some services very similar to what's available as
    
    > > IAP
    
    > > 
    
    > > in Odoo so part of it is checking whether customer has got enough
    
    > > 
    
    > > "credits". The easiest way would be to create a controller to handle this
    
    > > 
    
    > > but I am afraid of situations where the server is occupied with different
    
    > > 
    
    > > things like many users, etc.
    
    > > 
    
    > > 
    
    > > 
    
    > > Is there a way to "reserve" a worker for such kind of things? Or maybe
    
    > > 
    
    > > somehow to give priority for processing such requests?
    
    > > 
    
    > > 
    
    > > 
    
    > > Any advise is welcome. Thank you
    
    > > 
    
    > > 
    
    > > 
    
    > > Best regards
    
    > > 
    
    > > 	Radovan Skolnik
    
    > > 
    
    > > _______________________________________________
    
    > > 
    
    > > 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 Radovan Skolnik - 11:16 - 22 May 2023
  • Re: Reserved / priority worker

    I was just watching this video the other day that I thought did a good job of explaining separate odoo instances for erp and cron:

    https://www.youtube.com/watch?v=_q1MhVPKV5g


    On 2023-05-22 14:06, Radovan Skolnik wrote:
    Graeme,
    
    thanks for the tip. You mean starting another instance over the same database? 
    I must admit I haven't poked the internals on how concurrent access like this 
    would work but if it worked, that would be quite easy.
    
    Best regards,
    
    	Radovan
    
    On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote:
    
    > Should be easy enough, just start another odoo instance listening on a
    
    > different port or container. Configure reverse proxy to send those requests
    
    > to that instance. Its a fairly common setup already to have a seperate
    
    > instance for running crons, particular routes that need extra memory etc.
    
    > 
    
    > 
    
    > On Tue, 23 May 2023, 1:02 am Radovan Skolnik,
    
    > <notifications@odoo-community.org> wrote:
    
    > 
    
    > Hello,
    
    > 
    
    > I am going to provide some services very similar to what's available as IAP
    
    > in Odoo so part of it is checking whether customer has got enough
    
    > "credits". The easiest way would be to create a controller to handle this
    
    > but I am afraid of situations where the server is occupied with different
    
    > things like many users, etc.
    
    > 
    
    > Is there a way to "reserve" a worker for such kind of things? Or maybe
    
    > somehow to give priority for processing such requests?
    
    > 
    
    > Any advise is welcome. Thank you
    
    > 
    
    > Best regards
    
    > 
    
    > 	Radovan Skolnik
    
    > 
    
    > 
    
    > 
    
    > 
    
    > _______________________________________________
    
    > 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 erik.myllymaki - 11:11 - 22 May 2023
  • Re: Reserved / priority worker
    Graeme,
    
    thanks for the tip. You mean starting another instance over the same database? 
    I must admit I haven't poked the internals on how concurrent access like this 
    would work but if it worked, that would be quite easy.
    
    Best regards,
    
    	Radovan
    
    On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote:
    
    > Should be easy enough, just start another odoo instance listening on a
    
    > different port or container. Configure reverse proxy to send those requests
    
    > to that instance. Its a fairly common setup already to have a seperate
    
    > instance for running crons, particular routes that need extra memory etc.
    
    > 
    
    > 
    
    > On Tue, 23 May 2023, 1:02 am Radovan Skolnik,
    
    > <notifications@odoo-community.org> wrote:
    
    > 
    
    > Hello,
    
    > 
    
    > I am going to provide some services very similar to what's available as IAP
    
    > in Odoo so part of it is checking whether customer has got enough
    
    > "credits". The easiest way would be to create a controller to handle this
    
    > but I am afraid of situations where the server is occupied with different
    
    > things like many users, etc.
    
    > 
    
    > Is there a way to "reserve" a worker for such kind of things? Or maybe
    
    > somehow to give priority for processing such requests?
    
    > 
    
    > Any advise is welcome. Thank you
    
    > 
    
    > Best regards
    
    > 
    
    > 	Radovan Skolnik
    
    > 
    
    > 
    
    > 
    
    > 
    
    > _______________________________________________
    
    > 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 Radovan Skolnik - 11:05 - 22 May 2023