Archives
Contributors
-
Re: New repository OCA/sign
Yes indeedI cloned the repo yesterday and I'm gonna push soon.But there will be hard work to be OCA compliant :-/
You're welcome to help...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.comLe ven. 9 juin 2023, 21:52, Simon Maillard <notifications@odoo-community.org> a écrit :On 21/04/2023 18:31, Cyril VINH-TUNG wrote: > Hello, > On our side we developed integration to Lex Persona > (https://www.lex-persona.com/plateforme-de-signature-electronique/ > <https://www.lex-persona.com/plateforme-de-signature-electronique/>) > which is a french API to sign documents on the fly. Hi Cyril, I will start working on the electronic signature in the next few weeks, maybe with lex persona. Do you plan to open source your work? Regard, Simon -- Simon Maillard simon@ogesta.fr
_______________________________________________
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:06 - 10 Jun 2023 -
Re: New repository OCA/sign
On 21/04/2023 18:31, Cyril VINH-TUNG wrote: > Hello, > On our side we developed integration to Lex Persona > (https://www.lex-persona.com/plateforme-de-signature-electronique/ > <https://www.lex-persona.com/plateforme-de-signature-electronique/>) > which is a french API to sign documents on the fly. Hi Cyril, I will start working on the electronic signature in the next few weeks, maybe with lex persona. Do you plan to open source your work? Regard, Simon -- Simon Maillard simon@ogesta.fr
by Simon Maillard - 09:51 - 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
T: (03) 9135 1900 | M: 0403 76 76 76 | A: Bld 10/435 Williamstown Road, Port Melbourne, 3207
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_amountThe 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'sSome 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!
_______________________________________________
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 -
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_amountThe 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_idsWe've some use cases where for us it's practical to be able to create tax aml'sSome 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!
by Juan José Scarafía - 10:51 - 8 Jun 2023 -
Re: [FIX]:Weblate - use po file download/upload - revisions
Hi Stéphane,did you give a look to mine and Sergio replies (i attached them below)?Last month, as italian community, we had the Odoo Italia Days in Milan. We talked with other people interested in setting up a better way to manage translations, at least for italian language.We met Simone Orsi, OCA member, that support this idea.In fact we think that what we are looking for could be useful for all language teams.If you, or someone else, can invest some time to configure Weblate to activate the requested features, we can test it and give a fast feedback.Obviously, we welcome all people willing to join the project.Thanks for your time and help.StefanoDa "Stefano Consolaro" stefano.consolaro@mymage.itA contributors@odoo-community.orgCcData Mon, 23 Jan 2023 08:40:30 +0100Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
I give my reply for italian language/community:
> Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?
As far I know we don't have problems of a misuse of the tool. What we noticed is that the "need" and the "hurry" to have the translations, or a lack in the definition of a glossary for common terms, or the contributions of a new entry (like in part I am), goes to some incorrect or not so pertinent translations.
> What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.> How to make sure translation proposals are not stuck for too long waiting for review?
Hm, here I don't know what to say, can't be done in the "same way" that PSC are nominated for repository in GitHub?
Yes, this is a weakness. I don't know if it can be done and how, but I'd like to have a system in which the reviewed terms can be changed only by reviewers and other terms can be changed (and then loaded) by anyone (view *).
> Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.
Absolutely yes: the lack of resources is a problem and (*) I prefer that a thing is done now than perfect never. So the activation of the review process should be decided by each community.Thanks for expanding the discussion, I hope others will join.Da "Sergio Zanchetta" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Mon, 23 Jan 2023 10:36:56 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisionsIl giorno dom 22 gen 2023 alle ore 11:27 Stéphane Bidoul <notifications@odoo-community.org> ha scritto:We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.Yes, you are right. :-)Below, as italian community in addition to Stefano answers, you can find a proposal.Here are a few questions that come to mind. There might be more.- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?The second one. Incorrect/low level translations, not only new, that don't follow current community guidelines and glossaries (language specific).- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.- How to make sure translation proposals are not stuck for too long waiting for review?I would replicate Transifex structure or similar, if possible. Here is a proposal:- Anyone can be accepted as translator, strings are pushed as soon as translated. (or on a periodic basis)- There is a reviewer role, reviewed strings are freezed and can't be changed by translators.- The coordinator role has reviewer power and can appoint translators as reviewers.The coordinator could be nominated by each localization repository PSC. (l10n-*)He would be in charge of appointing reviewers evaluating the quality of their translations over time, based on guidelines/glossary compliance.- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.Sure, I add that not all communities have translation guidelines. [*][*] e.g. italian guidelines (and glossaries) https://www.odoo-italia.org/documentazione/14.0/traduzioni.htmlDa "Stéphane Bidoul" notifications@odoo-community.orgA "Contributors" contributors@odoo-community.orgCcData Sun, 22 Jan 2023 10:27:40 -0000Oggetto Re: [FIX]:Weblate - use po file download/upload - revisions
We discussed a translation review mechanism before, I think, but IIRC we concluded we need a process first.Here are a few questions that come to mind. There might be more.- Clearly define the problem we are attempting to solve? For instance, Is it "vandalism" of existing translations (this could be solved by banning offenders)? Or is it incorrect/low quality new translations (which can be fixed easily after the fact, I suppose)? Or something else?- What would be the process to appoint/elect reviewers? Currently we accept anyone who asks.- How to make sure translation proposals are not stuck for too long waiting for review?- Should/can we enable the review process per language? This may be important as not all language communities have the resources to have dedicated reviewers.Best regards,-sbi
by Stefano Consolaro - 09:56 - 8 Jun 2023 -
Re: Google Analytics Universal to GA4 for versions < 15.0
Thank you so much David!Hope this message gets indexed in case anyone will face the same issue in the next month or so.Cheers
FrancescoIl giorno gio 1 giu 2023 alle ore 11:42 David Vidal <notifications@odoo-community.org> ha scritto:Have you consider using Google Tag Manager for the task?:OCA Module: https://odoo-community.org/shop/google-tag-manager-4427?search=tag_manager#attr=23272David VidalTecnativaEl vie, 26 may 2023 a las 18:37, Francesco Foresti (<notifications@odoo-community.org>) escribió:Hi,has anyone worked on a module to implement the change described here:Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.
Which according to this post, amounts toinsert 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!_______________________________________________
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 Francesco Foresti - 04:26 - 5 Jun 2023 -
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 GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 04:40 - 2 Jun 2023 -
Re: Google Analytics Universal to GA4 for versions < 15.0
Have you consider using Google Tag Manager for the task?:OCA Module: https://odoo-community.org/shop/google-tag-manager-4427?search=tag_manager#attr=23272David VidalTecnativaEl vie, 26 may 2023 a las 18:37, Francesco Foresti (<notifications@odoo-community.org>) escribió:Hi,has anyone worked on a module to implement the change described here:Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.
Which according to this post, amounts toinsert 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!_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by David Vidal - 11:40 - 1 Jun 2023 -
Re: Issues with outgoing email management in Odoo
Cyril,Thanks for the insights, I will follow the discussion there to be notified if the work is finished.Kind regards,On Thu, Jun 1, 2023 at 10:58 AM Cyril VINH-TUNG <notifications@odoo-community.org> wrote:Hi LoisWe did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalitiesCheck final comment from rafael https://github.com/OCA/social/pull/855#issuecomment-1102348461We will definitely keep mail_body_notified_partnerBest 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.comLe 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 AlexWe 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 itWe 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'.We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55IMHO 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 partnersBest 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.comLe 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 AnteloERP 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 AnteloERP Consultant Manager at ForgeFlow S.L.
by Lois Rilo Antelo - 11:30 - 1 Jun 2023 -
Re: Issues with outgoing email management in Odoo
Hi LoisWe did not merge mail_body_notified_partner with mail_show_followers because they don't have same functionalitiesCheck final comment from rafael https://github.com/OCA/social/pull/855#issuecomment-1102348461We will definitely keep mail_body_notified_partnerBest 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.comLe 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 AlexWe 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 itWe 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'.We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55IMHO 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 partnersBest 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.comLe 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 AnteloERP 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 AlexWe 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 itWe 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'.We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55IMHO 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 partnersBest 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.comLe 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 AnteloERP Consultant Manager at ForgeFlow S.L.
by Lois Rilo Antelo - 09:39 - 1 Jun 2023 -
Re: Issues with outgoing email management in Odoo
Hi AlexWe 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 itWe 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'.We wrote a blog about it a few years ago (in french) https://www.easypme.com/blog/blog-5/post/le-futur-de-la-messagerie-d-entreprise-55IMHO 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 partnersBest 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.comLe mer. 31 mai 2023, 05:11, Alexandre Fayolle <notifications@odoo-community.org> a écrit :Hello everyone, This is a long standing topic in Odoo, but I'm facing it again with an unhappy customer. The way Odoo manages the sending of messages to followers of a "thread" by sending 1 email per follower, loosing all information from people who could have been in CC of an incoming mail, is really lame. Is there some knowledge hanging around about a way to change this so that Odoo would: * record the CC in a secondary field (say follower_cc_ids) for incoming message * promote a follower_cc to follower in case an incoming mail comes with this person in To: rather than CC: * send outgoing mails with 1 single mail with all followers in To: and follower_cc_ids in CC: I'm not super keen in touching this part of the Odoo source code, which I find quite obscure, and but maybe some have walked this path and could provide feedback, advice (or even maybe source code). Thanks for your help, -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Cyril VINH-TUNG - 08:26 - 31 May 2023 -
Re: Issues with outgoing email management in Odoo
This is open source, so you can contribute with that option in the module, via a configurable parameter. AFAIK, this is already being done by some contributor. Just look around.Regards.
by Pedro M. Baeza - 08:11 - 31 May 2023 -
Re: Issues with outgoing email management in Odoo
As far as I understand mail_tracking does insert a tracking image into emails [1]. This could be unwanted by receivers so I don't want the tracking feature but I want a solution for the issue described by Alexandre. Would it be reasonable to split the module into two or to make the tracking configurable? [1] https://github.com/OCA/social/blob/12.0/mail_tracking/models/mail_mail.py
by Jan Suhr - 08:01 - 31 May 2023 -
Re: Issues with outgoing email management in Odoo
Thanks, I'll check this. I had missed some part of the perimeter of that module and thought it was about tracking who opened a given message and the delivery status and such. Best regards Alexandre On 31/05/2023 17:17, Pedro M. Baeza wrote: > We handled this several years ago in `mail_tracking` module and it does > exactly what you want: show those in CC in replies, and suggest them on > next messages (even if they are not contacts yet). > > Regards. > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > <https://odoo-community.org/groups/contributors-15> > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > <https://odoo-community.org/groups?unsubscribe> > -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 05:45 - 31 May 2023 -
Re: Issues with outgoing email management in Odoo
We handled this several years ago in `mail_tracking` module and it does exactly what you want: show those in CC in replies, and suggest them on next messages (even if they are not contacts yet).Regards.
by Pedro M. Baeza - 05:16 - 31 May 2023 -
Issues with outgoing email management in Odoo
Hello everyone, This is a long standing topic in Odoo, but I'm facing it again with an unhappy customer. The way Odoo manages the sending of messages to followers of a "thread" by sending 1 email per follower, loosing all information from people who could have been in CC of an incoming mail, is really lame. Is there some knowledge hanging around about a way to change this so that Odoo would: * record the CC in a secondary field (say follower_cc_ids) for incoming message * promote a follower_cc to follower in case an incoming mail comes with this person in To: rather than CC: * send outgoing mails with 1 single mail with all followers in To: and follower_cc_ids in CC: I'm not super keen in touching this part of the Odoo source code, which I find quite obscure, and but maybe some have walked this path and could provide feedback, advice (or even maybe source code). Thanks for your help, -- Alexandre Fayolle Senior Software Engineer Tel : +33 4 58 48 20 30 Camptocamp France SAS 18 rue du Lac Saint André 73 370 Le Bourget-du-Lac France http://www.camptocamp.com
by Alexandre Fayolle - 05:11 - 31 May 2023 -
New poll in the forum: Add a "Jobs" forum category?
Please go to https://github.com/orgs/OCA/discussions/95 and share your thoughts.
by Jairo Llopis - 10:11 - 30 May 2023 -
Google Analytics Universal to GA4 for versions < 15.0
Hi,has anyone worked on a module to implement the change described here:
Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.
Which according to this post, amounts toinsert 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!
by Francesco Foresti - 06:31 - 26 May 2023 -
Re: Clear Customer Invoice and Vendor Bills
Hello Rafael,congratulations. That module is quite useful.I like it.Best regardsThorsten Vocks
openBIG.org
Dipl. Kaufmann (FH)
Porscheweg 4-6
49661 Cloppenburg
Phone: +49 4471 8409000
Fax: +49 4471 84090009
Mail: thorsten.vocks@openbig.org
Am Do., 25. Mai 2023 um 03:47 Uhr schrieb Rafael Blasco <notifications@odoo-community.org>:Sure
https://github.com/OCA/account-invoicing/tree/15.0/account_invoice_clearing
De: Daniel Guerrero <notifications@odoo-community.org>
Enviado el: domingo, 7 de mayo de 2023 1:57
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Clear Customer Invoice and Vendor BillsHello Rafael,
Did you develop the module?
Regards,
Daniel
From: Rafael Blasco <notifications@odoo-community.org>
Date: Sunday, 2 April 2023 at 1:47 PM
To: Contributors <contributors@odoo-community.org>
Subject: RE: Clear Customer Invoice and Vendor BillsThank you Yoshi but as I said Odoo CE has it for journal items in core.
IMHO account_neeting is not needed anymore in v14+ as can be done with “Automatic Entries” for selected Journal Items.
We will develop this UX Easy module for invoicing user in the next 2 weeks 😊
Best regards
Rafael
De: Yoshi Tashiro <notifications@odoo-community.org>
Enviado el: sábado, 1 de abril de 2023 14:22
Para: Contributors <contributors@odoo-community.org>
Asunto: Re: Clear Customer Invoice and Vendor Bills--
Yoshi Tashiro
On Sat, Apr 1, 2023 at 9:12 PM Rafael Blasco <notifications@odoo-community.org> wrote:
Dear Contributors,
I have been looking for a module which help to clear customer invoices with vendor bill from the invoices in the 2 directions.
I look for it in
- https://odoo-community.org/shop?&search=clearing
- https://github.com/OCA/account-invoicing
- https://github.com/OCA/account-financial-tools
We will develop a module account_invoice_clearing
From customer invoice o vendor bill you can bottom clear and a wizard will help you to clear with bill or viceversa
From list same with an action
Actually, this can be done by accountants really easy from account.move.lines but the module wants to provide this tool for invoicing department.
If any feedback, thank you!
Regards,
Rafael
MT-2035
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Thorsten Vocks - 07:11 - 25 May 2023
