Archives
Contributors
-
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-
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 :
+1I added you on the group. You should receive the notification soonFrom: "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
+1On 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.
_______________________________________________
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
+1I added you on the group. You should receive the notification soonFrom: "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
+1On 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
+1On 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-
RE: Documentation on Management System module and its related sub-modules
Thanks Daniel
I tried reaching on your business email dreis@OpenSourceIntegrators.com and seems it may have missed your inbox.
I have resent it just now and please make sure to also check your Junk / Spam folder.
Thanks >> Ketan
From: Daniel Reis <notifications@odoo-community.org>
Sent: Friday, 16 June 2023 9:17 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: Documentation on Management System module and its related sub-modulesHello Ketan.
You should find a few links in the repository README.
And I also did a presentation on it in last year's OCA Days:
https://www.youtube.com/watch?v=w2nf_O9TajM
Thanks
Daniel--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Ketan Chandaria - 01:01 - 21 Jun 2023 -
Re: Documentation on Management System module and its related sub-modules
Hello Ketan.
You should find a few links in the repository README.
And I also did a presentation on it in last year's OCA Days:
https://www.youtube.com/watch?v=w2nf_O9TajM
Thanks
Daniel
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 01:17 - 16 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: 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 itEl mar, 13 jun 2023 a la(s) 03:52, Nhomar Hernández (notifications@odoo-community.org) escribió:Hello @Juan José ScarafíaCan 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_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!_______________________________________________
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: @nhomarMéxico · Venezuela · Costa Rica · Perú
_______________________________________________
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 -
Re: tax_base_amount going to be deprecated. Anyone else using it?
Hello @Juan José ScarafíaCan 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_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!_______________________________________________
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: @nhomarMéxico · Venezuela · Costa Rica · Perú
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_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!_______________________________________________
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!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
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
_______________________________________________
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
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
-
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 -
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-
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 OdooCyril,
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
Check final comment from rafael https://github.com/OCA/social/pull/855#issuecomment-1102348461
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.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 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'.
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-55
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.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 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.
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rafael Blasco (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 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
-
-
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: Google Analytics Universal to GA4 for versions < 15.0
For the record, for v14 Studio73 developed this compatibility module that replaces the tracking code: https://github.com/OCA/website/tree/14.0/website_google_analytics_4 (we just migrated it to v13 for our not yet migrated modules: https://github.com/OCA/website/pull/987).El vie, 26 may 2023 a las 18:37, Francesco Foresti (<notifications@odoo-community.org>) escribió:Hi,has anyone worked on a module to implement the change described here:Odoo 15.0 is already adapted and ready for Analytics 4. After July 2023, if you want to use Google Analytics tracking in versions before 15.0, you will need to insert the GA tracker code manually, instead of entering your GA key in the Odoo settings.
Which according to this post, amounts 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:46 - 29 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 -
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
-
-
Invetory : pallete rate per day + picking rate/coli + pallete IN/OUT rate
Hasllo to everyone,I have several questions. We are implementing Odoo WMS here in Czech republic, and have to fix fololowing inventory rates
- stored pallete rate per day = example 1€/pallete/day
- picking rate/coli = example 0,25€/picked coli
- pallete rate IN/OUT = rate pallete IN 0,35€ (receive) + pallete out (delivery)
Does anyone of you can help with this isuue? Do we have in Odoo some extra applications for inventory rates?
Thanks in advanceS pozdravem / Best regards
MILOŠ MILOJKOVIĆ
Konzultant MRP/Inventory
Mobile: +420 725 426 206
(6) Miloš Milojković | LinkedIn
26HOUSE s.r.o.
Karolinská 2, 186 00 Praha 8
Česká republika
www.26house.com
by Miloš Milojković - 10:01 - 25 May 2023 -
Reserved / priority worker
Hello, I am going to provide some services very similar to what's available as IAP in Odoo so part of it is checking whether customer has got enough "credits". The easiest way would be to create a controller to handle this but I am afraid of situations where the server is occupied with different things like many users, etc. Is there a way to "reserve" a worker for such kind of things? Or maybe somehow to give priority for processing such requests? Any advise is welcome. Thank you Best regards Radovan Skolnik
by Radovan Skolnik - 03:00 - 22 May 2023-
Re: Reserved / priority worker
Erik, thanks a lot. Will check it out. Best regards, Radovan On pondelok 22. mája 2023 23:12:40 CEST Erik Myllymaki wrote: > I was just watching this video the other day that I thought did a good job > of explaining separate odoo instances for erp and cron: > > https://www.youtube.com/watch?v=_q1MhVPKV5g > > > > > On 2023-05-22 14:06, Radovan Skolnik wrote: > > Graeme, > > thanks for the tip. You mean starting another instance over the same > database? I must admit I haven't poked the internals on how concurrent > access like this would work but if it worked, that would be quite easy. > > Best regards, > > Radovan > > On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote: > > Should be easy enough, just start another odoo instance listening on a > > > > different port or container. Configure reverse proxy to send those > > requests > > > > to that instance. Its a fairly common setup already to have a seperate > > > > instance for running crons, particular routes that need extra memory etc. > > > > > > > > > > > > On Tue, 23 May 2023, 1:02 am Radovan Skolnik, > > > > <notifications@odoo-community.org> wrote: > > > > > > > > Hello, > > > > > > > > I am going to provide some services very similar to what's available as > > IAP > > > > in Odoo so part of it is checking whether customer has got enough > > > > "credits". The easiest way would be to create a controller to handle this > > > > but I am afraid of situations where the server is occupied with different > > > > things like many users, etc. > > > > > > > > Is there a way to "reserve" a worker for such kind of things? Or maybe > > > > somehow to give priority for processing such requests? > > > > > > > > Any advise is welcome. Thank you > > > > > > > > Best regards > > > > Radovan Skolnik > > > > _______________________________________________ > > > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > > > Post to: mailto:contributors@odoo-community.org > > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > > > > > > > > > _______________________________________________ > > > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > > > Post to: mailto:contributors@odoo-community.org > > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 11:16 - 22 May 2023 -
Re: Reserved / priority worker
Graeme, thanks for the tip. You mean starting another instance over the same database? I must admit I haven't poked the internals on how concurrent access like this would work but if it worked, that would be quite easy. Best regards, Radovan On pondelok 22. mája 2023 21:41:46 CEST Graeme Gellatly wrote: > Should be easy enough, just start another odoo instance listening on a > different port or container. Configure reverse proxy to send those requests > to that instance. Its a fairly common setup already to have a seperate > instance for running crons, particular routes that need extra memory etc. > > > On Tue, 23 May 2023, 1:02 am Radovan Skolnik, > <notifications@odoo-community.org> wrote: > > Hello, > > I am going to provide some services very similar to what's available as IAP > in Odoo so part of it is checking whether customer has got enough > "credits". The easiest way would be to create a controller to handle this > but I am afraid of situations where the server is occupied with different > things like many users, etc. > > Is there a way to "reserve" a worker for such kind of things? Or maybe > somehow to give priority for processing such requests? > > Any advise is welcome. Thank you > > Best regards > > Radovan Skolnik > > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 11:05 - 22 May 2023
-
Multi Tenant Self Hosted Enviroments
Greetings, I have been struggling to set up a multi-tenant, self hosted Odoo environment. The purpose of multi-tenant in my deployment, I am referring to having multiple clients, who will each want to "own" and manage their instance / database of Odoo. That is, being able to set up multiple websites, shops, with consolidated invoicing and services already provided by Odoo. I understand that I can set up separate VMs which would each point to a specific database. But it would require additional resources to deploy each VM to maintain the OS instances required. As a result, I am looking to consolidate the deployments as much as possible. This way I can configure clients and then break them out if/when it's needed. I am running Odoo 16, self hosted. I started to go down the path to try and force clients to use their specific domain name, but that became an issue because dbfilter can associate between a fully qualified hostname, or just the hostname itself. It wasn't built to go the other direction. Then I ran into the problem of a client needing to use multiple domains and how to associate them to their respective databases. I tried to do much of this logic within nginx, but even then I ran into problems with modifying HTTP headers and then losing the desired outcome. Does anybody know if I'm missing something, or would I really have to kickoff an Odoo instance for each client with their own distributed TLS/SSL cert, DB and front-end server ? I would really like to find a solution that would scale and I know a lot of people have made it scale. I'm just missing some pieces to do the same. Thank you, Charles
by cgucker - 07:46 - 20 May 2023-
Re: Multi Tenant Self Hosted Enviroments
I am all in on Terraform/AWS and I never surface the control plane at all. An isolated container pipeline creates a new database, then an internet-accessible ECS cluster provides access to it (with the control plane disabled).On Mon, May 22, 2023 at 5:52 AM Xavier Brochard <notifications@odoo-community.org> wrote:
Le 21.05.2023 23:32, Charles Gucker a écrit : > On Sun, May 21, 2023 at 12:22 PM Xavier Brochard >> In case Cloudpepper is not what you want, Ivan Yelizariev has made a >> package to help multi tenant Odoo hosting (see its modules on >> apps.odoo.com). There is also some bash scripts from the french >> provider >> Sisalp that you can download from http://download.sisalp.net/scripts/. >> You might also use the Yunohost solution, there is a good Odoo package >> (any version). > Thank you, I'm going to dig into the scripts. I also took a look at > Yunohost and it seems a little basic based on my background and > experiences. Yunohost is not so basic : while its purpose is to help beginners to self-host, it is also good if you want to not forget something, start with all annoying tasks done automaticaly and save time, as it is complete and well configured. **And you can allways do what you want with it.** It is also good if you need to try Odoo with Etherpad, NextCloud, LibreOffice, etc. > I'm > trying to understand how Odoo got to the point of multi-domain (being > able to add multiple websites) in the data plane, but not breaking > away the control plane (configuration functions) from the remaining > data plane functions. That is, dbfilter is intended to assign a > specific host or FQDN to facilitate the control plane functions, but > there isn't a function to administrate the relationships with the data > plane. In other words, within Odoo, there is no way to dynamically > maintain a list of vhost domains and associate them with their > respective databases and actually see the state of each vhost as they > relate to their database and mark them as active or inactive, which > would allow for the duplications or migrations from one database to > another without collisions. Don't forget to have a look on Yelizariev solution. You can ask him if you don't find his modules. There was also some useful OCA modules in the past. > I too ran a service provider in the early 90s Sometimes I miss this pleasant time, when there was a lot of new things to invent ! Best Xavier
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Adam Heinz - 05:00 - 22 May 2023
-
-
Hr Employee Shift planning
Dear allDo you have any experience in Shift planning for employees in Odoo ?I did not find any OCA module for it.I appreciate your inputsThanks in advanceBest regards
by Cyril VINH-TUNG - 03:30 - 17 May 2023-
Re: Hr Employee Shift planning
Hi Cyril,
A bit late on the ball ; at Coop IT Easy, we developed a suite of modules to organise the work of volunteers in cooperative supermarkets. Here they are :- shift
- shift_attendance
- beesdoo_website_shift
- + other modules in the same repository
Last year, we spent some time renaming the modules to push them on the OCA on empty repo shift-planning but we’re running late on schedule. We hope to simplify the counter system this year and port the code to v16 mid-2024.
All the best,
Robin KeunenCoop IT Easyrobin@coopiteasy.be+32 488 86 57 40On 17 May 2023, 04:32 +0200, wrote:
Dear all
Do you have any experience in Shift planning for employees in Odoo ?
I did not find any OCA module for it.
I appreciate your inputs
Thanks in advance
Best regards
_______________________________________________
Mailing-List: odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: odoo-community.org/groups?unsubscribe
by Robin Keunen - 11:11 - 22 May 2023 -
Re: Hr Employee Shift planning
I don't really have the time for that so it has a very low priority for me.
Regards,
Mike.
On 17/05/2023 20:57, Cyril VINH-TUNG wrote:
Thanks Michael
Do you plan to push this module to OCA ?
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 mar. 16 mai 2023, 19:27, Michael Telahun <notifications@odoo-community.org> a écrit :
https://github.com/trevi-software/trevi-hr/tree/14.0/resource_schedule Currently only for v14. I'm not sure when I'll have time to port it to v16. Please let me know if it's missing any features you need. Regards, Mike. On 17/05/2023 04:32, Cyril VINH-TUNG wrote: > Dear all > Do you have any experience in Shift planning for employees in Odoo ? > I did not find any OCA module for it. > I appreciate your inputs > Thanks in advance > Best regards > > _______________________________________________ > 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 Raphael Makonnen - 11:30 - 17 May 2023 -
Re: Hr Employee Shift planning
Thanks MichaelDo you plan to push this module to OCA ?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 mar. 16 mai 2023, 19:27, Michael Telahun <notifications@odoo-community.org> a écrit :https://github.com/trevi-software/trevi-hr/tree/14.0/resource_schedule Currently only for v14. I'm not sure when I'll have time to port it to v16. Please let me know if it's missing any features you need. Regards, Mike. On 17/05/2023 04:32, Cyril VINH-TUNG wrote: > Dear all > Do you have any experience in Shift planning for employees in Odoo ? > I did not find any OCA module for it. > I appreciate your inputs > Thanks in advance > Best regards > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Cyril VINH-TUNG - 07:55 - 17 May 2023 -
Re: Hr Employee Shift planning
https://github.com/trevi-software/trevi-hr/tree/14.0/resource_schedule Currently only for v14. I'm not sure when I'll have time to port it to v16. Please let me know if it's missing any features you need. Regards, Mike. On 17/05/2023 04:32, Cyril VINH-TUNG wrote: > Dear all > Do you have any experience in Shift planning for employees in Odoo ? > I did not find any OCA module for it. > I appreciate your inputs > Thanks in advance > Best regards > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe >
by Raphael Makonnen - 07:26 - 17 May 2023
-
-
Print the quotation preview to pdf
Hi! I need to be able to print the "customer preview" of the quotations to pdf. The option given to print in that view prints a different report (the same one that can be printed from the backend) to what it shows. I'm on Odoo v15 EE. Does anyone have a solution for this need?
by Juan Pablo Garza - 10:00 - 16 May 2023-
Re: Print the quotation preview to pdf
HelloYou might right-clic on the web page and choose 'Print'... then choose a pdf printer.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 mar. 16 mai 2023, 10:02, Sumitec <notifications@odoo-community.org> a écrit :Hi! I need to be able to print the "customer preview" of the quotations to pdf. The option given to print in that view prints a different report (the same one that can be printed from the backend) to what it shows. I'm on Odoo v15 EE. Does anyone have a solution for this need?
_______________________________________________
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 - 05:51 - 18 May 2023
-
-
Bug on l10n_fr_pos_cert | 14.0
Dear contributors of OCA,We encounter a bug on the version 14.0 CE and EE when using the module l10n_fr_pos_cert. It was tested on runbot, locally.We have the following error when clicking on "POS Inalterability Check" submenu of POS > Reporting, and clicking on "Save" button :The full error when copying it :Error:
Odoo Server Error
Traceback (most recent call last):
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/web/controllers/main.py", line 2109, in report_download
response = self.report_routes(reportname, docids=docids, converter=converter, context=context)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/http.py", line 533, in response_wrap
response = f(*args, **kw)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/web/controllers/main.py", line 2040, in report_routes
pdf = report.with_context(context)._render_qweb_pdf(docids, data=data)[0]
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/account/models/ir_actions_report.py", line 50, in _render_qweb_pdf
return super()._render_qweb_pdf(res_ids=res_ids, data=data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 889, in _render_qweb_pdf
html = self_sudo.with_context(context)._render_qweb_html(res_ids, data=data)[0]
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 929, in _render_qweb_html
data = self._get_rendering_context(docids, data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/account/models/ir_actions_report.py", line 55, in _get_rendering_context
return super()._get_rendering_context(docids=docids, data=data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 946, in _get_rendering_context
data.update(report_model._get_report_values(docids, data=data))
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/l10n_fr_pos_cert/report/pos_hash_integrity.py", line 14, in _get_report_values
data.update(self.env.company._check_pos_hash_integrity())
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/l10n_fr_pos_cert/models/res_company.py", line 77, in _check_pos_hash_integrity
start_order_info = build_order_info(orders_sorted_date[0])
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/models.py", line 5707, in __getitem__
return self.browse((self._ids[key],))
IndexError: tuple index out of rangeWhen this error is displayed for the first time, we can not access to the wizard of the menu "POS Inalterability Check" anymore. The traceback :Error:
Odoo Server Error
Traceback (most recent call last):
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/web/controllers/main.py", line 2109, in report_download
response = self.report_routes(reportname, docids=docids, converter=converter, context=context)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/http.py", line 533, in response_wrap
response = f(*args, **kw)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/web/controllers/main.py", line 2040, in report_routes
pdf = report.with_context(context)._render_qweb_pdf(docids, data=data)[0]
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/account/models/ir_actions_report.py", line 50, in _render_qweb_pdf
return super()._render_qweb_pdf(res_ids=res_ids, data=data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 889, in _render_qweb_pdf
html = self_sudo.with_context(context)._render_qweb_html(res_ids, data=data)[0]
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 929, in _render_qweb_html
data = self._get_rendering_context(docids, data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/account/models/ir_actions_report.py", line 55, in _get_rendering_context
return super()._get_rendering_context(docids=docids, data=data)
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/addons/base/models/ir_actions_report.py", line 946, in _get_rendering_context
data.update(report_model._get_report_values(docids, data=data))
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/l10n_fr_pos_cert/report/pos_hash_integrity.py", line 14, in _get_report_values
data.update(self.env.company._check_pos_hash_integrity())
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/addons/l10n_fr_pos_cert/models/res_company.py", line 77, in _check_pos_hash_integrity
start_order_info = build_order_info(orders_sorted_date[0])
File "/home/lanto/Documents/OCA Repos & Sources/Odoo Community Source/odoo_14c/odoo/models.py", line 5707, in __getitem__
return self.browse((self._ids[key],))
IndexError: tuple index out of rangeHave you an idea why this occurred ?Hope there is a solution for this bug.I am still available if you need further information.(sorry if there are mistakes with my English)Thank you !--Bonne journée 
Lanto RazafindrabeConsultant technico-fonctionnel+1 514-317-7944
Billet 5 ANS des Numigiens 🎂🎂🎂🎂🎂 Voir >>
by "Lanto Razafindrabe" <lanto.razafindrabe@numigi.com> - 06:56 - 16 May 2023 -
Someone using Property Management System (PMS) module?
Hello,I'd like to know more about the pms suites of modules here:from a functional perspective.The link to the doc is broken:I just opened an issue about that, we never know:If anyone in OCA community uses this modules and is happy to share his knowledge (by sending a manual with screenshots, or by visio), I'd be very grateful.Thanks a lot,--
Virginie0477/64.17.20
by Virginie Dewulf. - 05:31 - 15 May 2023-
Re: Someone using Property Management System (PMS) module?
Hi,about https://github.com/OCA/vertical-hotel : Its a typical hotel and restaurant solution for booking, reservation, folio, housekeeping.Thanks,On Tue, May 16, 2023 at 12:17 PM Virginie Dewulf <notifications@odoo-community.org> wrote:Hello Dario,My name is not Francesco, but I'm still happy to get your fast responseAre you behind the https://www.roomdoo.com/#producto solution?Could we have a little chat one to one?Here is my email adress to exchange without annoying all the contributors: virginie@coopiteasy.beThanks a lot!
--
Virginie0477/64.17.20-----Original Message-----From: Darío <notifications@odoo-community.org>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Re: Someone using Property Management System (PMS) module?Date: Mon, 15 May 2023 16:26:59 -0000Hi Francesco,We use the pms in production, but it is in alpha version so we are still consolidating all the flows and with constant changes in the module. We'll probably start working on stabilizing it after the summer in a v16.El lun, 15 may 2023 a las 17:32, Virginie Dewulf (<notifications@odoo-community.org>) escribió:Hello,I'd like to know more about the pms suites of modules here:from a functional perspective.The link to the doc is broken:I just opened an issue about that, we never know:If anyone in OCA community uses this modules and is happy to share his knowledge (by sending a manual with screenshots, or by visio), I'd be very grateful.Thanks a lot,--
Virginie0477/64.17.20_______________________________________________
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
--Technology Services @ www.serpentcs.comBusiness Solutions @ www.serpentcs.inEnterprise Mobile Apps @ www.odooonline.comQuality Assurance @ www.odooqa.comSAP Hana @ www.prozone-tech.comPortal & DMS @ www.alfray.inRegards,----------------------------------------------------------------------------------------------------------------------------Jay Vora Managing Director 
Direct: +91-9879354457 Office: +91-9033472982 Skype: jaynvora Twitter : jaynvora -------------------------------------------------------------------------------------------------
Visit our website : http://www.serpentcs.com
by Jay Vora - 08:51 - 16 May 2023 -
Re: Someone using Property Management System (PMS) module?
Hello Dario,My name is not Francesco, but I'm still happy to get your fast responseAre you behind the https://www.roomdoo.com/#producto solution?Could we have a little chat one to one?Here is my email adress to exchange without annoying all the contributors: virginie@coopiteasy.beThanks a lot!--
Virginie0477/64.17.20-----Original Message-----From: Darío <notifications@odoo-community.org>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Re: Someone using Property Management System (PMS) module?Date: Mon, 15 May 2023 16:26:59 -0000Hi Francesco,We use the pms in production, but it is in alpha version so we are still consolidating all the flows and with constant changes in the module. We'll probably start working on stabilizing it after the summer in a v16.El lun, 15 may 2023 a las 17:32, Virginie Dewulf (<notifications@odoo-community.org>) escribió:Hello,I'd like to know more about the pms suites of modules here:from a functional perspective.The link to the doc is broken:I just opened an issue about that, we never know:If anyone in OCA community uses this modules and is happy to share his knowledge (by sending a manual with screenshots, or by visio), I'd be very grateful.Thanks a lot,--
Virginie0477/64.17.20_______________________________________________
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 Virginie Dewulf. - 08:45 - 16 May 2023 -
Re: Someone using Property Management System (PMS) module?
HelloHow about https://github.com/OCA/vertical-hotel ?Could anyone point what are the pro/cons ?@Virginie here is the broken link https://www.roomdoo.com/Best regardsLe lun. 15 mai 2023, 05:32, Virginie Dewulf <notifications@odoo-community.org> a écrit :Hello,I'd like to know more about the pms suites of modules here:from a functional perspective.The link to the doc is broken:I just opened an issue about that, we never know:If anyone in OCA community uses this modules and is happy to share his knowledge (by sending a manual with screenshots, or by visio), I'd be very grateful.Thanks a lot,
--
Virginie0477/64.17.20_______________________________________________
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 - 07:36 - 15 May 2023
-
eCommerce checkout runs out of workers and Odoo dies
Hello,
We stumbled into an Odoo problem, when trying to complete several eCommerce checkouts at the same time, with a low number of workers available. For example: you have two workers, and you have two or more shoppers completing their payment at the exact same time.
We traced this to the report generation happening when closing a Sales Order, and found this relevant Issue:
https://github.com/odoo/odoo/issues/79522
Long story short -
running the reports triggers Odoo requests to get the HTML assets needed,
these triggers the need for more workers to serve the assets,
but no more workers are available and the Odoo server dies (with an "existing gracefully" message and no further explanation!).
The recommended solution from Odoo is to have the assets cached at the Nginx level, both for static files and for the asset bundles.
In this case this is a K8's deployment and we're using Ingress instead of Nginx, and are working through the particular configuration needed to achieve this effect.
I found it could be interesting to share this, and maybe get other points of view or reports from other people having faced the same problem.
Thank you
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais
by Daniel Reis - 07:40 - 9 May 2023-
Re: eCommerce checkout runs out of workers and Odoo dies
Hi Daniel
I don't know if it helps in your case, but we had a similar problem where the root cause was the invoice sequence number being set to "nogap" (as it should, in fact). This makes e-commerce clients have to wait on each other if both confirm at the same time. While waiting, both of them occupy workers, of course, so if you have only 2 workers and the third client comes to browse the shop he will not even get any response because he will have to wait for a free worker. Since ours was a very heavy-traffic e-commerce, this happened often even with many workers enabled, and we ended up refactoring the process so that the order is marked for confirmation in real-time (quick), but the actual invoice generation and sending by email (slow and prone to DB conflict) is delegated to a queue job and done sequentially.
-Tom
On 5/9/23 19:41, Daniel Reis wrote:
Hello,
We stumbled into an Odoo problem, when trying to complete several eCommerce checkouts at the same time, with a low number of workers available. For example: you have two workers, and you have two or more shoppers completing their payment at the exact same time.
We traced this to the report generation happening when closing a Sales Order, and found this relevant Issue:
https://github.com/odoo/odoo/issues/79522
Long story short -
running the reports triggers Odoo requests to get the HTML assets needed,
these triggers the need for more workers to serve the assets,
but no more workers are available and the Odoo server dies (with an "existing gracefully" message and no further explanation!).
The recommended solution from Odoo is to have the assets cached at the Nginx level, both for static files and for the asset bundles.
In this case this is a K8's deployment and we're using Ingress instead of Nginx, and are working through the particular configuration needed to achieve this effect.
I found it could be interesting to share this, and maybe get other points of view or reports from other people having faced the same problem.
Thank you
--
DANIEL REIS
MANAGING PARTNERM: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 12:05 - 10 May 2023
-
-
Odoo barcode range scanning functionality
Good day
My name is Sam, I'm a Tech Lead at Open Source Integrators. We have a client that's using Odoo Enterprise Edition v15 and needs the functionality to be able to enter a range of serial numbers by scanning the first and the last barcodes in a range when doing inventory adjustments. Do you know of any solution that could help us with this?
We appreciate your help,Samuel MaciasOpen Source Integrators
by Samuel Macias Oropeza - 10:00 - 8 May 2023-
Re: Odoo barcode range scanning functionality
Hi samuel,
This is Jorge, from Binhex.
We have developed for v14 community edition a solution that it's able to parse GS1-128 barcodes with identifiers, it works similar to Enterprise Barcode app.
Anyway, my team has experience also with enterprise barcode app, so i think we have experience to maybe help you find a solution.
Please let me know if you whant to have a chat with us and talk about the specific need.
Regards,
El 08/05/2023 21:02 Samuel Macias Oropeza <notifications@odoo-community.org> escribió:
Good day
My name is Sam, I'm a Tech Lead at Open Source Integrators. We have a client that's using Odoo Enterprise Edition v15 and needs the functionality to be able to enter a range of serial numbers by scanning the first and the last barcodes in a range when doing inventory adjustments. Do you know of any solution that could help us with this?
We appreciate your help,Samuel MaciasOpen Source Integrators_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Jorge Elena Poblet
Experto en Transformación Digital
CEO| Binhex Systems Solutions S.L.
+34 822 179 267 | +34 622 40 08 08 
j.elena@binhex.es 
https://binhex.es 
Calle Subida al Mayorazgo, 13, Oficina 15-2, Santa Cruz de Tenerife, Islas Canarias, España 
Aviso legal:
Protección de datos. - Binhex Systems Solutions, S.L. le informa que su dirección de correo electrónico, así como el resto de sus datos personales serán usados para nuestra relación y poder prestarle nuestros servicios. Dichos datos son necesarios para poder relacionarnos con usted, lo que nos permite el uso de su información dentro de la legalidad. Asimismo, podrán tener conocimiento de su información aquellas entidades que necesiten tener acceso a la misma para que podamos prestarle nuestros servicios. Conservaremos sus datos durante nuestra relación y mientras nos obliguen las leyes aplicables. En cualquier momento puede dirigirse a nosotros para saber qué información tenemos sobre usted, rectificarla si fuese incorrecta y eliminarla una vez finalizada nuestra relación. También tiene derecho a solicitar el traspaso de su información a otra entidad (portabilidad). Para solicitar alguno de estos derechos, deberá realizar una solicitud escrita a nuestra dirección, junto con una fotocopia de su DNI:
Binhex Systems Solutions, S.L., con dirección en Calle Lepanto 3, 2A, CP 38005, Santa Cruz de Tenerife (Santa Cruz de Tenerife). En caso de que entienda que sus derechos han sido desatendidos, puede formular una reclamación en la Agencia Española de Protección de Datos (www.agpd.es).
Confidencialidad. - El contenido de esta comunicación, así como el de toda la documentación anexa, es confidencial y va dirigida al destinatario del mismo. En el supuesto de que usted no fuera el destinatario, le solicitamos que nos lo indique y no comunique su contenido a terceros, procediendo a su destrucción.
Exención de responsabilidad. - El envío de la presente comunicación no implica la obligación por parte del remitente de controlar la ausencia de virus, gusanos, troyanos y/o cualquier otro programa informático dañino, correspondiendo al destinatario disponer de las herramientas de hardware y software necesarias para garantizar tanto la seguridad de su sistema de información como la detección y eliminación de programas informáticos dañinos. Binhex Systems Solutions, S.L. no se responsabiliza de los daños y perjuicios que tales programas informáticos puedan causar al destinatario.
by Jorge Elena Poblet - 11:26 - 8 May 2023
-
-
Datev data
Dear OCA,
i got an issue from a customer, that uses a very specific accounting chart in germany.
As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.
In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.
- The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.
- Exported CSV-files needs to be encoded in Windows ANSI
- Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters
- EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header
The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“
The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.
Is anbody aware of a solution, that already provides this kind of modification?
Would be very thankful for some hints concering that topic.
All the best
Nils
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)
Ust.-Idnr. (VAT-ID): DE341437044
by Nils Coenen - 12:26 - 3 May 2023-
Re: Datev data
Many thanks Holger Brunn for linking the appropriate PR´s. I´ll have a closer look.
@Thomas Pot: i would appreciate sharing your experience. Even if i am not involved in the dev of the mentioned modules yet…
I think we can only benefit from it.
BTW: I am facing this issue now on v16.
I´ll give it a try modifying the odoo functions manually and see, what kind of problems will occur.
It sounds like, that a corresponding module would be of interest to many users?!
All the best
Nils
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)
Ust.-Idnr. (VAT-ID): DE341437044Von: Thomas Pot <notifications@odoo-community.org>
Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
Datum: Mittwoch, 3. Mai 2023 um 14:41
An: Contributors <contributors@odoo-community.org>
Betreff: Re: Datev dataHello All,
We encountered also several issue's in the DATEV export function in Odoo EE. because of the urgent matters at that point we decided to override the default functions in Odoo.
We reported our issue's to Odoo but as far as I know, there are no actions taken for some.
It also depends on the used version; v15 is different from V13. (and already better)
But we would be happy to share our experience with the community?
Met vriendelijke groet - Kind Regards - Mit freundlichen Grüßen,
Thomas Pot
Open2Bizz - dé Odoo specialist
Mauritslaan 56 | 6161 HW | Geleen
Maak meteen een afspraak voor een online demo van Odoo / Open2Ortho:
Klik hier
Van: "Holger Brunn" <notifications@odoo-community.org>
Aan: "Contributors" <contributors@odoo-community.org>
Onderwerp: Re: Datev data_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Nils Coenen - 03:00 - 3 May 2023 -
Re: Datev data
> i know that Thorsten Vocks and Holger Brunn, are currently working the old > CSV tooling for Datev Back and Forth (in a specific customer project). The > code is not yet published but if i am not mistaken it will be soon. you can find both on https://github.com/OCA/l10n-germany/pulls in #118 and #121 -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 01:25 - 3 May 2023 -
Re: Datev data
Hi Frederick,
many thanks for your reply.
If there is something in progress for sharing with the OCA… would be great to have a feedback about the status.
I would like to provide input as well on this task. For now, I am not able to say if my dev skills will be sufficient in this case.
Still learning a lot. Especially in terms of using git in collab. Considering to keep it economic, i decided to ask here first.
I think a contribution by the customer can be achieved. Depending an the budget needed of course.
I will have an eye on OCA/l10n-germany and i will talk to the customer.
If Thorsten Vocks and/or Holger Brunn are willing to provide some infos… that would be great.
And many thanks for the offer of calling you on your mobile. I will fall back on it if necessary.
All the best
Nils
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)
Ust.-Idnr. (VAT-ID): DE341437044Von: Frederik Kramer <notifications@odoo-community.org>
Antworten an: "Odoo Community Association (OCA) Contributors" <contributors@odoo-community.org>
Datum: Mittwoch, 3. Mai 2023 um 12:52
An: Contributors <contributors@odoo-community.org>
Betreff: Re: Datev dataHi Nils,
i know that Thorsten Vocks and Holger Brunn, are currently working the old CSV tooling for Datev Back and Forth (in a specific customer project). The code is not yet published but if i am not mistaken it will be soon. So maybe either of those two can comment. Definitely most of your feedback (or better the one of your consultant) is somewhat known already within the group of OCA contributors working on the OCA Datev modul set. If you don't have own development skill but your customer is willing to contribute financially to develop an Open Source solution thats is typically the easiest and fastest way to get contributors attention. If you have further questions or suggestions to make you can always give me a call on my mobile
Best Frederik
Am 03.05.23 um 12:27 schrieb Nils Coenen:
Dear OCA,
i got an issue from a customer, that uses a very specific accounting chart in germany.
As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.
In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.
- The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.
- Exported CSV-files needs to be encoded in Windows ANSI
- Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters
- EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header
The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“
The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.
Is anbody aware of a solution, that already provides this kind of modification?
Would be very thankful for some hints concering that topic.
All the best
Nils
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)
Ust.-Idnr. (VAT-ID): DE341437044_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe--
Dr.-Ing. Frederik Kramer
Geschäftsführer
initOS GmbH
Innungsstraße 7
21244 Buchholz i.d.N.
Phone: +49 4181 13503-12
Fax: +49 4181 13503-10
Mobil: +49 179 3901819
Email: frederik.kramer@initos.com
Web: www.initos.com
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke
Sitz der Gesellschaft: Buchholz i.d.N.
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
_______________________________________________
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 - 01:21 - 3 May 2023 -
Re: Datev data
Hi Nils,
i know that Thorsten Vocks and Holger Brunn, are currently working the old CSV tooling for Datev Back and Forth (in a specific customer project). The code is not yet published but if i am not mistaken it will be soon. So maybe either of those two can comment. Definitely most of your feedback (or better the one of your consultant) is somewhat known already within the group of OCA contributors working on the OCA Datev modul set. If you don't have own development skill but your customer is willing to contribute financially to develop an Open Source solution thats is typically the easiest and fastest way to get contributors attention. If you have further questions or suggestions to make you can always give me a call on my mobile
Best Frederik
Am 03.05.23 um 12:27 schrieb Nils Coenen:
Dear OCA,
i got an issue from a customer, that uses a very specific accounting chart in germany.
As they want to perform the accounting on their own before sending it to the acc. Consultant, some adaption seem to be mandatory.
In order to create smooth convertability between the datev-export provided by odoo and the import in the system of t he accounting consultant, the data needs to be modified. So this is the feedback i got from the consultant about the export data.
- The code number for the account number extension (KNE) needs to start with digit number 4 instead of a 8 digit number. This is not a problem and provided by the Odoo enterprise core export tool.
- Exported CSV-files needs to be encoded in Windows ANSI
- Debit/credit indicators are only allowed in capital letters "S" or "H". The standard Odoo export provides small letters
- EXTF Version 700 instead of 510 is important when recording with empty and modified headings in the header
The export is provided by the modules „l10n_de_datev_reports“ & „l10n_de_reports“
The encoding can be changed after exporting, same for the capital letters. But to keep it as simple as possible for the customer, it would be great to have this included in the export function. Covering the other way as well would be awesome.
Is anbody aware of a solution, that already provides this kind of modification?
Would be very thankful for some hints concering that topic.
All the best
Nils
--
NICO SOLUTIONS - ENGINEERING & IT
Inhaber (Owner): Nils Coenen
Dr.-Ruckert-Str. 1G
28865 Lilienthal
Deutschland (Germany)
Ust.-Idnr. (VAT-ID): DE341437044
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
-- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH Innungsstraße 7 21244 Buchholz i.d.N. Phone: +49 4181 13503-12 Fax: +49 4181 13503-10 Mobil: +49 179 3901819 Email: frederik.kramer@initos.com Web: www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Buchholz i.d.N. Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 12:51 - 3 May 2023
-
OCA/bank_statement_import - Odoo 16, Switzerland
Hi there,We are currently upgrading a Swiss customer from Odoo V13 to V16.In V13 the customer uses the following modules from the OCA/bank_statement_import Project:- account_bank_statement_import_camt_oca- acclount_bank_statement_import_oca_camt54As far as I checked, based on modules available for V15, we would need:1. account_statement_import_camt2. account_statement_import_camt54and the base modules:3. account_stamement_import(_file)4. account_statement_import_base3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?Thanks in advance.Kind RegardsElmar--Beste Grüße / Kind RegardsElmar HardenackManaging PartnerAphora GmbH i.G.Represented by: Adam Hussein, Elmar HardenackRehringhauser Str. 7a | DE-57462 Olpe (HQ)Rudolfplatz 3 | DE-50674 KölnThis message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.
by Elmar Hardenack - 11:26 - 3 May 2023-
Re: OCA/bank_statement_import - Odoo 16, Switzerland
Hi Alex and Virginie,Thanks for the quick reply and providing the links.Kind regardsElmarAm Mi., 3. Mai 2023 um 11:42 Uhr schrieb Alex Comba <notifications@odoo-community.org>:Hi Elmar,please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.I hope it helps you.Best regardsOn Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:Hi there,We are currently upgrading a Swiss customer from Odoo V13 to V16.In V13 the customer uses the following modules from the OCA/bank_statement_import Project:- account_bank_statement_import_camt_oca- acclount_bank_statement_import_oca_camt54As far as I checked, based on modules available for V15, we would need:1. account_statement_import_camt2. account_statement_import_camt54and the base modules:3. account_stamement_import(_file)4. account_statement_import_base3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?Thanks in advance.Kind RegardsElmar--Beste Grüße / Kind RegardsElmar HardenackManaging PartnerAphora GmbH i.G.Represented by: Adam Hussein, Elmar HardenackRehringhauser Str. 7a | DE-57462 Olpe (HQ)Rudolfplatz 3 | DE-50674 KölnThis message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Beste Grüße / Kind RegardsElmar HardenackManaging PartnerAphora GmbH i.G.Represented by: Adam Hussein, Elmar HardenackRehringhauser Str. 7a | DE-57462 Olpe (HQ)Rudolfplatz 3 | DE-50674 KölnThis message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it.
by Elmar Hardenack - 06:35 - 4 May 2023 -
Re: OCA/bank_statement_import - Odoo 16, Switzerland
Hello Elmar,We also have customers using the Swiss localization and we want to migrate them from v12 to v16 in the following months (or year, depending on the work to be done).Maybe there are other modules that our respective customers use and we could cofinance part of them or split the work in a synchronized way.Don't hesitate to contact me directly (virginie@coopiteasy.be).By the way both modules you're interested in are here:- account_bank_statement_import_camt_ocaaccount_bank_statement_import_oca_camt54Have a nice day,--
Virginie0477/64.17.20-----Original Message-----From: Alex Comba <notifications@odoo-community.org>Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>To: Contributors <contributors@odoo-community.org>Subject: Re: OCA/bank_statement_import - Odoo 16, SwitzerlandDate: Wed, 03 May 2023 09:42:26 -0000Hi Elmar,please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.I hope it helps you.Best regardsOn Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:Hi there,We are currently upgrading a Swiss customer from Odoo V13 to V16.In V13 the customer uses the following modules from the OCA/bank_statement_import Project:- account_bank_statement_import_camt_oca- acclount_bank_statement_import_oca_camt54As far as I checked, based on modules available for V15, we would need:1. account_statement_import_camt2. account_statement_import_camt54and the base modules:3. account_stamement_import(_file)4. account_statement_import_base3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?Thanks in advance.Kind RegardsElmar--Beste Grüße / Kind RegardsElmar HardenackManaging PartnerAphora GmbH i.G.Represented by: Adam Hussein, Elmar HardenackRehringhauser Str. 7a | DE-57462 Olpe (HQ)Rudolfplatz 3 | DE-50674 KölnThis message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Virginie Dewulf. - 05:01 - 3 May 2023 -
Re: OCA/bank_statement_import - Odoo 16, Switzerland
Hi Elmar,please have a look at https://github.com/OCA/bank-statement-import/issues/503 where you can find the links to open PRs not yet migrated.I hope it helps you.Best regardsOn Wed, May 3, 2023 at 11:27 AM Elmar Hardenack <notifications@odoo-community.org> wrote:Hi there,We are currently upgrading a Swiss customer from Odoo V13 to V16.In V13 the customer uses the following modules from the OCA/bank_statement_import Project:- account_bank_statement_import_camt_oca- acclount_bank_statement_import_oca_camt54As far as I checked, based on modules available for V15, we would need:1. account_statement_import_camt2. account_statement_import_camt54and the base modules:3. account_stamement_import(_file)4. account_statement_import_base3. and 4. are available for V16, 1. and 2. are not, yet, as per https://github.com/OCA/bank-statement-import/tree/16.0Is there any plan to upgrade 1. and 2., and if so when? Or would you be willing to upgrade them now? Or did they get replaced with other OCA modules or maybe even Odoo standard features I'm not aware of?Thanks in advance.Kind RegardsElmar--Beste Grüße / Kind RegardsElmar HardenackManaging PartnerAphora GmbH i.G.Represented by: Adam Hussein, Elmar HardenackRehringhauser Str. 7a | DE-57462 Olpe (HQ)Rudolfplatz 3 | DE-50674 KölnThis message is exclusively intended for its addressee and may contain confidential information that is protected by professional privilege. If you are not the intended recipient, you are hereby notified that any copy, disclosure or dissemination of this communication is strictly prohibited by law. If this message has been received by error, please notify us immediately via e-mail and delete it._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Alex Comba
Tel (CH): +41 91 210 23 40
by Alex Comba. - 11:41 - 3 May 2023
-
-
suggestion for monitoring error 500
Hi,We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).Times to times, the end user (e-commerce customer) will receive an error 500.It is a bit of a catchall... Would anybody have any suggestion, to monitor such error, and possibly get an email, or a warning as a system administrator? Is there a way to catch at odoo level, if there is such error and send an email ?Or could we "monitor" the log file ? <-- any suggestion on possible tool ?Thanks,Dominique
by dominique.k - 07:21 - 1 May 2023-
Re: suggestion for monitoring error 500
Hi Dominique
If you have Odoo running behind NGINX, you can parse the access log file to get some statistics about the timestamps around which this occurs, and on which urls. I have a way of doing that with command line tools such as "awk", "sort" and "uniq" (for hourly statistics), but regular "grep" can also yield you the info.
Armed with that knowledge you can then check the Odoo log file around those times, sometimes it will also display "Internal error" or even a useful traceback, and you can then use "grep" again to extract relevant patterns over the course of a day or so.
If not enough information is given, then you could resort to modifying the Odoo source code to add some more exception-catching.
1 mei 2023 06:57:22 Holger Brunn <notifications@odoo-community.org>:
> It is a bit of a catchall... Would anybody have any suggestion, to monitor > such error, and possibly get an email, or a warning as a system > administrator? Is there a way to catch at odoo level, if there is such > error and send an email ? all requests go through https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ir_http.py#L153 so that seems the best place to catch your exception -- Your partner for the hard Odoo problems https://hunki-enterprises.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 05:56 - 1 May 2023 -
RE: suggestion for monitoring error 500
Hi Dominique,
I normally use the try … except like below:
try:except Exception as e:
mail_smtp_server = self.env["ir.mail_server"].sudo().search([], limit=1)
email_vals = {"state": "outgoing" ,
"subject": str(self.env.cr.dbname) + " Error in demo 1 controller " ,
"body_html": """Error in demo 1 controller : """ + str(e.message) + " " + str(e.args) ,
"auto_delete": True,
"email_from": mail_smtp_server.smtp_user ,
"email_to": madeb@regious.co.zw ,
}
self.env["mail.mail"].create(email_vals)
Regards,
Bill Made
+263 733 419 060
From: Dominique k <notifications@odoo-community.org>
Sent: Monday, May 1, 2023 7:29 AM
To: Contributors <contributors@odoo-community.org>
Subject: suggestion for monitoring error 500Hi,
We have a case where odoo is used as an e-commerce + portal system (with quite a lot of customisation).
Times to times, the end user (e-commerce customer) will receive an error 500.
It is a bit of a catchall... Would anybody have any suggestion, to monitor such error, and possibly get an email, or a warning as a system administrator? Is there a way to catch at odoo level, if there is such error and send an email ?
Or could we "monitor" the log file ? <-- any suggestion on possible tool ?
Thanks,
Dominique
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Bill Made - 08:51 - 1 May 2023 -
Re: suggestion for monitoring error 500
> It is a bit of a catchall... Would anybody have any suggestion, to monitor > such error, and possibly get an email, or a warning as a system > administrator? Is there a way to catch at odoo level, if there is such > error and send an email ? all requests go through https://github.com/OCA/OCB/blob/16.0/odoo/addons/base/models/ir_http.py#L153 so that seems the best place to catch your exception -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 07:56 - 1 May 2023
-
