Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
European Union One-Stop-Shop
Hi Community,As you know, a major tax change will be implemented shortly (1st of July) that will affect all EU countries.More info:https://ec.europa.eu/taxation_customs/business/vat/oss_enFor the newest versions, (from V14) Odoo is planning a "kind of solution", but what happens with older versions? Is any European partner working on this?Some of the Spanish partners started this project, and we were wondering if anybody else will do the same. The main idea is to "join our efforts" and offer a global solution according to the ideology proposed by OCA.Regards,--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 12:26 - 10 Jun 2021-
Re: European Union One-Stop-Shop
Hello all,
A quick update on this.
There was a great team effort on this feature, to develop, review and port across multiple Odoo versions.
The l10n_eu_oss module can be found at:
https://github.com/OCA/account-fiscal-rule
In the meanwhile, Odoo released their support for this.
It is an improvement to the l10n_eu_service module, available in Odoo CE.
There were later fixes, but the main implementation is here:
https://github.com/odoo/odoo/commit/d347eae1646639e2b346d404d1eb68ce9eac005c#diff-6299170bf4eb194cb23d4b799e0ce09b17a250b11e6eeb6aa3c58f63cea04c95
So there are two different solutions right now.
I started an Issue to discuss the differences.
Right now contributors feeling is that the OCA version probably does a better job.
You can check the details here:
https://github.com/OCA/account-fiscal-rule/issues/226
Have a nice day
Daniel
Às 11:27 de 10/06/21, Harald Panten Lopez escreveu:
Hi Community,
As you know, a major tax change will be implemented shortly (1st of July) that will affect all EU countries.
More info:https://ec.europa.eu/taxation_customs/business/vat/oss_en
For the newest versions, (from V14) Odoo is planning a "kind of solution", but what happens with older versions? Is any European partner working on this?
Some of the Spanish partners started this project, and we were wondering if anybody else will do the same. The main idea is to "join our efforts" and offer a global solution according to the ideology proposed by OCA.
Regards,--
Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Daniel Reis - 05:51 - 6 Jul 2021 -
Re: [28078] Re: European Union One-Stop-Shop
Hi all,
We didn't do the meeting today because there was lack of attendance,
would you like to do a meeting tomorrow 22.06 at 15:00? or if you like please suggest
other dates.
Kind regards,
UsamaOn 14.06.21 23:42, Frederik Kramer wrote:
Hi all, what you all makes absolute sense. In Germany we have the probably slightly different case that most SME still use Datev for their financial accounting, so looking at that specific thing its desireable to follow Datev' habit on creating accounts for specific accounting practices. Having said this meanwhile i checked the "German" Datev habit with regard to intra-trade and found out, that most probably we accumulate all but the domestic trades on 1! revenue account and 1! tax account. I'll wait final approval by the tax advisors but if that holds true, than yes certainly no reason to rework the design for more flexibility / complexity here. Best Frederik Am Montag, den 14.06.2021, 20:26 +0000 schrieb Valentin Vinagre Urteaga: > Hi Daniel, > As Pedro has commented, we thought about that option but it was much > more complicated, so we opted for an option that is easier to > implement and more versatile. > > El lun, 14 jun 2021 a las 22:18, Valentin Vinagre Urteaga (< > valentin.vinagre@sygel.es>) escribió: > > Hi Frederik, > > At first we also thought about being able to define which account > > to take the new taxes to ... but we thought it was better to take > > it to the same accounts that had the local taxes configured and > > then change it manually if necessary. Later an extension could be > > carried out with this functionality. > > > > El lun, 14 jun 2021 a las 21:57, Pedro M. Baeza (Tecnativa) (< > > pedro.baeza@tecnativa.com>) escribió: > > > The XML-ID thing is something that Valentín, Harald and I > > > discussed in the initial kick-off we did, and the > > > `oss_country_id` field is far more versatile for the needed > > > things than going to the XML-ID schema that will feel weird and > > > restricting. > > > > > > Regards. > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > > Post to: mailto:contributors@odoo-community.org > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > > > -- > > > > Valentín Vinagre Urteaga > > CTO > > Sygel Technology S.L > > > > +34 662 68 78 95 > > > > valentin.vinagre@sygel.es > > > > https://www.sygel.es > > > > C/ Àlaba 61, 5ª planta, 08005, Barcelona > > > > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-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: Rosengarten – Klecken 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
-- Mit freundlichen Grüßen Usama Albgaghdady Softwareentwickler initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-39 Fax: +49 4105 56156-10 Email: usama.albaghdady@initos.com Web: http://www.initos.com Geschäftsführung: Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke Sitz der Gesellschaft: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr: DE815580155
by Usama Albaghdady - 03:36 - 21 Jun 2021 -
Re: [28078] Re: European Union One-Stop-Shop
Hi all, what you all makes absolute sense. In Germany we have the probably slightly different case that most SME still use Datev for their financial accounting, so looking at that specific thing its desireable to follow Datev' habit on creating accounts for specific accounting practices. Having said this meanwhile i checked the "German" Datev habit with regard to intra-trade and found out, that most probably we accumulate all but the domestic trades on 1! revenue account and 1! tax account. I'll wait final approval by the tax advisors but if that holds true, than yes certainly no reason to rework the design for more flexibility / complexity here. Best Frederik Am Montag, den 14.06.2021, 20:26 +0000 schrieb Valentin Vinagre Urteaga: > Hi Daniel, > As Pedro has commented, we thought about that option but it was much > more complicated, so we opted for an option that is easier to > implement and more versatile. > > El lun, 14 jun 2021 a las 22:18, Valentin Vinagre Urteaga (< > valentin.vinagre@sygel.es>) escribió: > > Hi Frederik, > > At first we also thought about being able to define which account > > to take the new taxes to ... but we thought it was better to take > > it to the same accounts that had the local taxes configured and > > then change it manually if necessary. Later an extension could be > > carried out with this functionality. > > > > El lun, 14 jun 2021 a las 21:57, Pedro M. Baeza (Tecnativa) (< > > pedro.baeza@tecnativa.com>) escribió: > > > The XML-ID thing is something that Valentín, Harald and I > > > discussed in the initial kick-off we did, and the > > > `oss_country_id` field is far more versatile for the needed > > > things than going to the XML-ID schema that will feel weird and > > > restricting. > > > > > > Regards. > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 > > > Post to: mailto:contributors@odoo-community.org > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > > > -- > > > > Valentín Vinagre Urteaga > > CTO > > Sygel Technology S.L > > > > +34 662 68 78 95 > > > > valentin.vinagre@sygel.es > > > > https://www.sygel.es > > > > C/ Àlaba 61, 5ª planta, 08005, Barcelona > > > > -- Dr.-Ing. Frederik Kramer Geschäftsführer initOS GmbH An der Eisenbahn 1 21224 Rosengarten Phone: +49 4105 56156-12 Fax: +49 4105 56156-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: Rosengarten – Klecken Amtsgericht Tostedt, HRB 205226 Steuer-Nr: 15/200/53247 USt-IdNr.: DE815580155
by Frederik Kramer - 11:41 - 14 Jun 2021 -
Re: [28078] Re: European Union One-Stop-Shop
Hi Daniel,As Pedro has commented, we thought about that option but it was much more complicated, so we opted for an option that is easier to implement and more versatile.El lun, 14 jun 2021 a las 22:18, Valentin Vinagre Urteaga (<valentin.vinagre@sygel.es>) escribió:Hi Frederik,
At first we also thought about being able to define which account to take the new taxes to ... but we thought it was better to take it to the same accounts that had the local taxes configured and then change it manually if necessary. Later an extension could be carried out with this functionality.El lun, 14 jun 2021 a las 21:57, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:The XML-ID thing is something that Valentín, Harald and I discussed in the initial kick-off we did, and the `oss_country_id` field is far more versatile for the needed things than going to the XML-ID schema that will feel weird and restricting.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Valentín Vinagre Urteaga
CTO
Sygel Technology S.L

+34 662 68 78 95 
valentin.vinagre@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona --Valentín Vinagre Urteaga
CTO
Sygel Technology S.L

+34 662 68 78 95 
valentin.vinagre@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Valentín Vinagre - 10:26 - 14 Jun 2021 -
Re: [28078] Re: European Union One-Stop-Shop
Hi Frederik,
At first we also thought about being able to define which account to take the new taxes to ... but we thought it was better to take it to the same accounts that had the local taxes configured and then change it manually if necessary. Later an extension could be carried out with this functionality.El lun, 14 jun 2021 a las 21:57, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:The XML-ID thing is something that Valentín, Harald and I discussed in the initial kick-off we did, and the `oss_country_id` field is far more versatile for the needed things than going to the XML-ID schema that will feel weird and restricting.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Valentín Vinagre Urteaga
CTO
Sygel Technology S.L

+34 662 68 78 95 
valentin.vinagre@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Valentín Vinagre - 10:20 - 14 Jun 2021
-
-
Transfer/Migrate Product with Variants Keeping External Identifier for product.product
Hello everyone
I need to transfer products with variants from one Odoo database to another and have one requirement:
To keep the exact external identifier for both product.template and product.product records.
I need specially to preserve the external identifier for product.product (Product Variants) because later on I'll have to transfer stock moves and, yes, what is referenced in stock moves, sales, purchases, is product.product (and not product.template).
I've successfully exported products with variants (exported "attribute_line_ids/attribute_id/id" and "attribute_line_ids/value_ids/id") and import them in the destination database and everything is OK, products with variants are replicated but at the end variants (product.product records) have no external identifier, and I need them.
Can someone help, please?
Regards
--
Aires Silvestre
COO | Odoo Consultant
em.aires.silvestre@alien-group.com
tm.+244 913 728 650
Rua Doutor Agostinho Neto, 156, Bairro Azul, Luanda - Angola, Tel: +244 913 728 600 | +244 913 728 650,
Website: www.alien-group.com, Email: geral@alien-group.com
Não
imprima este email caso não seja estritamente
necessário. A Terra agradece-lhe!
by Aires Silvestre - 09:56 - 10 Jun 2021-
Re: Transfer/Migrate Product with Variants Keeping External Identifier for product.product
Hello Aires,
It is not clear, but I feel that you are doing the export based on Product Template + Attributes, that will later trigger the Variant creation.
I suggest you to instead export/import the Product Variants (product.product), along with the related attribute data, and let the implicit Product Template record be automatically created.
For the record I did a quick test (14.0), and:
- if you import a "MYPRODUCT" Product Template, it has a __import__.MYPRODUCT XMLId and creates a related Product Variant with no XMLId.
- if you import a "MYPRODUCT" Product Variant, it has a __import__.MYPRODUCT XMLId and creates a related Product Template with XMLId __import__.MYPRODUCT_product_template.
This is helpful for that cases where you have relations to Product Template records (BoMs for example).
I hope this helps.
Thanks
Daniel
On 10/06/2021 08:57, Aires Silvestre wrote:
Hello everyone
I need to transfer products with variants from one Odoo database to another and have one requirement:
To keep the exact external identifier for both product.template and product.product records.
I need specially to preserve the external identifier for product.product (Product Variants) because later on I'll have to transfer stock moves and, yes, what is referenced in stock moves, sales, purchases, is product.product (and not product.template).
I've successfully exported products with variants (exported "attribute_line_ids/attribute_id/id" and "attribute_line_ids/value_ids/id") and import them in the destination database and everything is OK, products with variants are replicated but at the end variants (product.product records) have no external identifier, and I need them.
Can someone help, please?
Regards
--
Aires Silvestre
COO | Odoo Consultant
em.aires.silvestre@alien-group.com
tm.+244 913 728 650
Rua Doutor Agostinho Neto, 156, Bairro Azul, Luanda - Angola, Tel: +244 913 728 600 | +244 913 728 650,
Website: www.alien-group.com, Email: geral@alien-group.com
Não imprima este email caso
não seja estritamente necessário. A Terra
agradece-lhe! _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal 



by Daniel Reis - 01:00 - 10 Jun 2021 -
Re: Transfer/Migrate Product with Variants Keeping External Identifier for product.product
Hi,
Are you having trouble with generating your own identifiers when you create the products?
Remember, they are just in a table.
If you have data in a module, the external identifiers are fixed by the id in the xml.
When you export anything in Odoo, it will use that identifier, or it will look for what identifier has been used, and if it is not there, will create its own?
So after importing your products in your new database, you could set / override the external identifier to be what it was in your export?
Without knowing what you have done, and what the endgame is exactly, I would have thought it a not too difficult task to replace the identifiers in your new db with what they were in the old db, ensuring that future exports from either source would have the same identifier.
Richard
Richard deMeester
Senior Development Analyst
WilldooIT Pty Ltd
E: richard.demeester@willdooit.com
M: +61 403 76 76 76
P: +61 3 9135 1900
A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
Making growth through technology easy
DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
From: Aires Silvestre <aires.silvestre@alien-group.com>
Sent: Thursday, 10 June 2021 5:57 PM
To: Contributors <contributors@odoo-community.org>
Subject: Transfer/Migrate Product with Variants Keeping External Identifier for product.productHello everyone
I need to transfer products with variants from one Odoo database to another and have one requirement:
To keep the exact external identifier for both product.template and product.product records.
I need specially to preserve the external identifier for product.product (Product Variants) because later on I'll have to transfer stock moves and, yes, what is referenced in stock moves, sales, purchases, is product.product (and not product.template).
I've successfully exported products with variants (exported "attribute_line_ids/attribute_id/id" and "attribute_line_ids/value_ids/id") and import them in the destination database and everything is OK, products with variants are replicated but at the end variants (product.product records) have no external identifier, and I need them.
Can someone help, please?
Regards
--
Aires Silvestre
COO | Odoo Consultant
em.aires.silvestre@alien-group.com
tm.+244 913 728 650
Rua Doutor Agostinho Neto, 156, Bairro Azul, Luanda - Angola, Tel: +244 913 728 600 | +244 913 728 650,
Website: www.alien-group.com, Email: geral@alien-group.com
Não imprima este email caso não seja estritamente necessário. A Terra agradece-lhe!
_______________________________________________
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> - 10:41 - 10 Jun 2021
-
-
Proposing myself as PSC for Document
Hello, I'm recently quite active on the dms repo, and I see it could use an extra maintainer. I propose myself.https://github.com/Yajo <-- meThanks everyone!
by Jairo Llopis - 08:31 - 10 Jun 2021-
Re: Proposing myself as PSC for Document
El lun, 14 de jun de 2021 a las 16:57:08 PM, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:Hi Jairo, It should be ok now.Yes, thank you.
by Jairo Llopis - 08:36 - 15 Jun 2021 -
Re: Proposing myself as PSC for Document
Hi Jairo, It should be ok now.-sbiOn Mon, Jun 14, 2021 at 8:32 AM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:El jue, 10 de jun de 2021 a las 10:27:40 AM, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:Let me know if you have not received the GitHub invite by tomorrow.I still don't have it._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Stéphane Bidoul - 06:56 - 14 Jun 2021 -
Re: Proposing myself as PSC for Document
El jue, 10 de jun de 2021 a las 10:27:40 AM, Stéphane Bidoul <stephane.bidoul@acsone.eu> escribió:Let me know if you have not received the GitHub invite by tomorrow.I still don't have it.
by Jairo Llopis - 08:31 - 14 Jun 2021 -
Re: Proposing myself as PSC for Document
+1
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, CanadaLe jeu. 10 juin 2021 à 02:32, Jairo Llopis <jairo.llopis@tecnativa.com> a écrit :Hello, I'm recently quite active on the dms repo, and I see it could use an extra maintainer. I propose myself.https://github.com/Yajo <-- meThanks everyone!_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Bruno Joliveau - 12:51 - 10 Jun 2021 -
Re: Proposing myself as PSC for Document
Let me know if you have not received the GitHub invite by tomorrow.-sbiOn Thu, Jun 10, 2021 at 12:12 PM Jairo Llopis <jairo.llopis@tecnativa.com> wrote:Good, so could somebody actually do it please? :D
El jue, 10 de jun de 2021 a las 07:47:37 AM, Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com> escribió:+1Le jeu. 10 juin 2021 à 09:11, Harald Panten Lopez <harald.panten@sygel.es> a écrit :+1!El jue, 10 jun 2021 a las 8:52, Enric Tobella (<etobella@creublanca.es>) escribió:+1 obviously!!On 10 Jun 2021 08:42, "Mignon, Laurent" <laurent.mignon@acsone.eu> wrote:+1On Thu, Jun 10, 2021 at 8:37 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:+1Le jeu. 10 juin 2021 à 08:32, Jairo Llopis <jairo.llopis@tecnativa.com> a écrit :Hello, I'm recently quite active on the dms repo, and I see it could use an extra maintainer. I propose myself.https://github.com/Yajo <-- meThanks everyone!_______________________________________________
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
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
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
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 Stéphane Bidoul - 12:26 - 10 Jun 2021
-
-
where can I list/edit bankaccounts in V14 in the community edition?
Hi there I would like to edit an existing bank account for a V14 community installation. I can not find out where to do this, and the documentation I find online assumes, that Accounting is installed, which only is available for the enterprise version. thanks Robert
by Robert Rottermann - 02:56 - 4 Jun 2021-
Re: where can I list/edit bankaccounts in V14 in the community edition?
in the address bookcheers,DominiqueOn Fri, 4 Jun 2021 at 20:57, robert rottermann <robert@redcor.ch> wrote:Hi there I would like to edit an existing bank account for a V14 community installation. I can not find out where to do this, and the documentation I find online assumes, that Accounting is installed, which only is available for the enterprise version. thanks Robert
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by dominique.k - 04:31 - 5 Jun 2021
-
-
where can I list/edit bankaccounts in V14 in the community edition?
Hi there I would like to edit an existing bank account for a V14 community installation. I can not find out where to do this, and the documentation I find online assumes, that Accounting is installed, which only is available for the enterprise version. thanks Robert
by robert - 02:56 - 4 Jun 2021 -
recurring report
Hi,I am looking to provide an interface to generate reports periodically.context:From an agreement, manage the generation and sending of monthly or quarterly report to a party set in the agreement.Do we have something that could help in OCA?thank you--Yves Goldbergodoo| Official Partner - OCA delegateOpen Source ERP, CRM & CMST +972 (3) 720 8818
M +972 (55) 966 1405T +32 (2) 588 2500--
by Yves Goldberg - 08:30 - 2 Jun 2021-
Re: recurring report
Tnx for the feedback Holger & sorry if I wasn't clear enough.There is a custom model "consumptions" and I would like to give the user the ability to configure the periodic generation and sending of some specific report to a res_partner defined in the agreement.The user would click to add a new periodic report. Fill in the settings and select a report to be sent.--Yves Goldberg------- Original message -----From: Holger Brunn <mail@hunki-enterprises.com>To: Contributors <contributors@odoo-community.org>Subject: Re: recurring reportDate: Wednesday, June 02, 2021 18:27> From an agreement, manage the generation and sending of monthly or quarterly > report to a party set in the agreement. Do we have something that could > help in OCA? I think that's pretty much standard Odoo: Create a server action of type email (https://github.com/OCA/OCB/blob/14.0/addons/mail/models/ir_actions.py#L17), create a mail template pointing to your report (https://github.com/OCA/OCB/ blob/14.0/addons/mail/models/mail_template.py#L56), and stick the whole thing into an automated action (https://github.com/OCA/OCB/blob/14.0/addons/ base_automation/models/base_automation.py#L39) calling the action based on your period. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
_______________________________________________Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribeAttachments:- signature.asc
by Yves Goldberg - 09:10 - 4 Jun 2021 - signature.asc
-
Re: recurring report
> From an agreement, manage the generation and sending of monthly or quarterly > report to a party set in the agreement. Do we have something that could > help in OCA? I think that's pretty much standard Odoo: Create a server action of type email (https://github.com/OCA/OCB/blob/14.0/addons/mail/models/ir_actions.py#L17), create a mail template pointing to your report (https://github.com/OCA/OCB/ blob/14.0/addons/mail/models/mail_template.py#L56), and stick the whole thing into an automated action (https://github.com/OCA/OCB/blob/14.0/addons/ base_automation/models/base_automation.py#L39) calling the action based on your period. -- Your partner for the hard Odoo problems https://hunki-enterprises.com
by Holger Brunn - 05:26 - 2 Jun 2021
-
-
Access to runbot1, runbot1-2 and runbot1-3
Hello everyone, Our hoster informed me this morning that a network switch fault is causing an outage on one of the runbot servers of the OCA. I redirected the web frontend to a different server, but builds on runbot1, runbot1-2 and runbot1-3 could be unreachable until the equipment is replaced. I'm sorry for the inconvenience and will post an update when I get more information from the hoster. -- 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 - 08:25 - 31 May 2021-
Re: Access to runbot1, runbot1-2 and runbot1-3
Thanks, Alexandre!--
Virginie0477/64.17.20-------- Message initial --------De: Alexandre Fayolle <alexandre.fayolle@camptocamp.com>Répondre à: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>À: Contributors <contributors@odoo-community.org>Objet: Re: Access to runbot1, runbot1-2 and runbot1-3Date: Mon, 31 May 2021 13:16:54 -0000Hello,
situation is back to normal.
Best regards
Alexandre
On 31/05/2021 08:24, Alexandre Fayolle wrote:
> Hello everyone,
>
> Our hoster informed me this morning that a network switch fault is
> causing an outage on one of the runbot servers of the OCA. I redirected
> the web frontend to a different server, but builds on runbot1, runbot1-2
> and runbot1-3 could be unreachable until the equipment is replaced.
>
> I'm sorry for the inconvenience and will post an update when I get more
> information from the hoster.
>
--
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 Virginie Dewulf. - 03:21 - 31 May 2021 -
Re: Access to runbot1, runbot1-2 and runbot1-3
Hello, situation is back to normal. Best regards Alexandre On 31/05/2021 08:24, Alexandre Fayolle wrote: > Hello everyone, > > Our hoster informed me this morning that a network switch fault is > causing an outage on one of the runbot servers of the OCA. I redirected > the web frontend to a different server, but builds on runbot1, runbot1-2 > and runbot1-3 could be unreachable until the equipment is replaced. > > I'm sorry for the inconvenience and will post an update when I get more > information from the hoster. > -- 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 - 03:15 - 31 May 2021
-
-
Combined view for view List and view Timeline
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 



by Sandip Mangukiya - 01:30 - 29 May 2021-
Re: Combined view for view List and view Timeline
I wonder if you could do something real simple like have a stored functional field called planned_or_unplanned_date / planned_unplanned or something. If it is unplanned set the date to something which is viewable on timeline with its own swim lane, otherwise set it to the planned date. So that way you can see it and drag drop. Have an inverse which sets the planned date when moved.On Sun, May 30, 2021 at 4:42 AM Sandip Mangukiya <smangukiya@opensourceintegrators.com> wrote:Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)SANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 


On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.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 Graeme Gellatly - 11:16 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Hi Pedro, We have put that option on the table as well. Thanks for confirming it as valid :)SANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 


On Sat, May 29, 2021 at 12:56 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.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 Sandip Mangukiya - 06:41 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Thank you, Daniel, I did look at that option and will require work on top of that in order to communicate with each other.On Sat, May 29, 2021, 12:47 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.--drNo dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 



_______________________________________________
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 Sandip Mangukiya - 06:35 - 29 May 2021 -
Re: Combined view for view List and view Timeline
The view by definition is a single thing. The dashboard suggested by Daniel combines view, but with no interaction between them.The best approach is to expand timeline view for having a placeholder to show the records that doesn't have a value for the field that you are grouping (or you can add an option for setting this field), and present there such records in a different way (not attached to any date component), and allowing to drag and drop. The bad part of this is that you need JS + Odoo JS framework skills for it.Regards.
by Pedro M. Baeza - 09:55 - 29 May 2021 -
Re: Combined view for view List and view Timeline
Hello Sandip, you could try the”board” view, that allows to compose several views in the same page.--drNo dia 29/05/2021, às 00:31, Sandip Mangukiya <smangukiya@opensourceintegrators.com> escreveu:
Hello Contributors,I would like to see if there are any pointers for the below requirements, thanks in advance.In Field Service, we are using the Timeline view (https://github.com/OCA/web/tree/14.0/web_timeline) to schedule field service orders, which is working great.but we need to show view List side by side of the timeline in order to drag and drop from list view to timeline for orders which are not scheduled yet. In order to schedule them faster and giving users more flexibility.I find one paid app web_splitview but has limited features like it doesn't support search function, limited to some views, etc.Have a good weekend!SandipSANDIP MANGUKIYA
TEAM LEAD MANAGERO: 1.855.877.2377
E: SMangukiya@OpenSourcelntegrators.comP.O. BOX 940, HIGLEY, AZ 85236 



_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Daniel Reis - 09:46 - 29 May 2021
-
-
question about payroll and attendance
Hello, I was wondering if there can be a link between payroll and attendances (hr.attendance) in Odoo ? The payroll module has a link with attendance (work calendar attendences) but not hr.attendences, AFAICT, so it seems weird to not be able to record overtime. But maybe I'm missing something obvious? -- 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 - 11:06 - 27 May 2021 -
[Compta] Generation des FEC et non assujetti TVA
Hello,(English below)J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?
Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?Cordialement
------- (English version)I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?
Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?Regards--Mathieu
by mathieu - 10:25 - 27 May 2021-
Re: [Compta] Generation des FEC et non assujetti TVA
Hi Mathieu,Alexis De lattre (OCA responsible of l10n_france) worked today on that point (it seems) for v14.Could you review and talk on this PR ? https://github.com/OCA/l10n-france/pull/288kind regards.GRAP - Service informatique (Groupement Régional Alimentaire de Proximité)Site Web | FramaSphere | Facebook
3 Grande rue des Feuillants, 69001 Lyon
Standard : (+33) 09.72.32.33.17Service Informatique : (+33) 09.73.79.64.40Astreinte Informatique : (+33) 06.81.85.61.43Member of the OCA (Odoo Community Association)Le jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :Hello,(English below)J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?
Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?Cordialement
------- (English version)I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?
Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?Regards--Mathieu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sylvain LE GAL - 11:01 - 28 May 2021 -
Re: [Compta] Generation des FEC et non assujetti TVA
You're right, generating FEC should also work for companies without VAT.I fixed it in this PR on l10n_fr_fec_oca (the OCA "improved" version to generate FEC) for odoo v14.0 :You can backport it to v10, it's very easy.AlexisLe jeu. 27 mai 2021 à 10:26, Mathieu C. <mathieu@matmicro.net> a écrit :Hello,(English below)J'utilise une version Odoo 10, pour une entreprise qui n'est pas assujettie à la TVA, comment générer les Fichiers d'Ecriture Comptable (FEC) ?
Actuellement le systeme oblige à rentrer un numéro de TVA.
Impossible de générer le FEC sans numéro de TVA.
Quelle est la méthode pour y remèdier ?Cordialement
------- (English version)I am using an Odoo 10 version, for a company that is not subject to VAT, how do I generate the Accounting Entry Files (FEC)?
Currently the system requires entering a VAT number.
Cannot generate FEC without VAT number.
What is the method to remedy it?Regards--Mathieu_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Alexis de Lattre - 11:01 - 28 May 2021
-
-
Problem with fiscal year starting on 1 October to 30 September and Odoo BI Report
Dear community,For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.Anyone have better way to achieve this?Many thanks,Kitti U.
by Kitti Upariphutthiphong - 05:01 - 26 May 2021-
Re: Problem with fiscal year starting on 1 October to 30 September and Odoo BI Report
Just for the finding record, OCA has a solution which is based on date_range. Which requires to work model by model.On Wed, May 26, 2021 at 10:01 PM Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:Dear community,For the fiscal year that starts from October and ending September. So, on the Odoo BI view, we expect to see that 2021 / Q1 means 1 October to 31 December.I think this is not possible in Odoo, as it only use "Date" to interpret the report, right?To achieve the expected result, I can only think of adding fiscalyear_id, and quarter as computed stored field in every models needed, which is very inefficient.Anyone have better way to achieve this?Many thanks,Kitti U._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 05:05 - 29 May 2021
-
-
v14 accounting changes
Hi all,
We started to take a closer look at the v14 accounting.
We are not delighted…to put it mildly.
We were wondering if any of you had something ongoing or planned to address some of the following points that we have encountered so far:
* Major changes in the taxe logic
* Use of a transit account in the bank reconcile process
* Cancel state of accounting entries
* Creation of entries that are then cancelled when a draft invoice is cancelled
On a more general basis, how do you plan to approach the migration to v14 for the accounting part considering the risk?
Looking forward to hear your insights,
Thanks!--
Quentin Lavallee - Chargé de projetsNUMIGI SOLUTIONS INC.(514) 317-7944Longueuil, Québec, Canada
by Quentin Lavallée-Bourdeau - 04:31 - 21 May 2021-
Re: v14 accounting changes
I'm not actually using v14, but I've play with it a little bit some time ago and there were some things that IMHO where a loss (between v13 and v14).- Now a payment only impacts the outstanding account (cash and bank journals). So, to see the actual balance of those journals
- you must use statements (I like statements but I don't like to be force to use them on all customers and all journals)
- after the v14 release, odoo add a patch that allows you to select the same journal liquidity account as the outstanding account as a way to bypass the outstanding. If you do so:
- The journal dashboard gives wrong data
- you can't use statements for this journal, and if you decide to use them later you are not going to be able to reconcile any previous payment.
- also, the setup to bypass outstanding is not user friendly
- payment + reconcile later vs paying from reconciliation
- In the previous version, if you pay from a bank statement a bill (black line) or if you create the payment and later reconcile it (blue line) the behaviour was the same, one payment. The only difference was the workflow
- on v14, if you create the payment and reconcile later you will have one payment + one statement journal entry. If you pay from the statement you only have one journal entry
- I don't like it because:
- what odoo is doing is not the same regarding the workflow
- If you pay from statements you don't have a payment so you won't see the payment on your payments lists and also you can't send a receipt/payment
- If we make the payment before we have 2 journal entries (the one from the payment plus the one from the statement) for the same operation. In previous version being one journal entry was clearer for me
That's my quick feeback for v14 reconciliationEl vie, 21 de may. de 2021 a la(s) 12:27, Oleg Kuryan (oleg.kuryan@xpansa.com) escribió:I agree with Pedro. I do not see problem statement in an email. Moreover in all above features I see only pluses that finally started to work properly.--On Fri, 21 May 2021 at 17:42, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Unless you specify the problems, I don't see such problems in the new "features", except train users on them.If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
///Best Regards,
Oleg Kuryan/// CEO & COO | ventor.tech | Building Personalized Inventory and Product Management System
/// mail : oleg.kuryan@xpansa.com
/// phone : +375293358638
/// skype : kuryan.oleg_______________________________________________
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 - 12:45 - 23 May 2021 -
Re: v14 accounting changes
I agree with Pedro. I do not see problem statement in an email. Moreover in all above features I see only pluses that finally started to work properly.--On Fri, 21 May 2021 at 17:42, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:Unless you specify the problems, I don't see such problems in the new "features", except train users on them.If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
///Best Regards,
Oleg Kuryan/// CEO & COO | ventor.tech | Building Personalized Inventory and Product Management System
/// mail : oleg.kuryan@xpansa.com
/// phone : +375293358638
/// skype : kuryan.oleg
by Oleg Kuryan - 05:25 - 21 May 2021 -
Re: v14 accounting changes
Unless you specify the problems, I don't see such problems in the new "features", except train users on them.If you go to specific things, then the debate can go on. You can do it by topic for not getting a laberintic thread.Regards.
by Pedro M. Baeza - 04:40 - 21 May 2021
-
-
Migration to Odoo 14: replacing size attribute of Char field
Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino
by Simone Rubino - 12:56 - 21 May 2021-
Re: Migration to Odoo 14: replacing size attribute of Char field
Thanks all for your suggestions :)
I chose to move the constraint to UI; unfortunately the Char widget did not allow to set the size option so I implemented https://github.com/OCA/web/pull/1952 that allows it.On Fri, 21 May 2021 at 15:01, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:The warning is from Odoo, not from linters, so #noqa is not valid.El vie., 21 may. 2021 14:52, Graeme Gellatly <gdgellatly@gmail.com> escribió:I think if the use case is valid and no convenient good alternative exists then the easiest solution is# noqawith a note.On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:how about api.onchange ?it would work on form modification.--On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.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
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Simone Rubino - 05:26 - 14 Jun 2021 -
Re: Migration to Odoo 14: replacing size attribute of Char field
The warning is from Odoo, not from linters, so #noqa is not valid.El vie., 21 may. 2021 14:52, Graeme Gellatly <gdgellatly@gmail.com> escribió:I think if the use case is valid and no convenient good alternative exists then the easiest solution is# noqawith a note.On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:how about api.onchange ?it would work on form modification.--On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.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
by Pedro M. Baeza - 03:00 - 21 May 2021 -
Re: Migration to Odoo 14: replacing size attribute of Char field
I think if the use case is valid and no convenient good alternative exists then the easiest solution is# noqawith a note.On Sat, May 22, 2021 at 12:16 AM Dominique k <dominique.k@elico-corp.com.sg> wrote:how about api.onchange ?it would work on form modification.--On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.com
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Graeme Gellatly - 02:51 - 21 May 2021 -
Re: Migration to Odoo 14: replacing size attribute of Char field
how about api.onchange ?it would work on form modification.--On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <simone.rubino@agilebg.com> wrote:Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.
that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.com
by dominique.k - 02:11 - 21 May 2021 -
Re: Migration to Odoo 14: replacing size attribute of Char field
If I don't remember bad, there's a warning logged saying the size is deprecated, and that's why it's included in the migration guide.I think the alternative is to put it on the view, not on the field.Regards.
by Pedro M. Baeza - 01:01 - 21 May 2021
-
-
Stock valuation by location drilldown
Hello, I might be stupid not to see how todo that but let me ask. We have locations design in a hierarchical way (as I guess is designed). So for example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this hierarchy (shelfs). Is there a simple way to do stock valuation by some sort of drilldown? Or at least to get stock value of top location including all its children recursively? The need stems from the requirement to compare this calculation to other Inventory software which is to be replaced by Odoo. But first we have to be sure the calculations match. Thank you. Best regards Radovan Skolnik
by Radovan Skolnik - 11:51 - 19 May 2021-
Re: Stock valuation by location drilldown
Aaron, YES! Not exactly but very close. It reports on product quantity while I need value but it is easy to modify. Also uses that magic child_of for searching in read_group which I wanted to ask about (had it in my email but deleted it). Thank you very much! Best regards Radovan On streda 19. mája 2021 14:22:07 CEST Aarón Henríquez Quintana wrote: > I think this is what you are looking for, isn't it? > https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua > ntity_by_location [1] On Wed, 19 May 2021 at 14:07, Radovan Skolnik < > radovan@skolnik.info [2] > wrote: I guess I understand but: as I described > in my initial post I need to be able to make the sum of stock.quant values > recursively. Let's say a single location represents a warehouse or store > room (first level location), with racks (second level location) and shelfs > (third level location). Now I need to be able to see value of that top > level location which should incorporate value of all of its children and > their children... Hope I am making myself clear. > Best regards > Radovan > > On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote: > > If your context has a warehouse, or a location_id, then all the figures > > that are computed on product will be contextually constrained based on > > that context. Exactly what compute figures are available on > > product.product varies from version to version, but the context should > > already be enough to achieve what you need. > > > > > > > > > > > > > > > > > > > > > > > > > > * Richard deMeester * > > > > Senior Development Analyst > > > > * WilldooIT Pty Ltd ** * > > * E: * None [1] richard.demeester@willdooit.com [3] > > * M: * +61 403 76 76 76 > > * P: * +61 3 9135 1900 > > * A: * 10/435 Williamstown Road, Port Melbourne, Vic 3207 > > > > > > > > > > > > > > Making growth through technology easy * > > > > > > > > * * > > * DISCLAIMER * | This electronic message together with any attachments is > > confidential. If you are not the recipient, do not copy, disclose, or use > > the contents in any way. Please also advise us by e-mail that you have > > received this message in error and then please destroy this email and any > > of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes > > made to this message and/or any attachments after sending by WilldooIT > > Pty. > > Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all > > liability for virus or anything similar in this email or attachment. > > > > > > > > > > > > > > > > *From:* Radovan Skolnik < radovan@skolnik.info [4] > > > *Sent:* Wednesday, 19 May 2021 9:47 PM > > *To:* Contributors < contributors@odoo-community.org [5] > > > *Subject:* Re: Stock valuation by location drilldown > > > > This idea came to mind (please comment on its viability): in stock_account > > there is computed field value of stock.quant that calculates the value. > > stock.location has quant_ids. So it should be easily possible to create a > > computed field for stock.location that would make sum of its stock.quants > > as well as its child stock.locations. I guess there could be some magic > > that would allow to prevent recursive call to sum of stock.location > > children. Any pointers on how to do that? > > Thank you. Best regards > > Radovan Skolnik > > > > On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote: > > > Hello, > > > I might be stupid not to see how todo that but let me ask. We have > > > locations design in a hierarchical way (as I guess is designed). So for > > > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts > > > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this > > > hierarchy (shelfs). Is there a simple way to do stock valuation by some > > > sort of drilldown? Or at least to get stock value of top location > > > including all its children recursively? The need stems from the > > > requirement to compare this calculation to other Inventory software > > > which > > > is to be replaced by Odoo. But first we have to be sure the calculations > > > match. Thank you. Best regards > > > Radovan Skolnik > > > > > > > > > _______________________________________________ > > > Mailing-List: https://odoo-community.org/groups/contributors-15 [6] [1] > > > Post to: mailto: contributors@odoo-community.org [7] > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [8] [2] > > > > > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 [9] > > > [2] https://odoo-community.org/groups?unsubscribe [10] > > > > _______________________________________________ > > > > Mailing-List: > > https://odoo-community.org/groups/contributors-15 [11] [2] > > > > Post to: mailto: contributors@odoo-community.org [12] > > > > Unsubscribe: > > https://odoo-community.org/groups?unsubscribe [13] [3] > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [14] [4] > > Post to: mailto: contributors@odoo-community.org [15] > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [16] [5] > > > > > > > > [1] mailto: geoff.szentesi@willdooit.com [17] > > [2] https://odoo-community.org/groups/contributors-15 [18] > > [3] https://odoo-community.org/groups?unsubscribe [19] > > [4] https://odoo-community.org/groups/contributors-15 [20] > > [5] https://odoo-community.org/groups?unsubscribe [21] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [22] > Post to: mailto: contributors@odoo-community.org [23] > Unsubscribe: https://odoo-community.org/groups?unsubscribe [24] > > -- > Aaron Henríquez Quintana * Technical Consultant ahenriquez@forgeflow.com > [25] Twitter: /AaronHForgeFlow | Linkedin: / > aaron-henriquez-quintana-84299869 None [26] > None [27] None [28] None [29] None [30] > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [31] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [32] > > > > [1] > https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_qua > ntity_by_location [2] mailto:radovan@skolnik.info > [3] mailto:richard.demeester@willdooit.com > [4] mailto:radovan@skolnik.info > [5] mailto:contributors@odoo-community.org > [6] https://odoo-community.org/groups/contributors-15 > [7] mailto:contributors@odoo-community.org > [8] https://odoo-community.org/groups?unsubscribe > [9] https://odoo-community.org/groups/contributors-15 > [10] https://odoo-community.org/groups?unsubscribe > [11] https://odoo-community.org/groups/contributors-15 > [12] mailto:contributors@odoo-community.org > [13] https://odoo-community.org/groups?unsubscribe > [14] https://odoo-community.org/groups/contributors-15 > [15] mailto:contributors@odoo-community.org > [16] https://odoo-community.org/groups?unsubscribe > [17] mailto:geoff.szentesi@willdooit.com > [18] https://odoo-community.org/groups/contributors-15 > [19] https://odoo-community.org/groups?unsubscribe > [20] https://odoo-community.org/groups/contributors-15 > [21] https://odoo-community.org/groups?unsubscribe > [22] https://odoo-community.org/groups/contributors-15 > [23] mailto:contributors@odoo-community.org > [24] https://odoo-community.org/groups?unsubscribe > [25] mailto:judit.valls@forgeflow.com > [26] https://www.forgeflow.com/ > [27] https://github.com/ForgeFlow > [28] https://www.linkedin.com/company/2415389 > [29] https://www.youtube.com/channel/UC6tv8_do-x2jg2nDx4H_DnA > [30] https://twitter.com/ForgeFlow > [31] https://odoo-community.org/groups/contributors-15 > [32] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 02:36 - 19 May 2021 -
Re: Stock valuation by location drilldown
I think this is what you are looking for, isn't it? https://github.com/OCA/stock-logistics-reporting/tree/13.0/stock_report_quantity_by_locationOn Wed, 19 May 2021 at 14:07, Radovan Skolnik <radovan@skolnik.info> wrote:I guess I understand but: as I described in my initial post I need to be able to make the sum of stock.quant values recursively. Let's say a single location represents a warehouse or store room (first level location), with racks (second level location) and shelfs (third level location). Now I need to be able to see value of that top level location which should incorporate value of all of its children and their children... Hope I am making myself clear. Best regards Radovan On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote: > If your context has a warehouse, or a location_id, then all the figures that > are computed on product will be contextually constrained based on that > context. Exactly what compute figures are available on product.product > varies from version to version, but the context should already be enough to > achieve what you need. > > > > > > > > > > > > > * Richard deMeester * > > Senior Development Analyst > > * WilldooIT Pty Ltd ** * > * E: * None [1] richard.demeester@willdooit.com > * M: * +61 403 76 76 76 > * P: * +61 3 9135 1900 > * A: * 10/435 Williamstown Road, Port Melbourne, Vic 3207 > > > > > > > Making growth through technology easy * > > > > * * > * DISCLAIMER * | This electronic message together with any attachments is > confidential. If you are not the recipient, do not copy, disclose, or use > the contents in any way. Please also advise us by e-mail that you have > received this message in error and then please destroy this email and any > of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes > made to this message and/or any attachments after sending by WilldooIT Pty. > Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all > liability for virus or anything similar in this email or attachment. > > > > > > > > *From:* Radovan Skolnik <radovan@skolnik.info> > *Sent:* Wednesday, 19 May 2021 9:47 PM > *To:* Contributors <contributors@odoo-community.org> > *Subject:* Re: Stock valuation by location drilldown > > This idea came to mind (please comment on its viability): in stock_account > there is computed field value of stock.quant that calculates the value. > stock.location has quant_ids. So it should be easily possible to create a > computed field for stock.location that would make sum of its stock.quants as > well as its child stock.locations. I guess there could be some magic that > would allow to prevent recursive call to sum of stock.location children. > Any pointers on how to do that? > Thank you. Best regards > Radovan Skolnik > > On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote: > > Hello, > > I might be stupid not to see how todo that but let me ask. We have > > locations design in a hierarchical way (as I guess is designed). So for > > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts > > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this > > hierarchy (shelfs). Is there a simple way to do stock valuation by some > > sort of drilldown? Or at least to get stock value of top location > > including all its children recursively? The need stems from the > > requirement to compare this calculation to other Inventory software which > > is to be replaced by Odoo. But first we have to be sure the calculations > > match. Thank you. Best regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [1] > > Post to: mailto:contributors@odoo-community.org > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2] > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 > > [2] https://odoo-community.org/groups?unsubscribe > > _______________________________________________ > Mailing-List: > https://odoo-community.org/groups/contributors-15 [2] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: > https://odoo-community.org/groups?unsubscribe [3] > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [4] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] > > > > [1] mailto:geoff.szentesi@willdooit.com > [2] https://odoo-community.org/groups/contributors-15 > [3] https://odoo-community.org/groups?unsubscribe > [4] https://odoo-community.org/groups/contributors-15 > [5] 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
--Aaron Henríquez QuintanaTechnical ConsultantTwitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869
by Aarón Henríquez - 02:21 - 19 May 2021 -
Re: Stock valuation by location drilldown
I guess I understand but: as I described in my initial post I need to be able to make the sum of stock.quant values recursively. Let's say a single location represents a warehouse or store room (first level location), with racks (second level location) and shelfs (third level location). Now I need to be able to see value of that top level location which should incorporate value of all of its children and their children... Hope I am making myself clear. Best regards Radovan On streda 19. mája 2021 13:56:49 CEST Richard deMeester wrote: > If your context has a warehouse, or a location_id, then all the figures that > are computed on product will be contextually constrained based on that > context. Exactly what compute figures are available on product.product > varies from version to version, but the context should already be enough to > achieve what you need. > > > > > > > > > > > > > * Richard deMeester * > > Senior Development Analyst > > * WilldooIT Pty Ltd ** * > * E: * None [1] richard.demeester@willdooit.com > * M: * +61 403 76 76 76 > * P: * +61 3 9135 1900 > * A: * 10/435 Williamstown Road, Port Melbourne, Vic 3207 > > > > > > > Making growth through technology easy * > > > > * * > * DISCLAIMER * | This electronic message together with any attachments is > confidential. If you are not the recipient, do not copy, disclose, or use > the contents in any way. Please also advise us by e-mail that you have > received this message in error and then please destroy this email and any > of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes > made to this message and/or any attachments after sending by WilldooIT Pty. > Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all > liability for virus or anything similar in this email or attachment. > > > > > > > > *From:* Radovan Skolnik <radovan@skolnik.info> > *Sent:* Wednesday, 19 May 2021 9:47 PM > *To:* Contributors <contributors@odoo-community.org> > *Subject:* Re: Stock valuation by location drilldown > > This idea came to mind (please comment on its viability): in stock_account > there is computed field value of stock.quant that calculates the value. > stock.location has quant_ids. So it should be easily possible to create a > computed field for stock.location that would make sum of its stock.quants as > well as its child stock.locations. I guess there could be some magic that > would allow to prevent recursive call to sum of stock.location children. > Any pointers on how to do that? > Thank you. Best regards > Radovan Skolnik > > On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote: > > Hello, > > I might be stupid not to see how todo that but let me ask. We have > > locations design in a hierarchical way (as I guess is designed). So for > > example we have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts > > / RowNo / ShelfNo. Now the stock resides at the leaf nodes in this > > hierarchy (shelfs). Is there a simple way to do stock valuation by some > > sort of drilldown? Or at least to get stock value of top location > > including all its children recursively? The need stems from the > > requirement to compare this calculation to other Inventory software which > > is to be replaced by Odoo. But first we have to be sure the calculations > > match. Thank you. Best regards > > Radovan Skolnik > > > > > > _______________________________________________ > > Mailing-List: https://odoo-community.org/groups/contributors-15 [1] > > Post to: mailto:contributors@odoo-community.org > > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2] > > > > > > > > [1] https://odoo-community.org/groups/contributors-15 > > [2] https://odoo-community.org/groups?unsubscribe > > _______________________________________________ > Mailing-List: > https://odoo-community.org/groups/contributors-15 [2] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: > https://odoo-community.org/groups?unsubscribe [3] > > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [4] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] > > > > [1] mailto:geoff.szentesi@willdooit.com > [2] https://odoo-community.org/groups/contributors-15 > [3] https://odoo-community.org/groups?unsubscribe > [4] https://odoo-community.org/groups/contributors-15 > [5] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 02:05 - 19 May 2021 -
Re: Stock valuation by location drilldown
If your context has a warehouse, or a location_id, then all the figures that are computed on product will be contextually constrained based on that context. Exactly what compute figures are available on product.product varies from version to version, but the context should already be enough to achieve what you need.
Richard deMeester
Senior Development Analyst
WilldooIT Pty Ltd
E: richard.demeester@willdooit.com
M: +61 403 76 76 76
P: +61 3 9135 1900
A: 10/435 Williamstown Road, Port Melbourne, Vic 3207
Making growth through technology easy
DISCLAIMER | This electronic message together with any attachments is confidential. If you are not the recipient, do not copy, disclose, or use the contents in any way. Please also advise us by e-mail that you have received this message in error and then please destroy this email and any of its attachments. WilldooIT Pty. Ltd. is not responsible for any changes made to this message and/or any attachments after sending by WilldooIT Pty. Ltd. WilldooIT Pty. Ltd. use virus scanning software but exclude all liability for virus or anything similar in this email or attachment.
From: Radovan Skolnik <radovan@skolnik.info>
Sent: Wednesday, 19 May 2021 9:47 PM
To: Contributors <contributors@odoo-community.org>
Subject: Re: Stock valuation by location drilldownThis idea came to mind (please comment on its viability): in stock_account there is computed field value of stock.quant that calculates the value. stock.location has quant_ids. So it should be easily possible to create a computed field for stock.location that would make sum of its stock.quants as well as its child stock.locations. I guess there could be some magic that would allow to prevent recursive call to sum of stock.location children. Any pointers on how to do that? Thank you. Best regards Radovan Skolnik On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote: > Hello, > I might be stupid not to see how todo that but let me ask. We have locations > design in a hierarchical way (as I guess is designed). So for example we > have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo / > ShelfNo. Now the stock resides at the leaf nodes in this hierarchy > (shelfs). Is there a simple way to do stock valuation by some sort of > drilldown? Or at least to get stock value of top location including all its > children recursively? The need stems from the requirement to compare this > calculation to other Inventory software which is to be replaced by Odoo. > But first we have to be sure the calculations match. Thank you. Best > regards > Radovan Skolnik > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [1] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2] > > > > [1] https://odoo-community.org/groups/contributors-15 > [2] 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 "Richard deMeester" <richard.demeester@willdooit.com> - 01:51 - 19 May 2021 -
Re: Stock valuation by location drilldown
This idea came to mind (please comment on its viability): in stock_account there is computed field value of stock.quant that calculates the value. stock.location has quant_ids. So it should be easily possible to create a computed field for stock.location that would make sum of its stock.quants as well as its child stock.locations. I guess there could be some magic that would allow to prevent recursive call to sum of stock.location children. Any pointers on how to do that? Thank you. Best regards Radovan Skolnik On streda 19. mája 2021 11:51:45 CEST Radovan Skolnik wrote: > Hello, > I might be stupid not to see how todo that but let me ask. We have locations > design in a hierarchical way (as I guess is designed). So for example we > have Goods / RowNo / ShelfNo hierarchy, similarly Spare Parts / RowNo / > ShelfNo. Now the stock resides at the leaf nodes in this hierarchy > (shelfs). Is there a simple way to do stock valuation by some sort of > drilldown? Or at least to get stock value of top location including all its > children recursively? The need stems from the requirement to compare this > calculation to other Inventory software which is to be replaced by Odoo. > But first we have to be sure the calculations match. Thank you. Best > regards > Radovan Skolnik > > > _______________________________________________ > Mailing-List: https://odoo-community.org/groups/contributors-15 [1] > Post to: mailto:contributors@odoo-community.org > Unsubscribe: https://odoo-community.org/groups?unsubscribe [2] > > > > [1] https://odoo-community.org/groups/contributors-15 > [2] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 01:46 - 19 May 2021
-
-
Accounting PSC Member apply
Hi Community,I would like to apply for PSC member on Accounting repositories.Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.You can have a look at my profile https://github.com/HaraldPantenTHX!--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 10:16 - 19 May 2021-
Re: Accounting PSC Member apply
Hi,I've added you to the PSC. you should get an invitation soon.CheersOn Wed, May 19, 2021 at 10:17 AM Harald Panten Lopez <harald.panten@sygel.es> wrote:Hi Community,I would like to apply for PSC member on Accounting repositories.Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.You can have a look at my profile https://github.com/HaraldPantenTHX!--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Simone OrsiFull stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
by Simone Orsi - 09:36 - 20 May 2021 -
Re: Accounting PSC Member apply
+1Il gio 20 mag 2021, 19:12 Enric Tobella <etobella@creublanca.es> ha scritto:+1On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:+1On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:Hi Community,I would like to apply for PSC member on Accounting repositories.Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.You can have a look at my profile https://github.com/HaraldPantenTHX!--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
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
by Sergio Corato - 07:21 - 20 May 2021 -
Re: Accounting PSC Member apply
+1On 20 May 2021 18:27, Kitti Upariphutthiphong <kittiu@ecosoft.co.th> wrote:+1On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:Hi Community,I would like to apply for PSC member on Accounting repositories.Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.You can have a look at my profile https://github.com/HaraldPantenTHX!--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
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 - 07:10 - 20 May 2021 -
Re: Accounting PSC Member apply
+1On Wed, May 19, 2021, 15:17 Harald Panten Lopez <harald.panten@sygel.es> wrote:Hi Community,I would like to apply for PSC member on Accounting repositories.Mine is a functional profile with some technical knowledge. I'm an active member of the Community as well.You can have a look at my profile https://github.com/HaraldPantenTHX!--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Kitti Upariphutthiphong - 06:26 - 20 May 2021 -
-
-
Project consumable (v14.0)
Hi there,I've the need to follow the analytic cost of consumables per project.As far when consumables are purchase we don't know how they will be used and while creating the quotation we don't know how exactly how many consumable to be sale, I'll create a new module probably called project_consumable in oca/project repo that will let users to record used consumable that will create relevant analytic account line linked to the consumable product and project (likes hr_timesheet which record time per project/task). I'll take care we get proper analysis.I plan later to generate sale order (I know this is not very suitable. Add products in the generated invoice would make more sense in odoo... could be done in different modules anyway ) from some of those account move lines.Are there already such efforts? I'll be happy to hear your comments :)regards,
by Pierre Verkest - 10:01 - 19 May 2021-
Re: Project consumable (v14.0)
Ok then if it's very different. I don't see the conversion to account.analytic.line. For me that should be the final result (project.task.material generates account.analytic.line when an analytic account is generated). Also to force consumable instead allowing stockable/consumable is something I don't see.Regards.
by Pedro M. Baeza - 10:46 - 19 May 2021 -
Re: Project consumable (v14.0)
I've seen that module and this is why I've chosen to not use it:* I'm not sure it's the same purpose* I do not require to enforce consumable to be linked to a specific task only to the project* I'm not sure we need an extra model (`project.task.material`)for my needs and I'm a bit afraid about keep consistency between such modeland `account.analytic.line`. Or do you agree that I move `project.task.material` touse `account.analytic.line` instead ?If so I can change the behaviour and provide a migration script to smoothly go ahead.Let me know what you think !Le mer. 19 mai 2021 à 10:26, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :I would go with using and expanding if needed project_task_material.Regards._______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Pierre
by Pierre Verkest - 10:41 - 19 May 2021 -
Re: Project consumable (v14.0)
I would go with using and expanding if needed project_task_material.Regards.
by Pedro M. Baeza - 10:26 - 19 May 2021
-
-
Manufacturing Order reporting
Hi all,is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?If not, which OCA repository could I do a PR?ThanksSergio Corato
by Sergio Corato - 12:31 - 14 May 2021-
Re: Manufacturing Order reporting
Hi David,The need is for a specific report of a single product manufactured (it has a relevant value), but I'll keep that in mind, thanks!Sergio CoratoIl giorno lun 17 mag 2021 alle ore 08:57 David Beal <david.beal@akretion.com> ha scritto:Hi Sergio,A really partial response here I think, but not finished.Maybe for inspiration ?"pivot table from product which make appears disparity between theoretical component consumption and real component consumption" RegardsLe ven. 14 mai 2021 à 15:42, Sergio Corato <sergiocorato@gmail.com> a écrit :Hi Harald,thanks!Sergio CoratoIl giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:I don't remeber any report with such kind of details.I think that your PR should be in https://github.com/OCA/manufacture-reportingEl vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:Hi all,is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?If not, which OCA repository could I do a PR?ThanksSergio Corato_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
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 Sergio Corato - 10:00 - 17 May 2021 -
Re: Manufacturing Order reporting
Hi Sergio,A really partial response here I think, but not finished.Maybe for inspiration ?"pivot table from product which make appears disparity between theoretical component consumption and real component consumption" RegardsLe ven. 14 mai 2021 à 15:42, Sergio Corato <sergiocorato@gmail.com> a écrit :Hi Harald,thanks!Sergio CoratoIl giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:I don't remeber any report with such kind of details.I think that your PR should be in https://github.com/OCA/manufacture-reportingEl vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:Hi all,is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?If not, which OCA repository could I do a PR?ThanksSergio Corato_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
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 David BEAL - 08:55 - 17 May 2021 -
Re: Manufacturing Order reporting
Hi Harald,thanks!Sergio CoratoIl giorno ven 14 mag 2021 alle ore 12:52 Harald Panten Lopez <harald.panten@sygel.es> ha scritto:I don't remeber any report with such kind of details.I think that your PR should be in https://github.com/OCA/manufacture-reportingEl vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:Hi all,is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?If not, which OCA repository could I do a PR?ThanksSergio Corato_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona _______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Sergio Corato - 03:40 - 14 May 2021 -
Re: Manufacturing Order reporting
I don't remeber any report with such kind of details.I think that your PR should be in https://github.com/OCA/manufacture-reportingEl vie, 14 may 2021 a las 12:32, Sergio Corato (<sergiocorato@gmail.com>) escribió:Hi all,is there a module with a report to show the cost of a manufactured product, with cost of components at the time of production and worked times and deviations from BOM?If not, which OCA repository could I do a PR?ThanksSergio Corato_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 12:50 - 14 May 2021
-
-
Account financial reserve naming
Hi all,We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).If we can have a little feedback from some of you on our future baby name.Regards,--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 06:35 - 10 May 2021-
Re: Account financial reserve naming
Hello, A little late response, but by chance I'm working on approximately this here: <https://github.com/coopiteasy/addons/pull/222> We're considering to propose it to the OCA. Le mercredi 06 avril 2022 à 09:21 +0000, Silverstar J a écrit : > Hello All, > > I am looking for an account wallet module something like this > https://apps.odoo.com/apps/modules/13.0/odoo_website_wallet/. > Using account_wallet by acsone can we achieve something which a paid > module provides. > > Can you please suggest something. > > > > On Mon, May 17, 2021 at 1:47 PM Roussel, Denis > <denis.roussel@acsone.eu> wrote: > > Oooops, link : https://github.com/OCA/sale-workflow/pull/1583/files > > > > > > > > On Mon, May 17, 2021 at 10:11 AM Roussel, Denis > > <denis.roussel@acsone.eu> wrote: > > > That's not exactly the same purpose (we use both in our project). > > > > > > I think for v14, we can base our thinking on the new voucher > > > module in that flow (I will do soon a PR with a wallet-voucher or > > > sth similar). > > > > > > A migration PR for sale_promotion_rule is currently draft there. > > > IMHO, we need to split the coupon flow accordingly too. > > > > > > On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy > > > <raphael.reverdy@akretion.com> wrote: > > > > Hi, > > > > > > > > We addressed a similar need with (oca/sale_workflow) > > > > sale_promotion_rule. > > > > The "deposit" is simply a voucher. It can be splitted (partial > > > > use in a SO), increased, and expiration can be set. > > > > > > > > Ok for account-wallet , may be move sale_promotion_rule there? > > > > > > > > Regards, > > > > > > > > Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) > > > > <antoniomaria.vigliotti@gmail.com> a écrit : > > > > > +1 account-wallet > > > > > > > > > > Antonio M. Vigliotti > > > > > Mobile (+39) 342.8740910 > > > > > > > > > > > > > > > > > > > > Il 12/05/21 17:11, Bruno Joliveau ha scritto: > > > > > > > > > > > +1 for account-wallet > > > > > > > > > > > > Bruno Joliveau - Président > > > > > > NUMIGI SOLUTIONS INC. > > > > > > bruno.joliveau@numigi.com > > > > > > (514) 317-7944 > > > > > > > > > > > > Longueuil, Québec, Canada > > > > > > http://www.numigi.com/ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Le mer. 12 mai 2021 à 11:06, Roussel, Denis > > > > > > <denis.roussel@acsone.eu> a écrit : > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > > > > I'm requesting the creation of a new repository named > > > > > > > account-wallet. > > > > > > > > > > > > > > I hope this will help to fulfill people request. I will > > > > > > > add PR's for 14 soon. > > > > > > > > > > > > > > I think we can add it to accounting-maintainers PSC. > > > > > > > > > > > > > > > > > > > > > Thanks all for the little brainstorming. > > > > > > > > > > > > > > On Tue, May 11, 2021 at 2:45 PM Roussel, Denis > > > > > > > <denis.roussel@acsone.eu> wrote: > > > > > > > > > > > > > > > Yes. > > > > > > > > > > > > > > > > I think that will not conflict with future Odoo sale > > > > > > > > gift card (but they change their mind meantime). > > > > > > > > > > > > > > > > Maybe account-wallet (for repo)? > > > > > > > > > > > > > > > > Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul > > > > > > > > <stephane.bidoul@acsone.eu> a écrit : > > > > > > > > > > > > > > > > > wallet is an interesting name too. > > > > > > > > > > > > > > > > > > I guess it's best to create a new repo, since this is > > > > > > > > > a suite of modules covering several areas ? > > > > > > > > > > > > > > > > > > -sbi > > > > > > > > > > > > > > > > > > On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti > > > > > > > > > (gmail) <antoniomaria.vigliotti@gmail.com> wrote: > > > > > > > > > > > > > > > > > > > May be intresting for other countries, if I > > > > > > > > > > understand the request. > > > > > > > > > > > > > > > > > > > > The financial reserve is a sort of payment down > > > > > > > > > > but not specific for any order. > > > > > > > > > > > > > > > > > > > > In Italy is called "anticipo" (like payment down > > > > > > > > > > but it is not the same meaning) or portafoglio > > > > > > > > > > (Italian term for "wallet"). The account should be > > > > > > > > > > a <credit account type>. > > > > > > > > > > We have to develop a module with this feature, can > > > > > > > > > > we share the thinks ena eventually the code, if you > > > > > > > > > > agred. > > > > > > > > > > > > > > > > > > > > Antonio M. Vigliotti > > > > > > > > > > Mobile (+39) 342.8740910 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Il 11/05/21 13:37, Roussel, Denis ha scritto: > > > > > > > > > > > > > > > > > > > > > I like it. > > > > > > > > > > > > > > > > > > > > > > One thing more is the fact that that fund can be > > > > > > > > > > > partner agnostic. As it can represent a 'gift > > > > > > > > > > > voucher' which has a certain balance > > > > > > > > > > > corresponding to the voucher value (if not used > > > > > > > > > > > yet). > > > > > > > > > > > > > > > > > > > > > > Apart of that consideration, is it a good idea to > > > > > > > > > > > create a repo for those modules or to go in an > > > > > > > > > > > existing one ? > > > > > > > > > > > > > > > > > > > > > > On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul > > > > > > > > > > > <stephane.bidoul@acsone.eu> wrote: > > > > > > > > > > > > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > Maybe a good name would be account_partner_fund > > > > > > > > > > > > ? > > > > > > > > > > > > > > > > > > > > > > > > In a nutshell, we have the following concepts > > > > > > > > > > > > in these modules (as I understand it after a > > > > > > > > > > > > quick reminder from Cedric, errors and > > > > > > > > > > > > imprecisions are mine, but the general idea > > > > > > > > > > > > should be this): > > > > > > > > > > > > > > > > > > > > > > > > - funds (cagnottes) are created > > > > > > > > > > > > - a balance sheet account is used to track the > > > > > > > > > > > > funds, with all journal items in this account > > > > > > > > > > > > having a m2o to the corresponding fund + > > > > > > > > > > > > partner_id > > > > > > > > > > > > - funds can be credited with balance sheet > > > > > > > > > > > > movements (bank to fund, no VAT impact) > > > > > > > > > > > > - funds can be used as payment means > > > > > > > > > > > > - when funds expire, there is a debit fund / > > > > > > > > > > > > credit revenue, and at that moment some VAT is > > > > > > > > > > > > due > > > > > > > > > > > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > Stéphane Bidoul | @SBidoul > > > > > > > > > > > > Acsone sa/nv | http://acsone.eu/ | +32 2 888 > > > > > > > > > > > > 3120 > > > > > > > > > > > > > > > > > > > > > > > > On Mon, May 10, 2021 at 6:37 PM Roussel, Denis > > > > > > > > > > > > <denis.roussel@acsone.eu> wrote: > > > > > > > > > > > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > We want to put some modules we did to OCA, > > > > > > > > > > > > > but before we want to validate naming with > > > > > > > > > > > > > some native english speakers as some > > > > > > > > > > > > > translations are ambiguous. > > > > > > > > > > > > > > > > > > > > > > > > > > We want to modelize a financial reserve (we > > > > > > > > > > > > > named it in French 'cagnotte' - that is > > > > > > > > > > > > > translated at first sight jackpot or pot(the > > > > > > > > > > > > > ambiguous one :-) ) through account moves > > > > > > > > > > > > > that feed a waiting account. > > > > > > > > > > > > > > > > > > > > > > > > > > These entries should allow to pay invoices > > > > > > > > > > > > > later (we know the 'wallet' in development on > > > > > > > > > > > > > Odoo side but this is quite different as > > > > > > > > > > > > > based on accounting entries). > > > > > > > > > > > > > > > > > > > > > > > > > > If we can have a little feedback from some of > > > > > > > > > > > > > you on our future baby name. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > > > __________________________________________ > > > > > > > > > > > > > Denis Roussel > > > > > > > > > > > > > Software Engineer > > > > > > > > > > > > > Acsone SA, Succursale de Liège (Val Benoît) > > > > > > > > > > > > > Tel : +32 2 888 31 49 > > > > > > > > > > > > > Fax : +32 2 888 31 59 > > > > > > > > > > > > > Gsm : +32 472 22 00 57 > > > > > > > > > > > > > Acsone sa/nv > > > > > > > > > > > > > Boulevard de la Woluwe 56 Woluwedal | B-1200 > > > > > > > > > > > > > Brussels | Belgium > > > > > > > > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | > > > > > > > > > > > > > Belgium > > > > > > > > > > > > > Zone Industrielle 22 | L-8287 Kehlen | > > > > > > > > > > > > > Luxembourg > > > > > > > > > > > > > www.acsone.eu > > > > > > > > > > > > > > > > > > > > > > > > > > _____________________________________________ > > > > > > > > > > > > > __ > > > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > > __________________________________________ > > > > > > > > > > > Denis Roussel > > > > > > > > > > > Software Engineer > > > > > > > > > > > Acsone SA, Succursale de Liège (Val Benoît) > > > > > > > > > > > Tel : +32 2 888 31 49 > > > > > > > > > > > Fax : +32 2 888 31 59 > > > > > > > > > > > Gsm : +32 472 22 00 57 > > > > > > > > > > > Acsone sa/nv > > > > > > > > > > > Boulevard de la Woluwe 56 Woluwedal | B-1200 > > > > > > > > > > > Brussels | Belgium > > > > > > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | > > > > > > > > > > > Belgium > > > > > > > > > > > Zone Industrielle 22 | L-8287 Kehlen | > > > > > > > > > > > Luxembourg > > > > > > > > > > > www.acsone.eu > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > > > > > > 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 > > > > > > > > > > > > > > > > > > > > > -- > > > > > > > __________________________________________ > > > > > > > Denis Roussel > > > > > > > Software Engineer > > > > > > > Acsone SA, Succursale de Liège (Val Benoît) > > > > > > > Tel : +32 2 888 31 49 > > > > > > > Fax : +32 2 888 31 59 > > > > > > > Gsm : +32 472 22 00 57 > > > > > > > Acsone sa/nv > > > > > > > Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels > > > > > > > | Belgium > > > > > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium > > > > > > > Zone Industrielle 22 | L-8287 Kehlen | Luxembourg > > > > > > > www.acsone.eu > > > > > > > > > > > > > > _______________________________________________ > > > > > > > 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 > > > > > > > > > > > > -- > > > > Raphaël Reverdy > > > > Mobile +33 6 38 02 03 93 > > > > Fixe +33 4 82 53 84 60 > > > > _______________________________________________ > > > > Mailing-List: > > > > https://odoo-community.org/groups/contributors-15 > > > > Post to: mailto:contributors@odoo-community.org > > > > Unsubscribe: https://odoo-community.org/groups?unsubscribe > > > > > > > > > -- > > > __________________________________________ > > > Denis Roussel > > > Software Engineer > > > Acsone SA, Succursale de Liège (Val Benoît) > > > Tel : +32 2 888 31 49 > > > Fax : +32 2 888 31 59 > > > Gsm : +32 472 22 00 57 > > > > > > Acsone sa/nv > > > Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | Belgium > > > Quai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium > > > Zone Industrielle 22 | L-8287 Kehlen | Luxembourg > > > www.acsone.eu > > > > > > >
by Carmen Bianca Bakker - 11:06 - 29 Apr 2022 -
Re: Account financial reserve naming
Hello All,I am looking for an account wallet module something like this https://apps.odoo.com/apps/modules/13.0/odoo_website_wallet/.Using account_wallet by acsone can we achieve something which a paid module provides.Can you please suggest something.On Mon, May 17, 2021 at 1:47 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:On Mon, May 17, 2021 at 10:11 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:That's not exactly the same purpose (we use both in our project).I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:Hi,We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.Ok for account-wallet , may be move sale_promotion_rule there?Regards,Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :+1 account-wallet
Il 12/05/21 17:11, Bruno Joliveau ha scritto:
+1 for account-wallet
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada
Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
I'm requesting the creation of a new repository named account-wallet.
I hope this will help to fulfill people request. I will add PR's for 14 soon.
I think we can add it to accounting-maintainers PSC.
Thanks all for the little brainstorming.
On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Yes.
I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).
Maybe account-wallet (for repo)?
Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
wallet is an interesting name too.
I guess it's best to create a new repo, since this is a suite of modules covering several areas ?
-sbi
On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:
May be intresting for other countries, if I understand the request.
The financial reserve is a sort of payment down but not specific for any order.
In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.
Il 11/05/21 13:37, Roussel, Denis ha scritto:
I like it.
One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).
Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?
On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi,
Maybe a good name would be account_partner_fund ?
In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):
- funds (cagnottes) are created
- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id
- funds can be credited with balance sheet movements (bank to fund, no VAT impact)- funds can be used as payment means
- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due
Best regards,
--
On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi all,
We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.
We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.
These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).
If we can have a little feedback from some of you on our future baby name.
Regards,
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Silverstar - 11:21 - 6 Apr 2022 -
Re: Account financial reserve naming
On Mon, May 17, 2021 at 10:11 AM Roussel, Denis <denis.roussel@acsone.eu> wrote:That's not exactly the same purpose (we use both in our project).I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:Hi,We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.Ok for account-wallet , may be move sale_promotion_rule there?Regards,Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :+1 account-wallet
Il 12/05/21 17:11, Bruno Joliveau ha scritto:
+1 for account-wallet
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada
Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
I'm requesting the creation of a new repository named account-wallet.
I hope this will help to fulfill people request. I will add PR's for 14 soon.
I think we can add it to accounting-maintainers PSC.
Thanks all for the little brainstorming.
On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Yes.
I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).
Maybe account-wallet (for repo)?
Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
wallet is an interesting name too.
I guess it's best to create a new repo, since this is a suite of modules covering several areas ?
-sbi
On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:
May be intresting for other countries, if I understand the request.
The financial reserve is a sort of payment down but not specific for any order.
In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.
Il 11/05/21 13:37, Roussel, Denis ha scritto:
I like it.
One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).
Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?
On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi,
Maybe a good name would be account_partner_fund ?
In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):
- funds (cagnottes) are created
- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id
- funds can be credited with balance sheet movements (bank to fund, no VAT impact)- funds can be used as payment means
- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due
Best regards,
--
On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi all,
We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.
We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.
These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).
If we can have a little feedback from some of you on our future baby name.
Regards,
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 10:16 - 17 May 2021 -
Re: Account financial reserve naming
That's not exactly the same purpose (we use both in our project).I think for v14, we can base our thinking on the new voucher module in that flow (I will do soon a PR with a wallet-voucher or sth similar).A migration PR for sale_promotion_rule is currently draft there. IMHO, we need to split the coupon flow accordingly too.On Mon, May 17, 2021 at 10:07 AM Raphaël Reverdy <raphael.reverdy@akretion.com> wrote:Hi,We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.Ok for account-wallet , may be move sale_promotion_rule there?Regards,Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :+1 account-wallet
Il 12/05/21 17:11, Bruno Joliveau ha scritto:
+1 for account-wallet
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada
Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
I'm requesting the creation of a new repository named account-wallet.
I hope this will help to fulfill people request. I will add PR's for 14 soon.
I think we can add it to accounting-maintainers PSC.
Thanks all for the little brainstorming.
On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Yes.
I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).
Maybe account-wallet (for repo)?
Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
wallet is an interesting name too.
I guess it's best to create a new repo, since this is a suite of modules covering several areas ?
-sbi
On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:
May be intresting for other countries, if I understand the request.
The financial reserve is a sort of payment down but not specific for any order.
In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.
Il 11/05/21 13:37, Roussel, Denis ha scritto:
I like it.
One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).
Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?
On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi,
Maybe a good name would be account_partner_fund ?
In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):
- funds (cagnottes) are created
- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id
- funds can be credited with balance sheet movements (bank to fund, no VAT impact)- funds can be used as payment means
- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due
Best regards,
--
On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi all,
We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.
We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.
These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).
If we can have a little feedback from some of you on our future baby name.
Regards,
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
--__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg
by Denis Roussel - 10:16 - 17 May 2021 -
Re: Account financial reserve naming
Hi,We addressed a similar need with (oca/sale_workflow) sale_promotion_rule.The "deposit" is simply a voucher. It can be splitted (partial use in a SO), increased, and expiration can be set.Ok for account-wallet , may be move sale_promotion_rule there?Regards,Le mer. 12 mai 2021 à 17:27, Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> a écrit :+1 account-wallet
Il 12/05/21 17:11, Bruno Joliveau ha scritto:
+1 for account-wallet
Bruno Joliveau - PrésidentNUMIGI SOLUTIONS INC.
(514) 317-7944
Longueuil, Québec, Canada
Le mer. 12 mai 2021 à 11:06, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,
I'm requesting the creation of a new repository named account-wallet.
I hope this will help to fulfill people request. I will add PR's for 14 soon.
I think we can add it to accounting-maintainers PSC.
Thanks all for the little brainstorming.
On Tue, May 11, 2021 at 2:45 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Yes.
I think that will not conflict with future Odoo sale gift card (but they change their mind meantime).
Maybe account-wallet (for repo)?
Le mar. 11 mai 2021 à 14:31, Stéphane Bidoul <stephane.bidoul@acsone.eu> a écrit :
wallet is an interesting name too.
I guess it's best to create a new repo, since this is a suite of modules covering several areas ?
-sbi
On Tue, May 11, 2021 at 2:16 PM Antonio M. Vigliotti (gmail) <antoniomaria.vigliotti@gmail.com> wrote:
May be intresting for other countries, if I understand the request.
The financial reserve is a sort of payment down but not specific for any order.
In Italy is called "anticipo" (like payment down but it is not the same meaning) or portafoglio (Italian term for "wallet"). The account should be a <credit account type>.
We have to develop a module with this feature, can we share the thinks ena eventually the code, if you agred.
Il 11/05/21 13:37, Roussel, Denis ha scritto:
I like it.
One thing more is the fact that that fund can be partner agnostic. As it can represent a 'gift voucher' which has a certain balance corresponding to the voucher value (if not used yet).
Apart of that consideration, is it a good idea to create a repo for those modules or to go in an existing one ?
On Tue, May 11, 2021 at 11:01 AM Stéphane Bidoul <stephane.bidoul@acsone.eu> wrote:
Hi,
Maybe a good name would be account_partner_fund ?
In a nutshell, we have the following concepts in these modules (as I understand it after a quick reminder from Cedric, errors and imprecisions are mine, but the general idea should be this):
- funds (cagnottes) are created
- a balance sheet account is used to track the funds, with all journal items in this account having a m2o to the corresponding fund + partner_id
- funds can be credited with balance sheet movements (bank to fund, no VAT impact)- funds can be used as payment means
- when funds expire, there is a debit fund / credit revenue, and at that moment some VAT is due
Best regards,
--
On Mon, May 10, 2021 at 6:37 PM Roussel, Denis <denis.roussel@acsone.eu> wrote:
Hi all,
We want to put some modules we did to OCA, but before we want to validate naming with some native english speakers as some translations are ambiguous.
We want to modelize a financial reserve (we named it in French 'cagnotte' - that is translated at first sight jackpot or pot(the ambiguous one :-) ) through account moves that feed a waiting account.
These entries should allow to pay invoices later (we know the 'wallet' in development on Odoo side but this is quite different as based on accounting entries).
If we can have a little feedback from some of you on our future baby name.
Regards,
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--
__________________________________________
Denis Roussel
Software Engineer
Acsone SA, Succursale de Liège (Val Benoît)
Tel : +32 2 888 31 49
Fax : +32 2 888 31 59
Gsm : +32 472 22 00 57Acsone sa/nv
Boulevard de la Woluwe 56 Woluwedal | B-1200 Brussels | BelgiumQuai Banning, 6 (Val Benoît) | B-4000 Liège | Belgium
Zone Industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60
by Raphaël Reverdy - 10:06 - 17 May 2021
-
-
Sale Order -> Payment -> Invoice
Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal 



by Daniel Reis - 10:06 - 6 May 2021-
Re: Sale Order -> Payment -> Invoice
Hi Daniel,What feature are you missing exactly?The workflow that you're mentioning can be done by using a Standard Odoo Community version. (V13 and V14 at least).1- Sell by ordered quantities (not delivered).2- Generate the invoice automatically when the online payment is confirmed. --> Here you'll have to manage the payments by credit card, for example, so the payments can be validated in "real-time". This doesn't work with bank transfer as in this case, user has to confirm the payment/quotation manually.3- As I said previously, once the payment has been validated, the quotation is validated as well and a new shipping i pending to be transfered.4- You can also set an automatic confirmation by email, once the Delivery orders are done.As other contributors mentioned, sale_automatic_workflow might be helpful to improve such sales workflows.El lun, 10 may 2021 a las 17:52, Juan José Scarafía (ADHOC) (<scarafia.juanjose@gmail.com>) escribió:We've extended sale order type for similar needs (Bad documented on the modules).El vie, 7 de may. de 2021 a la(s) 04:57, Raphaël Reverdy (raphael.reverdy@akretion.com) escribió:Le ven. 7 mai 2021 à 08:22, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :This one forces the invoice to be paid in advance https://github.com/OCA/sale-workflow/tree/14.0/sale_stock_picking_blocking but there must be an invoice so I guess it does not fit that use case.RegardsOn Thu, 6 May 2021 at 22:07, Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal
_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
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
--Harald Panten López
CEO
Sygel Technology S.L

+34 637 88 42 41 
harald.panten@sygel.es 
https://www.sygel.es 
C/ Àlaba 61, 5ª planta, 08005, Barcelona
by Harald Panten Lopez - 07:00 - 10 May 2021 -
Re: Sale Order -> Payment -> Invoice
We've extended sale order type for similar needs (Bad documented on the modules).El vie, 7 de may. de 2021 a la(s) 04:57, Raphaël Reverdy (raphael.reverdy@akretion.com) escribió:Le ven. 7 mai 2021 à 08:22, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :This one forces the invoice to be paid in advance https://github.com/OCA/sale-workflow/tree/14.0/sale_stock_picking_blocking but there must be an invoice so I guess it does not fit that use case.RegardsOn Thu, 6 May 2021 at 22:07, Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal
_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60_______________________________________________
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 - 05:51 - 10 May 2021 -
Re: Sale Order -> Payment -> Invoice
Le ven. 7 mai 2021 à 08:22, Aarón Henríquez Quintana <ahenriquez@forgeflow.com> a écrit :This one forces the invoice to be paid in advance https://github.com/OCA/sale-workflow/tree/14.0/sale_stock_picking_blocking but there must be an invoice so I guess it does not fit that use case.RegardsOn Thu, 6 May 2021 at 22:07, Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal
_______________________________________________
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
--Raphaël ReverdyMobile +33 6 38 02 03 93Fixe +33 4 82 53 84 60
by Raphaël Reverdy - 09:56 - 7 May 2021 -
Re: Sale Order -> Payment -> Invoice
This one forces the invoice to be paid in advance https://github.com/OCA/sale-workflow/tree/14.0/sale_stock_picking_blocking but there must be an invoice so I guess it does not fit that use case.RegardsOn Thu, 6 May 2021 at 22:07, Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal 



_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Aarón Henríquez - 08:21 - 7 May 2021 -
Re: Sale Order -> Payment -> Invoice
set the products for invoice on "ordered qty" instead of "delivered qty"then, you can have an invoice before the delivery is done.regards--On Fri, 7 May 2021 at 4:07 AM, Daniel Reis <dreis@opensourceintegrators.com> wrote:Hello,
I'm looking at implementing a typical eCommerce-like B2C workflow, where Orders are paid before the picking starts and an invoice is generated.
AFAIK Odoo does not support this flow out of the box.
I also searched the OCA modules for help, and couldn't find any.
Did I miss anything on my search?
Thank you
--
Daniel Reis
Managing Director
M: +351 919991307
E: DReis@OpenSourceIntegrators.comAv Doutor Desidério Cambournac 12 • 2710-553 Sintra, Portugal 



_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
Dominique KON-SUN-TACK [Project Manager]Odoo Gold Partner, best Odoo Partner 2014 for APACMobile: + 65 8502 2399Skype: dominique_elicoWebsite: www.elico-corp.com
by dominique.k - 01:16 - 7 May 2021
-
-
OCA RFQ: Communication Strategy Expert - closes 12th May
Hello OCA Contributors
Just a reminder that our latest OCA RFQ closes on the 12th May.
We are looking for a Communication Strategy Expert to help define our Communication Strategy for the next 3 years.
To find out about the work schedule and deliverables please see here: https://drive.google.com/file/d/19EL646MjjpI4lN47v4P18tHMk2q_1ktR/view
If you have any questions please email: rfq@odoo-community.org
Warmest regards,Rebecca--Rebecca GellatlyGeneral SecretaryOdoo Community Association
by Rebecca Gellatly - 02:26 - 5 May 2021