Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Translations in version 16+ 
    Hi,

with the changed backend mechanism of translation the Developer Tools "Technical Translation" disappeared. There is a substantial movement in local community to get Slovak and Czech translations sorted out properly but using Odoo's Transifex is inflexible. OCA's Weblate seems better but... If it was lower versions I'd propose doing module sprints on live instance (using Technical Translation" and then exporting the resulting .po file but that's not possible now.

What is your preferred / proposed way of doing this? We're talking whole Odoo (Community for a start) here and few people (10-20 at max) working simultaneously. Any advise is highly welcome. Thank you.

Best regards

	Radovan Skolnik
    by Radovan Skolnik - 09:50 - 14 Jul 2023
  • nominating thomaspaulb as PSC for l10n-netherlands 
    Hi all,

I'd like to nominate https://github.com/thomaspaulb for the team who 
contributes all over the place, but also is based in NL and contributes there 
enough to merit this.

At the same time I acknowledge that I'm not doing a great job as 
representative in this repo, so if anyone would like to step forward to take 
this position over, I'd be happy to pass the torch.

Best,
Holger


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com
    by Holger Brunn - 04:02 - 13 Jul 2023

    1 attachments 1 attachments

    signature.asc

    6 replies 6 replies

  • Git

    Dear Contributors,

    i know… this topic maybe don´t belong here… But i´ll give it a try… I do have the following problem:

     

    Switched from mac to a Win PC a while ago with my dev enviroment. Everything was working great and the performance boost is quite addictive ;P

    But something happened now and i dont know what exactly.

     

    So here is my bottleneck right now.  For some reason (which i dont know) i am not able to patch the code anymore when migrating a module.

     

    So the format patch…

    „git format-patch --keep-subject --stdout origin/16.0..origin/15.0 -- MODULE | git am -3 –keep“

    … will not apply and i get the following error:

     

    fatal: empty ident name (for <>) not allowed

    Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

     

    So the git am got stuck and when i look at the author-script in the rebase-apply folder, there is nothing for GIT_AUTHOR_NAME='', GIT_AUTHOR_EMAIL='', GIT_AUTHOR_DATE=''

    I already set the name and email in gitconfig (local & global) with git config --global user.name "NAME" & with git config --global user.email "EMAIL" but the behaviour is the same.

     

    In addition, i dont know where it gets this line from: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

     

    When i enter the name and email in the author script file and continue the am… -> Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

    But i guess the reference is totally wrong!

     

    Has anybody an idea, what happens here and why it doesnt pull the name & Email properly?

     

    I addition the pre-commit makes trouble as well.

    Generate the default setup.py for an addons directory fails with the error:

    - hook id: setuptools-odoo-make-default

    - exit code:

     

    Traceback (most recent call last):

      File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 194, in _run_module_as_main

        return _run_code(code, main_globals, None,

      File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 87, in _run_code

        exec(code, run_globals)

      File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\Scripts\setuptools-odoo-make-default.EXE\__main__.py", line 7, in <module>

      File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 402, in main

        make_default_setup_addons_dir(

      File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 152, in make_default_setup_addons_dir

        make_default_setup_addon(

      File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 122, in make_default_setup_addon

        os.symlink(os.path.relpath(addon_dir, odoo_addons_path), link_path)

    OSError: [WinError 1314] Dem Client fehlt ein erforderliches Recht: '..\\..\\..\\..\\MODULE' -> '.\\setup\\MODULE\\odoo\\addons\\MODULE'

     

    So i guess there is eaither a problem with symlink (if necessary), access rights on my local drive or Visual Studio Issue. Futhermore i get:

    ************* Module MODULE

    MODULE\views\file1.xml:1: [W7930(file-not-used), ]  not used from manifest

    MODULE\views\file2.xml:1: [W7930(file-not-used), ]  not used from manifest

    ************* Module MODULE

     

    And some further files listed that dont really exist n the format-pached files….

    Already checked a lot of infos from the web, but nothing worked out.

     

    Is anybody aware of whats going on here or rather can help me to sort this out?

    I wanted to give it a try this way, before performing more and more tests or before decide to use my old enviroment and setup the new system from scratch.

     

    Any helpful hint is much appreciated

     

    All the best

    Nils

     

    -- 

    NICO SOLUTIONS - ENGINEERING & IT 
    Dr.-Ruckert-Str.     1G 
    28865 Lilienthal 
    Deutschland (Germany) 

    by Nils Coenen - 02:47 - 12 Jul 2023

    2 replies 2 replies

    • Re: Git

      Hi Daniel,

      thanks for you reply. Yes i am using it directly on windows. I am just curious about what happened, as it was working flawlessly. Kind of weird.

      Temporarily i will switch back on my mac… but i want to get this running on the new system.

      I´ll have a look tot he WSL2 Ubuntu environment. Thank you!

       

      All the best

      Nils

       

      -- 

      NICO SOLUTIONS - ENGINEERING & IT 
      Dr.-Ruckert-Str.       1G 
      28865 Lilienthal 
      Deutschland (Germany) 

       

      Von: Daniel Reis <notifications@odoo-community.org>
      Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
      Datum: Mittwoch, 12. Juli 2023 um 15:22
      An: Contributors <contributors@odoo-community.org>
      Betreff: Re: Git

       

      It seems that you are using Git directly under Windows.
      My recommendation would be to instead use Git inside a WSL2 Ubuntu environment.

      Thanks
      Daniel

      On 12/07/2023 13:47, nils.coenen wrote:

      Dear Contributors,

      i know… this topic maybe don´t belong here… But i´ll give it a try… I do have the following problem:

       

      Switched from mac to a Win PC a while ago with my dev enviroment. Everything was working great and the performance boost is quite addictive ;P

      But something happened now and i dont know what exactly.

       

      So here is my bottleneck right now.  For some reason (which i dont know) i am not able to patch the code anymore when migrating a module.

       

      So the format patch…

      „git format-patch --keep-subject --stdout origin/16.0..origin/15.0 -- MODULE | git am -3 –keep“

      … will not apply and i get the following error:

       

      fatal: empty ident name (for <>) not allowed

      Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

       

      So the git am got stuck and when i look at the author-script in the rebase-apply folder, there is nothing for GIT_AUTHOR_NAME='', GIT_AUTHOR_EMAIL='', GIT_AUTHOR_DATE=''

      I already set the name and email in gitconfig (local & global) with git config --global user.name "NAME" & with git config --global user.email "EMAIL" but the behaviour is the same.

       

      In addition, i dont know where it gets this line from: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

       

      When i enter the name and email in the author script file and continue the am… -> Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

      But i guess the reference is totally wrong!

       

      Has anybody an idea, what happens here and why it doesnt pull the name & Email properly?

       

      I addition the pre-commit makes trouble as well.

      Generate the default setup.py for an addons directory fails with the error:

      - hook id: setuptools-odoo-make-default

      - exit code:

       

      Traceback (most recent call last):

        File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 194, in _run_module_as_main

          return _run_code(code, main_globals, None,

        File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 87, in _run_code

          exec(code, run_globals)

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\Scripts\setuptools-odoo-make-default.EXE\__main__.py", line 7, in <module>

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 402, in main

          make_default_setup_addons_dir(

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 152, in make_default_setup_addons_dir

          make_default_setup_addon(

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 122, in make_default_setup_addon

          os.symlink(os.path.relpath(addon_dir, odoo_addons_path), link_path)

      OSError: [WinError 1314] Dem Client fehlt ein erforderliches Recht: '..\\..\\..\\..\\MODULE' -> '.\\setup\\MODULE\\odoo\\addons\\MODULE'

       

      So i guess there is eaither a problem with symlink (if necessary), access rights on my local drive or Visual Studio Issue. Futhermore i get:

      ************* Module MODULE

      MODULE\views\file1.xml:1: [W7930(file-not-used), ]  not used from manifest

      MODULE\views\file2.xml:1: [W7930(file-not-used), ]  not used from manifest

      ************* Module MODULE

       

      And some further files listed that dont really exist n the format-pached files….

      Already checked a lot of infos from the web, but nothing worked out.

       

      Is anybody aware of whats going on here or rather can help me to sort this out?

      I wanted to give it a try this way, before performing more and more tests or before decide to use my old enviroment and setup the new system from scratch.

       

      Any helpful hint is much appreciated

       

      All the best

      Nils

       

      -- 

      NICO SOLUTIONS - ENGINEERING & IT 
      Dr.-Ruckert-Str.       1G 
      28865 Lilienthal 
      Deutschland (Germany) 

       

      --

      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

      Das Bild wurde vom Absender entfernt.

      _______________________________________________
      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 - 04:01 - 12 Jul 2023
    • Re: Git
      It seems that you are using Git directly under Windows.
      My recommendation would be to instead use Git inside a WSL2 Ubuntu environment.

      Thanks
      Daniel

      On 12/07/2023 13:47, nils.coenen wrote:

      Dear Contributors,

      i know… this topic maybe don´t belong here… But i´ll give it a try… I do have the following problem:

       

      Switched from mac to a Win PC a while ago with my dev enviroment. Everything was working great and the performance boost is quite addictive ;P

      But something happened now and i dont know what exactly.

       

      So here is my bottleneck right now.  For some reason (which i dont know) i am not able to patch the code anymore when migrating a module.

       

      So the format patch…

      „git format-patch --keep-subject --stdout origin/16.0..origin/15.0 -- MODULE | git am -3 –keep“

      … will not apply and i get the following error:

       

      fatal: empty ident name (for <>) not allowed

      Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

       

      So the git am got stuck and when i look at the author-script in the rebase-apply folder, there is nothing for GIT_AUTHOR_NAME='', GIT_AUTHOR_EMAIL='', GIT_AUTHOR_DATE=''

      I already set the name and email in gitconfig (local & global) with git config --global user.name "NAME" & with git config --global user.email "EMAIL" but the behaviour is the same.

       

      In addition, i dont know where it gets this line from: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

       

      When i enter the name and email in the author script file and continue the am… -> Applying: From 9db567da369584bfa55d85bb9e42f167ae4135ea Mon Sep 17 00:00:00 2001

      But i guess the reference is totally wrong!

       

      Has anybody an idea, what happens here and why it doesnt pull the name & Email properly?

       

      I addition the pre-commit makes trouble as well.

      Generate the default setup.py for an addons directory fails with the error:

      - hook id: setuptools-odoo-make-default

      - exit code:

       

      Traceback (most recent call last):

        File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 194, in _run_module_as_main

          return _run_code(code, main_globals, None,

        File "c:\users\my_user\appdata\local\programs\python\python38\lib\runpy.py", line 87, in _run_code

          exec(code, run_globals)

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\Scripts\setuptools-odoo-make-default.EXE\__main__.py", line 7, in <module>

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 402, in main

          make_default_setup_addons_dir(

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 152, in make_default_setup_addons_dir

          make_default_setup_addon(

        File "C:\Users\ my_user \.cache\pre-commit\reposb6fkp7c\py_env-python3\lib\site-packages\setuptools_odoo\make_default_setup.py", line 122, in make_default_setup_addon

          os.symlink(os.path.relpath(addon_dir, odoo_addons_path), link_path)

      OSError: [WinError 1314] Dem Client fehlt ein erforderliches Recht: '..\\..\\..\\..\\MODULE' -> '.\\setup\\MODULE\\odoo\\addons\\MODULE'

       

      So i guess there is eaither a problem with symlink (if necessary), access rights on my local drive or Visual Studio Issue. Futhermore i get:

      ************* Module MODULE

      MODULE\views\file1.xml:1: [W7930(file-not-used), ]  not used from manifest

      MODULE\views\file2.xml:1: [W7930(file-not-used), ]  not used from manifest

      ************* Module MODULE

       

      And some further files listed that dont really exist n the format-pached files….

      Already checked a lot of infos from the web, but nothing worked out.

       

      Is anybody aware of whats going on here or rather can help me to sort this out?

      I wanted to give it a try this way, before performing more and more tests or before decide to use my old enviroment and setup the new system from scratch.

       

      Any helpful hint is much appreciated

       

      All the best

      Nils

       

      -- 

      NICO SOLUTIONS - ENGINEERING & IT 
      Dr.-Ruckert-Str.       1G 
      28865 Lilienthal 
      Deutschland (Germany) 

      _______________________________________________
      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 - 03:22 - 12 Jul 2023
  • Odoo with a decoupled front-end

    Hello,

    I'm looking for a solution where I can use Odoo with a decoupled front-end and I'd love to hear your thoughts. I'd like to use Odoo as my back-end and Nuxt as my front-end. I've seen https://github.com/vuestorefront-community/odoo but this looks dedicated to e-commerce.

    Is it possible to have a decoupled front-end but still use the Odoo login functionality and so the I can integrate the Odoo portal (e.g. domain.nl/my/home) inside Nuxt? I've seen https://github.com/OCA/rest-framework as well but I am not sure if this can work with the portal.

    Any thoughts are very welcome. Thank you!

    With kind regards,

    Wytze Jan Riedstra
    codeNext

    by Wytze Jan Riedstra - 07:51 - 12 Jul 2023

    9 replies 9 replies

  • Logistics Business Cooperation Partner with Xin Nuo Yuan International Logistics Co., LTD.
    Hi dear,
    I apologize for taking you 1 minutes to review this email. It won't waste your time at all.

    Do you want to reduce your shipping costs and keep your shipment safe from/to CHINA?

    This is professional shipping agent certified on WCA. We have competitive prices and services.

    We provide below service:

    A. Full container, LCL shipment to port/to door.
    B. Air shipping to airport/to door.
    C. Offer a one-top service platform with shipping space booking, customs declaration, inspection reporting, tax paying, insuring, storage, delivering.etc.

    Sincerely hope we can cooperate,I promise will try my best to quote you the best rate with the best way.

    BTW, if I send to the wrong person, would you please forward it to the right person? Thank you so much~

    WhatsApp：+86 15999719220
    our website: http://www.xnydg.com/
     

    Have a wonderful day~

    Stella

    If you do not desire to receive future emails from us, then please click Unsubscribe to me and we will remove you from our mailing list.

    by "syin@xny-logistics.com" <sales08@xny-logistics.com> - 08:51 - 11 Jul 2023

    4 attachments 4 attachments

    11479_WCA LOGO.png
    62268_签名.png
    CatchF59A(07-06-(07-11-14-48-11).jpg
    92.gif
  • Optional drop-shipping
    Hello, looking for advice on any OCA module that may exists to assist on the following scenario:

    Orders are usually delivered from our warehouse.
    But in some special cases we can have a supplier deliver it directly to the customer location (maybe they are closer to the customer).

    This is a dropshipping scenario, it can be configured in Odoo, but it is an inflexible always or never choice.
    I wish there were an adhoc approach for this.

    In this case we would need to specifically say that this delivery is to be dropshipped, maybe even set what supplier it should come from.
    Maybe there is something already out there that can help with this.

    Thanks for any directions

    --
    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 - 06:25 - 7 Jul 2023

    4 replies 4 replies

  • Packaging in the warehouse 
    Hello,

another question for another customer. The customer is dealing with storing 
and distribution of food supplies. The way the products are modelled (in SAP 
which is the source of master data) is a product - for example rice, and a 
packaging - for example 50kg bag, 25kg bag, ...

So the first idea was to use Odoo's packaging. However Odoo does not use it for 
inventory management (inside warehouse). The different types of packaging could 
maybe be modelled as attributes for variants. But that doesn't feel right as 
well. In this scenario I would expect to be able to get a report of total 
amount of rice in the warehouse as well as grouped by different packaging 
types.

Any pointers are highly welcome. Thank you.

Best regards

	Radovan Skolnik
    by Radovan Skolnik - 05:46 - 28 Jun 2023

    7 replies 7 replies

  • Palette management in the warehouse 
    Hello,

hope this is not a stupid question. Customer would like to have something like 
this:

*) a palette with multiple different lots (batches) of single product (or even 
with different products)
*) the palette can be placed in a (palatte) location/position in the warehouse
*) you can remove things from palette (put them in outgoing shipments for 
example)
*) when all the contents of the palette is gone, the palette should 
"disappear" as well and effectively make the location/position free.

Has anyone dealt with something like this? Any pointers I could follow?

Thank you very much. Best regards

	Radovan Skolnik
    by Radovan Skolnik - 05:41 - 28 Jun 2023

    2 replies 2 replies

    • Re: Palette management in the warehouse 
      Hi David,

thanks for info. I somehow got misleaded with packagings where they say in the docs: "In Odoo, packagings are used for indicative purposes on sales/purchase orders and inventory transfers." Now I see packages and packagings are two different things. Will check them out. 

Best regards

	Radovan Skolnik

On streda 28. júna 2023 18:02:42 CEST David Vidal wrote:

> This very much how the core packages work (model stock.quant.package).

> Although the workflows for this maybe aren't the most intuitive.

> 

> 

> El mié, 28 jun 2023 a las 17:42, Radovan Skolnik

> (<notifications@odoo-community.org>) escribió:

> 

> Hello,

> 

> hope this is not a stupid question. Customer would like to have something

> like this:

> 

> *) a palette with multiple different lots (batches) of single product (or

> even with different products)

> *) the palette can be placed in a (palatte) location/position in the

> warehouse *) you can remove things from palette (put them in outgoing

> shipments for example)

> *) when all the contents of the palette is gone, the palette should

> "disappear" as well and effectively make the location/position free.

> 

> Has anyone dealt with something like this? Any pointers I could follow?

> 

> Thank you very much. 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 - 07:21 - 28 Jun 2023
    • Re: Palette management in the warehouse
      This very much how the core packages work (model stock.quant.package). Although the workflows for this maybe aren't the most intuitive.

      El mié, 28 jun 2023 a las 17:42, Radovan Skolnik (<notifications@odoo-community.org>) escribió:
      Hello,

hope this is not a stupid question. Customer would like to have something like 
this:

*) a palette with multiple different lots (batches) of single product (or even 
with different products)
*) the palette can be placed in a (palatte) location/position in the warehouse
*) you can remove things from palette (put them in outgoing shipments for 
example)
*) when all the contents of the palette is gone, the palette should 
"disappear" as well and effectively make the location/position free.

Has anyone dealt with something like this? Any pointers I could follow?

Thank you very much. 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 David Vidal - 06:01 - 28 Jun 2023
  • Publish accounting entries + budget on the website
    Hello,

    We have a public organization who wants to publish all their accounting data including the account budgets on the website in real time (not in the portal but on the website - the module would be like website_account and website_account_budget)

    Do you know something that can help ?

    Thanks in advance
    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
    by Cyril VINH-TUNG - 06:30 - 28 Jun 2023
  • Routes, trucks and gates
    Hello,

    I have a customer using Odoo 16 to manage his logistics operations: they have 2 warehouses with 12 gates, a fleet of 30 trucks of different sizes and a number of routes.

    I checked the transport repo but didn't find much there. Am I missing something? 

    Any suggestion that could help?

    Thank you
    --
    Maxime Chambreuil
    Desde mi móvil
    by Maxime Chambreuil - 05:21 - 28 Jun 2023

    2 replies 2 replies

  • Proposing myself as Procurement & Purchase PSC
    Hi Community,

    I'd like to become a PSC member for Procurement & Purchase. (https://odoo-community.org/psc-teams/procurement-purchase-12).

    My team and me, we are active contributors of the OCA. I think that some extra help is always welcome. (https://github.com/HaraldPanten).

    Thanks!

    --


     

    Harald Panten López

    CEO

    Sygel Technology S.L

    		 
    		+34 613 04 76 66
    		harald.panten@sygel.es
    		https://www.sygel.es
    		C/ Àlaba 61, 5ª planta, 08005, Barcelona
     
     
     
    by Harald Panten Lopez - 12:16 - 27 Jun 2023

    14 replies 14 replies

  • request to join psc of cooperative

    hello,

    i would like to join the psc of the cooperative repository as well as propose my colleague carmen bianca bakker as member also. we’ve worked on migrating several modules from 12.0 to 14.0 as well as move (and rename) the modules from coopiteasy/vertical-cooperative to there. we’re currently working on making the cooperator module multi-company compatible. my github username is huguesdk and carmen’s is carmenbianca.

    note: the “send a membership request” button on the “contribute” page of the website references the address contribute@odoo-community.org. shouldn’t it be contributors@?

    cheers,

    hugues

    by hugues de keyzer - 06:25 - 21 Jun 2023

    6 replies 6 replies

  • Question regarding the Community Discuss functionnality
    Hi Community,

    I'm running v16 community version and I'm wondering what is the technology hiding behind the live discuss feature :

    I didn't succeed to find out if it relies on an external dependency or ant IAP service.

    Any feedback will be appreciated,

    Regards

    Vertical seprator

    Florent THOMAS

    ☎ +33 972 457 755
    ✉ florent.thomas@mind-and-go.com

    Mind & Go
    14, Rue Pierre Cartelet | 66000 PERPIGNAN

    Logo Mind And Go Facebook Mind And Go Twitter Mind And Go LinkedIn Mind And Go
    by Florent THOMAS - 06:46 - 18 Jun 2023

    1 attachments 1 attachments

    393565

    5 replies 5 replies

  • Proposing myself as Tools PSC

    Hi all,

    I like to become member of the "Tools PSC Team". (https://odoo-community.org/psc-teams/tools-30). My contributions in this area:

    - Funder of interface-github and odoo-module-migrator repositories

    - I have proposed the following modules to the community : auth_admin_passkey, module_analysis, module_change_auto_install, server_action_navigate, pos_environment, user_all_groups and deeply refactored : server_action_mass_edit (formely "mass_editing")

    Thanks for your attention.

    -- 
Sylvain LE GAL
- GRAP, service informatique
- 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
- Astreinte : 06.81.85.61.43 // informatique@grap.coop
    by Sylvain LE GAL - 11:10 - 16 Jun 2023

    21 replies 21 replies

    • Re: Proposing myself as Tools PSC 
      +1

Le vendredi 16 juin 2023 à 21:12 +0000, Sylvain LE GAL (GRAP) a écrit :

>  

> Hi all,

>  

> I like to become member of the "Tools PSC Team". (https://odoo-community.org/psc-teams/tools-30). My contributions in this area: 

>  

>  

> - Funder of interface-github and odoo-module-migrator repositories

>  

> - I have proposed the following modules to the community : auth_admin_passkey, module_analysis, module_change_auto_install, server_action_navigate, pos_environment, user_all_groups and deeply refactored : server_action_mass_edit (formely "mass_editing")

>  

> Thanks for your attention.

>  

>  -- 

> Sylvain LE GAL

> - GRAP, service informatique

> - 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17

> - Astreinte : 06.81.85.61.43 // informatique@grap.coop

>  

> _______________________________________________

>                         Mailing-List: https://odoo-community.org/groups/contributors-15

>                         Post to: mailto:contributors@odoo-community.org

>                         Unsubscribe: https://odoo-community.org/groups?unsubscribe

>                     


-- 
Carmen Bianca BAKKER <carmen@coopiteasy.be>
Coop IT Easy
      by Carmen Bianca Bakker - 01:33 - 23 Jun 2023
    • Re: Proposing myself as Tools PSC

      Thanks !

      It works.


      Le 19/06/2023 à 11:21, Enric Tobella Alomar a écrit :
      +1
       
      I added you on the group. You should receive the notification soon
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
      From: "Mignon, Laurent" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Mon, 19 Jun 2023 08:31:57 -0000
      Subject: Re: Proposing myself as Tools PSC
       
      +1
       
      On Mon, Jun 19, 2023 at 9:47 AM Jairo Llopis <notifications@odoo-community.org> wrote:
      El vie, 16 de jun de 2023 a las 21:12:01 PM, Sylvain LE GAL (GRAP) <notifications@odoo-community.org> escribió:
      I like to become member of the "Tools PSC Team"
       
      +1
      _______________________________________________
      Mailing-List: https://odoo-community.org/groups/contributors-15
      Post to: mailto:contributors@odoo-community.org
      Unsubscribe: https://odoo-community.org/groups?unsubscribe




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.

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

      -- 
Sylvain LE GAL
- GRAP, service informatique
- 3 Grande rue des Feuillants 69001 LYON, 09.72.32.33.17
- Astreinte : 06.81.85.61.43 // informatique@grap.coop
      by Sylvain LE GAL - 06:21 - 22 Jun 2023
    • Re: Proposing myself as Tools PSC
      +1
       
      I added you on the group. You should receive the notification soon
       
      Enric Tobella Alomar
      Av. J. V. Foix 63
      08034 Barcelona
      Tlf.    932 522 522 (Ext. 9611)
       
      From: "Mignon, Laurent" <notifications@odoo-community.org>
      To: "Contributors" <contributors@odoo-community.org>
      Date: Mon, 19 Jun 2023 08:31:57 -0000
      Subject: Re: Proposing myself as Tools PSC
       
      +1
       
      On Mon, Jun 19, 2023 at 9:47 AM Jairo Llopis <notifications@odoo-community.org> wrote:
      El vie, 16 de jun de 2023 a las 21:12:01 PM, Sylvain LE GAL (GRAP) <notifications@odoo-community.org> escribió:
      I like to become member of the "Tools PSC Team"
       
      +1
      _______________________________________________
      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




      Tanto este mensaje como los documentos que, en su caso, lleve como anexos,
      pueden contener información reservada y/o confidencial, destinada exclusivamente
      para el uso del destinatario o la persona responsable de entregarlo al mismo,
      estando su uso no autorizado prohibido legalmente.
      Su contenido no constituye un compromiso para Creu Blanca (la empresa remitente)
      salvo ratificación escrita por ambas partes. En caso de su recepción por error,
      rogamos nos lo comunique por igual vía, se abstenga de realizar copias del mensaje
      o documentos adjuntos, remitirlo o facilitarlo a un tercero, y proceda en su defecto,
      a su eliminación.
      by Enric Tobella Alomar - 11:20 - 19 Jun 2023
    • Re: Proposing myself as Tools PSC
      +1

      On Mon, Jun 19, 2023 at 9:47 AM Jairo Llopis <notifications@odoo-community.org> wrote:
      El vie, 16 de jun de 2023 a las 21:12:01 PM, Sylvain LE GAL (GRAP) <notifications@odoo-community.org> escribió:
      I like to become member of the "Tools PSC Team"

      +1

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

      by Laurent Mignon - 10:30 - 19 Jun 2023
    • Re: Proposing myself as Tools PSC
      El vie, 16 de jun de 2023 a las 21:12:01 PM, Sylvain LE GAL (GRAP) <notifications@odoo-community.org> escribió:
      I like to become member of the "Tools PSC Team"

      +1
      by Jairo Llopis - 09:46 - 19 Jun 2023

  • Documentation on Management System module and its related sub-modules

    I was hoping if someone here can help or guide me in gaining any kind of detailed documentation / user guide for the OCA module https://github.com/OCA/management-system and all its sub-modules so that it gives a good understanding on how to best install and use it.
    Thank you in anticipation

    by Ketan Chandaria - 05:40 - 16 Jun 2023

    2 replies 2 replies

  • tax_base_amount going to be deprecated. Anyone else using it?
    Hello Everyone.
    It seams that odoo is going to deprecate the not so used field tax_base_amount 
    The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

    Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

    We've some use cases where for us it's practical to be able to create tax aml's
    Some examples:
    • bank statements.
      • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
        • check deposit (cash in)
        • expense fee (cash out)
        • tax 1 (based on the expense fee, cash out)
        • tax 2 (based on the expense fee, cash out)
      • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
    • special invoice taxes
      • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
      • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
      • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
    • supplier bills
      • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
      • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
      • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
    • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
      • This is the ideal for us

    #

    account

    tax_ids

    tax_id

    debit

    credit

    tax_base_amount

    1

    Suppliers



    1210



    2

    VAT withholding


    VAT withholding


    21

    210

    3

    Proffits withholding type 1


    Proffits withholding type 1


    60

    600

    4

    Proffits withholding type 2


    Proffits withholding type 2


    80

    400

    5

    Cash




    1049


      • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

    #

    account

    tax_ids

    tax_id

    debit

    credit

    tax_base_amount

    1

    Suppliers



    1210



    2

    VAT withholding


    VAT withholding


    21

    210

    3

    Profits withholding type 1


    Profits withholding type 1


    60

    600

    4

    Profits withholding type 2


    Profits withholding type 2


    80

    400

    5

    Cash




    1049


    6

    Base for VAT withholding

    VAT withholding


    210



    7

    Negative for base VAT withholding




    210


    8

    Base for Profits withholding type 1

    Profits withholding type 1


    600



    9

    Negative for Profits withholding type 1




    600


    10

    Base for Profits withholding type 2

    Profits withholding type 2


    400



    11

    Negative for Profits withholding type 2




    400


    • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

    Summarizing.
    • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
    • IMHO
      • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
      • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
      • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
    Anyone else share these thoughts or can show me that my ideas are wrong?
    Thanks!

    Ing. Juan José Scarafía

    (+54 9 341) 3 278039

    twitter: @jjscarafia

    github: @jjscarafia

    by Juan José Scarafía - 10:51 - 8 Jun 2023

    1 attachments 1 attachments

    asda.png

    5 replies 5 replies

    • Re: tax_base_amount going to be deprecated. Anyone else using it?
      Hi Nhomar!
      I don't have a PR. It was a conversation with Odoo team (localizations PO) + developer. 

      The "rationale" that I understood from the conversation was:
      • nowadays, on odoo standard, there is no usage of the tax_base_amount except on the tax audit report view
      • on odoo reports, they are considering as the tax_base_amount the amount of the base lines where those taxes where applied. so there could be some difference between the stored tax_base_amount and the one used on reports
      • my opinions: 
        • instead of fixing/improving it, just removing seems easier
        • in countries where the tax is send globally, tax_base_amount on the tax line it self makes lot of sense (simpler code, less lines, less complexity, less computations)
        • in countries where the taxes are computed and reported by line, may be something different is needed 
      Example of odoo report where they are not using the tax_base_amount but computing it
      image.png

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia



      El mar, 13 jun 2023 a la(s) 03:52, Nhomar Hernández (notifications@odoo-community.org) escribió:

      Can you share the PR where the deprecation is happening?

      the complementary account moves are an actual error (in fact if you combine them with the extra 2 lines that every line generate in the chase basis this will be a huge issue) 

      In a few thousand invoices company (not that big) explain those extra moves will be complicated, I can not understand how 1 field vs thousands of lines just for the sake of a consistency that is and should be there is better.

      But anyways before make any conclusion.

      Do you have the PR?
      Do you have the conversation where Odoo's explains the rationale?

      Regards.

      El jue, 8 jun 2023 a la(s) 14:52, Juan José Scarafía (notifications@odoo-community.org) escribió:
      Hello Everyone.
      It seams that odoo is going to deprecate the not so used field tax_base_amount 
      The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

      Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

      We've some use cases where for us it's practical to be able to create tax aml's
      Some examples:
      • bank statements.
        • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
          • check deposit (cash in)
          • expense fee (cash out)
          • tax 1 (based on the expense fee, cash out)
          • tax 2 (based on the expense fee, cash out)
        • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
      • special invoice taxes
        • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
        • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
        • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
      • supplier bills
        • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
        • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
        • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
      • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
        • This is the ideal for us

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Proffits withholding type 1


      Proffits withholding type 1


      60

      600

      4

      Proffits withholding type 2


      Proffits withholding type 2


      80

      400

      5

      Cash




      1049


        • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Profits withholding type 1


      Profits withholding type 1


      60

      600

      4

      Profits withholding type 2


      Profits withholding type 2


      80

      400

      5

      Cash




      1049


      6

      Base for VAT withholding

      VAT withholding


      210



      7

      Negative for base VAT withholding




      210


      8

      Base for Profits withholding type 1

      Profits withholding type 1


      600



      9

      Negative for Profits withholding type 1




      600


      10

      Base for Profits withholding type 2

      Profits withholding type 2


      400



      11

      Negative for Profits withholding type 2




      400


      • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

      Summarizing.
      • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
      • IMHO
        • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
        • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
        • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
      Anyone else share these thoughts or can show me that my ideas are wrong?
      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia

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



      --

      Nhomar G Hernández

      Vauxoo | CEO

      ¡Construyamos algo genial!
      Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

      México · Venezuela · Costa Rica · Perú

      phone nhomar@vauxoo.com phone vauxoo.com/contactus  

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

      by Juan José Scarafía - 04:35 - 13 Jun 2023

      1 attachments 1 attachments

      image.png
    • Re: tax_base_amount going to be deprecated. Anyone else using it?

      Can you share the PR where the deprecation is happening?

      the complementary account moves are an actual error (in fact if you combine them with the extra 2 lines that every line generate in the chase basis this will be a huge issue) 

      In a few thousand invoices company (not that big) explain those extra moves will be complicated, I can not understand how 1 field vs thousands of lines just for the sake of a consistency that is and should be there is better.

      But anyways before make any conclusion.

      Do you have the PR?
      Do you have the conversation where Odoo's explains the rationale?

      Regards.

      El jue, 8 jun 2023 a la(s) 14:52, Juan José Scarafía (notifications@odoo-community.org) escribió:
      Hello Everyone.
      It seams that odoo is going to deprecate the not so used field tax_base_amount 
      The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

      Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

      We've some use cases where for us it's practical to be able to create tax aml's
      Some examples:
      • bank statements.
        • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
          • check deposit (cash in)
          • expense fee (cash out)
          • tax 1 (based on the expense fee, cash out)
          • tax 2 (based on the expense fee, cash out)
        • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
      • special invoice taxes
        • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
        • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
        • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
      • supplier bills
        • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
        • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
        • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
      • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
        • This is the ideal for us

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Proffits withholding type 1


      Proffits withholding type 1


      60

      600

      4

      Proffits withholding type 2


      Proffits withholding type 2


      80

      400

      5

      Cash




      1049


        • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Profits withholding type 1


      Profits withholding type 1


      60

      600

      4

      Profits withholding type 2


      Profits withholding type 2


      80

      400

      5

      Cash




      1049


      6

      Base for VAT withholding

      VAT withholding


      210



      7

      Negative for base VAT withholding




      210


      8

      Base for Profits withholding type 1

      Profits withholding type 1


      600



      9

      Negative for Profits withholding type 1




      600


      10

      Base for Profits withholding type 2

      Profits withholding type 2


      400



      11

      Negative for Profits withholding type 2




      400


      • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

      Summarizing.
      • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
      • IMHO
        • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
        • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
        • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
      Anyone else share these thoughts or can show me that my ideas are wrong?
      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia

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



      --

      Nhomar G Hernández

      Vauxoo | CEO

      ¡Construyamos algo genial!
      Cel: +52 (477) 393.3942 | Telegram: nhomar | Twitter: @nhomar

      México · Venezuela · Costa Rica · Perú

      phone nhomar@vauxoo.com phone vauxoo.com/contactus  

      by Nhomar Hernández - 08:51 - 13 Jun 2023
    • Re: tax_base_amount going to be deprecated. Anyone else using it?
      Hi Juan, 

      I'm also from Argentina so we use it too. I agree with all your points and I really don't like the suggested "way" of doing it that Odoo is proposing. 
      The deprecation of this field is a final decision? I think we will need to find a new approach to this, since all those dummy lines are confusing even for accounting people. 

      On Thu, Jun 8, 2023 at 5:52 PM Juan José Scarafía <notifications@odoo-community.org> wrote:
      Hello Everyone.
      It seams that odoo is going to deprecate the not so used field tax_base_amount 
      The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

      Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

      We've some use cases where for us it's practical to be able to create tax aml's
      Some examples:
      • bank statements.
        • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
          • check deposit (cash in)
          • expense fee (cash out)
          • tax 1 (based on the expense fee, cash out)
          • tax 2 (based on the expense fee, cash out)
        • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
      • special invoice taxes
        • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
        • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
        • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
      • supplier bills
        • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
        • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
        • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
      • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
        • This is the ideal for us

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Proffits withholding type 1


      Proffits withholding type 1


      60

      600

      4

      Proffits withholding type 2


      Proffits withholding type 2


      80

      400

      5

      Cash




      1049


        • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers



      1210



      2

      VAT withholding


      VAT withholding


      21

      210

      3

      Profits withholding type 1


      Profits withholding type 1


      60

      600

      4

      Profits withholding type 2


      Profits withholding type 2


      80

      400

      5

      Cash




      1049


      6

      Base for VAT withholding

      VAT withholding


      210



      7

      Negative for base VAT withholding




      210


      8

      Base for Profits withholding type 1

      Profits withholding type 1


      600



      9

      Negative for Profits withholding type 1




      600


      10

      Base for Profits withholding type 2

      Profits withholding type 2


      400



      11

      Negative for Profits withholding type 2




      400


      • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

      Summarizing.
      • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
      • IMHO
        • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
        • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
        • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
      Anyone else share these thoughts or can show me that my ideas are wrong?
      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia

      _______________________________________________
      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:11 - 13 Jun 2023
    • Re: tax_base_amount going to be deprecated. Anyone else using it?
      Hi Richard! 
      Thanks, I believe we've a similar need. On imports we register "purchase bills" for the import import clearance where you only pay taxes.
      What we're doing till now is adding invoice lines that represent each base amount with the corresponding taxes and later on negative lines to balance the.
      Indeed doing what you said could work but we wouldn't have the tax_base_amout (and we needed for later tax declaration)

      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia



      El jue, 8 jun 2023 a la(s) 23:01, Richard deMeester (notifications@odoo-community.org) escribió:

      Hi Juan,

      We used to generate tax lines for import charges as a tax only line.

      When ordering products from foreign sources, a tax may be applied by the customs at time of import.

      This tax is payable directly to the point of import, and is not associated with any lines.

      We introduced a change to l10n_au (now included in Odoo enterprise) which defines an import tax:

      au_tax_purchase_taxable_import

      Which has is a tax included tax with a 100000000000 percent value.

      This effectively allows a line on the invoice for a large figure, and with rounding, Odoo determines the base value as being the fraction of a cent and the whole amount ends up as tax, and then ends up in reporting, linked to an invoice line that has no real value.

      Hope this gives you some ideas.

      Richard





       

       

      Kind Regards 

       

       

      A close up of a sign Description automatically generated 

       

      Richard deMeester 

      Senior Development Analyst 

       

       

       

       

      T: (03) 9135 1900 | M: 0403 76 76 76 | A: Bld 10/435 Williamstown Road, Port Melbourne, 3207 

       

      A picture containing monitor, screen, holding, person Description automatically generated 

       

       
      MAKING GROWTH THROUGH TECHNOLOGY EASY 

       
      Notice: This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not disclose or use the information in this email in any way. If you have received this email in error please notify the sender. Although reasonable precautions have been taken to ensure no viruses are present in this email, no responsibility is accepted by WilldooIT Pty Ltd or its related entities for any loss or damage arising from the use of this email or attachments. Any views expressed in this email or file attachments are those of the individual sender only, unless expressly stated to be those of WilldooIT Pty Ltd  ABN 85 006 073 052 or any of its related entities. 

       

       


      From: Juan José Scarafía <notifications@odoo-community.org>
      Sent: Friday, 9 June 2023 6:52 AM
      To: Contributors <contributors@odoo-community.org>
      Subject: tax_base_amount going to be deprecated. Anyone else using it?
       
      Hello Everyone.
      It seams that odoo is going to deprecate the not so used field tax_base_amount 
      The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

      Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

      We've some use cases where for us it's practical to be able to create tax aml's
      Some examples:
      • bank statements.
        • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
          • check deposit (cash in)
          • expense fee (cash out)
          • tax 1 (based on the expense fee, cash out)
          • tax 2 (based on the expense fee, cash out)
        • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
      • special invoice taxes
        • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
        • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
        • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
      • supplier bills
        • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
        • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
        • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
      • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
        • This is the ideal for us

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers

      1210

      2

      VAT withholding

      VAT withholding

      21

      210

      3

      Proffits withholding type 1

      Proffits withholding type 1

      60

      600

      4

      Proffits withholding type 2

      Proffits withholding type 2

      80

      400

      5

      Cash


      1049
        • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers

      1210

      2

      VAT withholding

      VAT withholding

      21

      210

      3

      Profits withholding type 1

      Profits withholding type 1

      60

      600

      4

      Profits withholding type 2

      Profits withholding type 2

      80

      400

      5

      Cash


      1049

      6

      Base for VAT withholding

      VAT withholding

      210

      7

      Negative for base VAT withholding


      210

      8

      Base for Profits withholding type 1

      Profits withholding type 1

      600

      9

      Negative for Profits withholding type 1


      600

      10

      Base for Profits withholding type 2

      Profits withholding type 2

      400

      11

      Negative for Profits withholding type 2


      400
      • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

      Summarizing.
      • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
      • IMHO
        • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
        • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
        • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
      Anyone else share these thoughts or can show me that my ideas are wrong?
      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia

      _______________________________________________
      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 Juan José Scarafía - 10:00 - 10 Jun 2023
    • Re: tax_base_amount going to be deprecated. Anyone else using it?

      Hi Juan,

      We used to generate tax lines for import charges as a tax only line.

      When ordering products from foreign sources, a tax may be applied by the customs at time of import.

      This tax is payable directly to the point of import, and is not associated with any lines.

      We introduced a change to l10n_au (now included in Odoo enterprise) which defines an import tax:

      au_tax_purchase_taxable_import

      Which has is a tax included tax with a 100000000000 percent value.

      This effectively allows a line on the invoice for a large figure, and with rounding, Odoo determines the base value as being the fraction of a cent and the whole amount ends up as tax, and then ends up in reporting, linked to an invoice line that has no real value.

      Hope this gives you some ideas.

      Richard





       

       

      Kind Regards 

       

       

      A close up of a sign Description automatically generated 

       

      Richard deMeester 

      Senior Development Analyst 

      richard.demeester@willdooit.com 

       

       

       

       

      T: (03) 9135 1900 | M: 0403 76 76 76 | A: Bld 10/435 Williamstown Road, Port Melbourne, 3207 

       

      A picture containing monitor, screen, holding, person Description automatically generated 

       

       
      MAKING GROWTH THROUGH TECHNOLOGY EASY 

       
      Notice: This email and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to which they are addressed. If you are not the intended recipient, you may not disclose or use the information in this email in any way. If you have received this email in error please notify the sender. Although reasonable precautions have been taken to ensure no viruses are present in this email, no responsibility is accepted by WilldooIT Pty Ltd or its related entities for any loss or damage arising from the use of this email or attachments. Any views expressed in this email or file attachments are those of the individual sender only, unless expressly stated to be those of WilldooIT Pty Ltd  ABN 85 006 073 052 or any of its related entities. 

       

       


      From: Juan José Scarafía <notifications@odoo-community.org>
      Sent: Friday, 9 June 2023 6:52 AM
      To: Contributors <contributors@odoo-community.org>
      Subject: tax_base_amount going to be deprecated. Anyone else using it?
       
      Hello Everyone.
      It seams that odoo is going to deprecate the not so used field tax_base_amount 
      The main reason odoo is going to do so is that now it may be inconsistent on how odoo is computing the base amount for a tax (the base for Odoo is always the sum of the balance of the aml's where the tax is applied on the tax_ids field)

      Together with that field being deprecated, the idea behind is that there shouldn't be any aml (account.move.line) with tax_line_id that was not originated by another aml with tax_ids

      We've some use cases where for us it's practical to be able to create tax aml's
      Some examples:
      • bank statements.
        • on many banks operations (for eg. check deposits) we have expenses + taxes associated. So for on check deposit we may have 4 statement lines:
          • check deposit (cash in)
          • expense fee (cash out)
          • tax 1 (based on the expense fee, cash out)
          • tax 2 (based on the expense fee, cash out)
        • On Odoo standard we're not able to reconcile that because we can't say that an statement line is 100% a tax In the odoo approach those two taxes should came from the tax being applied on the "expense fee"
      • special invoice taxes
        • we've some special invoice taxes where the base amount is not the subtotal of the invoice line but some specific computation (for ex. is the vat of that line)
        • in that use case, we're storing the calculated base amount on tax_base_amount. Considering that the base amount is the sum of the subtotales of the lines where the tax is linked, is not correct.
        • On master (and I believe 16 two). Odoo has a similar use case for belgium. When you offer a cash discount, no matter if the customer use it or not, the vat is computed on the discounted price. That's why there is a new option on the payment terms and, only for having the right base amount on the invoice, odoo is creating virtual lines (check attachment)
      • supplier bills
        • It's really common to receive supplier bills with some specific taxes that are totalized and without information on which are the base lines.
        • in those use cases creating just a tax line (as it was possible on v12-) would be really handy. Nowadays we're adding that tax on the first invoice line (arbitrary) and then editing the amount on the subtotal section. The computed base amount by odoo on reports doesn't represent anything.
        • For us it would make much more sense to add the tax on subtotal by choosing: tax, base amount, and amount. And that would create the aml without any need of linked base lines with tax_ids
      • We also have some specific needs related to payment withholdings. Summarizing, when you pay or get paid you receive or apply different kind of withholdings for different amounts.
        • This is the ideal for us

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers

      1210

      2

      VAT withholding

      VAT withholding

      21

      210

      3

      Proffits withholding type 1

      Proffits withholding type 1

      60

      600

      4

      Proffits withholding type 2

      Proffits withholding type 2

      80

      400

      5

      Cash


      1049
        • This is the odoo proposal (to have all the base amounts computed by the tax base lines). Lines 6 till 11 are dummy lines just for the base amounts

      #

      account

      tax_ids

      tax_id

      debit

      credit

      tax_base_amount

      1

      Suppliers

      1210

      2

      VAT withholding

      VAT withholding

      21

      210

      3

      Profits withholding type 1

      Profits withholding type 1

      60

      600

      4

      Profits withholding type 2

      Profits withholding type 2

      80

      400

      5

      Cash


      1049

      6

      Base for VAT withholding

      VAT withholding

      210

      7

      Negative for base VAT withholding


      210

      8

      Base for Profits withholding type 1

      Profits withholding type 1

      600

      9

      Negative for Profits withholding type 1


      600

      10

      Base for Profits withholding type 2

      Profits withholding type 2

      400

      11

      Negative for Profits withholding type 2


      400
      • We also know that in Brazil and some other countries, there are some webservices that returns the base amounts and taxes you need to apply to an invoice, Si in those use cases also the base amount of the tax may not be the sum of subtotals where the tax is applied

      Summarizing.
      • Odoo is working on removint tax_base_amount and enforcing that every aml that represents a tax should be created by some aml with that tax. The base amount of the tax would be the sum of the base lines
      • IMHO
        • That approach could work but requires a lot of dummy lines (plus and negative) to represent all the possible combinations of tax base amounts. This is not only for performance but also for db size, code complexity and bank reconciliation.
        • to keep and improve, or at lease allow, the possibility of having amls taxes where the tax_base_amount represents the base amount, and the balance represents the tax amount, seems an easy to understand and flexible way to deal with base amounts on many different use cases
        • Lastly, I also like the tax_base_amount field on the aml's as it's really easy to audit and check. On one record (the aml) you have all the data you need related to a tax.
      Anyone else share these thoughts or can show me that my ideas are wrong?
      Thanks!

      Ing. Juan José Scarafía

      (+54 9 341) 3 278039

      twitter: @jjscarafia

      github: @jjscarafia

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

      by "Richard deMeester" <richard.demeester@willdooit.com> - 04:01 - 9 Jun 2023

      5 attachments 5 attachments

      Outlook-rme5do3y.png
      Outlook-A picture .png
      Outlook-beioq42j.png
      Outlook-snlg1gyb.png
      Outlook-A close up.png
  • OCA Days 2023 - Registrations, Call for Speakers and Functional Survey
    Hello OCA Contributors,

    The exciting news is that the OCA registrations are now live.

    We also have our call for speakers open - we want to hear from everyone! Do you have an awesome tutorial/training, case study, module update etc you want to share with the community? Send your proposals through here.

    This year we are really wanting to encourage more functional people to attend and get the most out of this time together. We are creating a functional track to support this alongside our usual great talks.

    The OCA Functional Workgroup have created a survey for people interested in the functional side of things and would love to hear from you - please fill in the survey here. Let us know what you are interested in learning about and how we can help you.

    We are looking forward to seeing you in November.
    Rebecca

    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 04:40 - 2 Jun 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

    9 replies 9 replies

    • RE: Issues with outgoing email management in Odoo

      And finally

       

      https://github.com/OCA/social/tree/15.0/mail_composer_cc_bcc

       

      Thank you!

       

       

      De: Lois Rilo Antelo <notifications@odoo-community.org>
      Enviado el: jueves, 1 de junio de 2023 11:32
      Para: Contributors <contributors@odoo-community.org>
      Asunto: 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 Rafael Blasco (Moduon) - 10:51 - 26 Jul 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

  • 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

    3 replies 3 replies