Contributors

Weblate contact

Hi,
I tried to contact weblate support in https://translation.odoo-community.org/contact but after I sent the email, it said "Could not send message to administrator.".
From what I understand of the platform, maybe there is some configuration missing in OCA's weblate installation? Can someone have a look?

I have looked in https://odoo-community.org/groups but haven't found any mailing list dedicated to platform or translations issues, let me know if I should write somewhere else.

Thanks,
Simone Rubino

by Simone Rubino - 10:36 - 20 Jan 2022
1 replies 1 replies
Re: Weblate contact

Hi Simone,

I'm not sure why the weblate contact form doesn't work.

In the meantime send your question to transbot@odoo-community.org. That is where we (well, I) manage the registration requests and if there weblate-related support questions, i'll see them there too when I look at new users requests.

Best,

-sbi

On Thu, Jan 20, 2022 at 10:36 AM Simone Rubino <simone.rubino@agilebg.com> wrote:
Hi,
I tried to contact weblate support in https://translation.odoo-community.org/contact but after I sent the email, it said "Could not send message to administrator.".
From what I understand of the platform, maybe there is some configuration missing in OCA's weblate installation? Can someone have a look?

I have looked in https://odoo-community.org/groups but haven't found any mailing list dedicated to platform or translations issues, let me know if I should write somewhere else.

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

by Stéphane Bidoul - 01:46 - 22 Jan 2022

Proposing new PSC's

Dear Odoo Community contributors,

I would like to propose new PSC members from ForgeFlow and Creu Blanca.

The names I'm proposing are all very active contributors. You can check their contributions in the table below.

PSC Team	Propose	Github handles
Banking	Aaron Henriquez, Enric Tobella, Jordi Ballester	aaronhforgeflow, etobella, jordibforgeflow
HR	Alba Riera	albariera
Reporting engine	Hector Villarreal, Enric Tobella	hviorforgeflow,etobella
Search	Hector Villarreal, Enric Tobella	hviorforgeflow,etobella
Social	Enric Tobella	etobella
Web	Enric Tobella	etobella

Regards,

Jordi Ballester Alomar

CEO & Founder

Spain: (+34) 629 53 07 07 | USA: (+1) 646 980 46 59 | Denmark: (+45) 78 78 21 89

Email: jordi.ballester@forgeflow.com | Twitter: /jordibforgeflow | Linkedin: /jordiballesteralomar

The content of this email is confidential and intended for the recipient specified in message only. It is strictly forbidden to share any part of this message with any third party, without a written consent of the sender. If you received this message by mistake, please reply to this message and follow with its deletion, so that we can ensure such a mistake does not occur in the future.

by Jordi Ballester Alomar - 10:30 - 20 Jan 2022

9 replies 9 replies

Vendor Pricelist records for Product Variants - what am I missing?

Hello,

as New Year came it fell upon me to update lots of pricelists. As we use Product Variants (product.product) quite a bit I am invalidating (i.e. setting date_end) on existing Supplier Pricelist (product.supplierinfo) records and creating new ones. Using base_import_match to match the correct product variant by internal reference (default_code) and trying to import related product.supplierinfo record. Originally I wanted to create small helper that would invalidate all existing records (no end date, same variant, same template, same supplier, same company) when creating new one. Just to save time updating existing records and creating new ones. However it never works (more on that below).

Now there are 2 fields defined for product.template and none for product.product that would serve what I am wanting to do. Here's what's defined for product.template (in 13.0, 14.0 and 15.0 as well):

seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors', depends_context=('company',), help="Define vendor pricelists.")
variant_seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id')

In Purchase there is this for product.template view:

Just for clarity, here's part from product.supplierinfo:

product_id = fields.Many2one('product.product', 'Product Variant', check_company=True, help="If not set, the vendor price will apply to all variants of this product.")

product_tmpl_id = fields.Many2one('product.template', 'Product Template', check_company=True, index=True, ondelete='cascade')

Am I missing something here or are these the same besides the context and some witchcraft in views? While trying to import the product.product records when creating product.supplierinfo records there's always product_tmpl_id but never product_id. Shouldn't the definition of variant_s be like this and defined in product.product model:

variant_seller_ids = fields.One2many('product.supplierinfo', 'product_id')

What is the purpose of current design? Would anyone be willing to shed some light here? Hope such post fits in the mailing list.

Thank you very much.Best regards

Radovan Skolnik

by Radovan Skolnik - 08:31 - 20 Jan 2022

3 replies 3 replies

Re: Vendor Pricelist records for Product Variants - what am I missing?

Graeme,

I perfectly undertsand the design of product.supplierinfo and have no problem dealing with date_end (I created a small module that upon creation of new record end the existing ones with the same combination of attributes)

What puzzles me is the design from the side of product.template and/or product.product side. You see there are basically 2 identical one2many attributes (so actually no database tables / columns are created) on product.template that reference product.supplierinfo: seller_ids and variant_seller_ids:

    seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors', help="Define vendor pricelists.")

    variant_seller_ids = fields.One2many('product.supplierinfo', 'product_tmpl_id')

As the name would suggest the latter should somehow provide info on sellers of variants. But it does not in any way. The variant_seller_ids is never used in code. It is only referenced in one view where it is displayed instead of seller_ids in purchase/views/product_views.xml when there are more than 1 variants of that product:

    <field name="seller_ids" context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id), 'product_template_invisible_variant': True}" nolabel="1" attrs="{'invisible': [('product_variant_count','>',1)]}"/>

    <field name="variant_seller_ids" context="{'default_product_tmpl_id': context.get('product_tmpl_id', active_id)}" nolabel="1" attrs="{'invisible': [('product_variant_count','<=',1)]}"/>

But it still shows the same thing as seller_ids would! According to a comment on PR that introduced this back in June 2017 in version 11.0 from sswapnesh (who I believe is best Odoo contributor for years 2019, 2020 and 202) this does not make sense as well. Just see it there - tho comment is from August 2020. I believe the variant_seller_ids should have been defined in product.product and the name of its inverse filed should have been product_id. Or something similar.

I stumbled upon this situation when attempting to import-update product variant and also create new corresponding record for product.supplierinfo. It seems that's impossible. Why? Because there is no one2many relation between product.product and product.supplierinfo. I do not believe this was intended.

Am I making sense? Do those 2 attributes together make sense in context of product.supplierinfo? Not to me.

Best regards

    Radovan

On štvrtok 20. januára 2022 20:56:57 CET Graeme Gellatly wrote:

> In general when you do lots of seller pricelist you enable Vendor Pricelists

> and import from there. The end date problem is still a problem. You can

> kind of get around it with sequences, start dates on new records and then

> find dups after. It would be good to have a specific module to do

> everything. But supplierinfo is straightforward. Those are the fields you

> care about. Not product template relational references. Do it via vendor

> pricelists and much easier. product_id = fields . Many2one (

> 'product.product' , 'Product Variant' , check_company = True , help = "If

> not set, the vendor price will apply to all variants of this product." )

> product_tmpl_id = fields . Many2one ( 'product.template' , 'Product

> Template' , check_company = True ,       index = True , ondelete =

> 'cascade' ) On Thu, Jan 20, 2022 at 10:27 PM Radovan Skolnik <

> radovan@skolnik.info [1] > wrote: What's more the field variant_seller_ids

> is never used anywhere besides that view. It was introduced into 11.0 by

> this PR: https://github.com/odoo/odoo/pull/17789 [2]

>

> R.S.

>

> On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:

> > Hello,

> >

> > as New Year came it fell upon me to update lots of pricelists. As we use

> > Product Variants (product.product) quite a bit I am invalidating (i.e.

> > setting date_end) on existing Supplier Pricelist (product.supplierinfo)

> > records and creating new ones. Using base_import_match to match the

> > correct

> > product variant by internal reference (default_code) and trying to import

> > related product.supplierinfo record. Originally I wanted to create small

> > helper that would invalidate all existing records (no end date, same

> > variant, same template, same supplier, same company) when creating new

> > one.

> > Just to save time updating existing records and creating new ones. However

> > it never works (more on that below).

> >

> > Now there are 2 fields defined for product.template and none for

> > product.product that would serve what I am wanting to do. Here's what's

> > defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids

> > =

> > fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',

> > depends_context=('company',), help="Define vendor pricelists.")

> > variant_seller_ids = fields.One2many('product.supplierinfo',

> > 'product_tmpl_id')

> >

> > In Purchase there is this for product.template view:

> > <field name="seller_ids"

> > context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_i

> > d

> > ), 'product_template_invisible_variant': True}" nolabel="1"

> > attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field

> > name="variant_seller_ids" context="{'default_product_tmpl_id':

> > context.get('product_tmpl_id', active_id)}" nolabel="1"

> > attrs="{'invisible': [('product_variant_count','<=',1)]}"/>

> >

> > Just for clarity, here's part from product.supplierinfo:

> > product_id = fields.Many2one('product.product', 'Product Variant',

> > check_company=True, help="If not set, the vendor price will apply to all

> > variants of this product.") product_tmpl_id =

> > fields.Many2one('product.template', 'Product Template',

> > check_company=True,

> > index=True, ondelete='cascade')

> >

> > Am I missing something here or are these the same besides the context and

> > some witchcraft in views? While trying to import the product.product

> > records when creating product.supplierinfo records there's always

> > product_tmpl_id but never product_id. Shouldn't the definition of

> > variant_s

> > be like this and defined in product.product model: variant_seller_ids =

> > fields.One2many('product.supplierinfo', ' *product_id* ')

> >

> > What is the purpose of current design? Would anyone be willing to shed

> > some

> > light here? Hope such post fits in the mailing list.

> >

> > Thank you very much.Best regards

> >

> > Radovan Skolnik

> >

> > _______________________________________________

> > Mailing-List: https://odoo-community.org/groups/contributors-15 [3] [1]

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

> > Unsubscribe: https://odoo-community.org/groups?unsubscribe [5] [2]

> >

> >

> >

> > [1] https://odoo-community.org/groups/contributors-15 [6]

> > [2] https://odoo-community.org/groups?unsubscribe [7]

>

> _______________________________________________

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

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

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

>

>

> _______________________________________________

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

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

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

>

>

>

> [1] mailto:radovan@skolnik.info

> [2] https://github.com/odoo/odoo/pull/17789

> [3] https://odoo-community.org/groups/contributors-15

> [4] mailto:contributors@odoo-community.org

> [5] https://odoo-community.org/groups?unsubscribe

> [6] https://odoo-community.org/groups/contributors-15

> [7] https://odoo-community.org/groups?unsubscribe

> [8] https://odoo-community.org/groups/contributors-15

> [9] mailto:contributors@odoo-community.org

> [10] https://odoo-community.org/groups?unsubscribe

> [11] https://odoo-community.org/groups/contributors-15

> [12] https://odoo-community.org/groups?unsubscribe

by Radovan Skolnik - 09:36 - 20 Jan 2022

Re: Vendor Pricelist records for Product Variants - what am I missing?

In general when you do lots of seller pricelist you enable Vendor Pricelists and import from there. The end date problem is still a problem. You can kind of get around it with sequences, start dates on new records and then find dups after. It would be good to have a specific module to do everything.

But supplierinfo is straightforward. Those are the fields you care about. Not product template relational references. Do it via vendor pricelists and much easier.

product_id = fields.Many2one(
	'product.product', 'Product Variant', check_company=True,
	help="If not set, the vendor price will apply to all variants of this product.")
	product_tmpl_id = fields.Many2one(
	'product.template', 'Product Template', check_company=True,
	index=True, ondelete='cascade')

On Thu, Jan 20, 2022 at 10:27 PM Radovan Skolnik <radovan@skolnik.info> wrote:

What's more the field variant_seller_ids is never used anywhere besides that view.

It was introduced into 11.0 by this PR: https://github.com/odoo/odoo/pull/17789

R.S.

On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:

> Hello,

>

> as New Year came it fell upon me to update lots of pricelists. As we use

> Product Variants (product.product) quite a bit I am invalidating (i.e.

> setting date_end) on existing Supplier Pricelist (product.supplierinfo)

> records and creating new ones. Using base_import_match to match the correct

> product variant by internal reference (default_code) and trying to import

> related product.supplierinfo record. Originally I wanted to create small

> helper that would invalidate all existing records (no end date, same

> variant, same template, same supplier, same company) when creating new one.

> Just to save time updating existing records and creating new ones. However

> it never works (more on that below).

>

> Now there are 2 fields defined for product.template and none for

> product.product that would serve what I am wanting to do. Here's what's

> defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids =

> fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',

> depends_context=('company',), help="Define vendor pricelists.")

> variant_seller_ids = fields.One2many('product.supplierinfo',

> 'product_tmpl_id')

>

> In Purchase there is this for product.template view:

> <field name="seller_ids"

> context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id

> ), 'product_template_invisible_variant': True}" nolabel="1"

> attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field

> name="variant_seller_ids" context="{'default_product_tmpl_id':

> context.get('product_tmpl_id', active_id)}" nolabel="1"

> attrs="{'invisible': [('product_variant_count','<=',1)]}"/>

>

> Just for clarity, here's part from product.supplierinfo:

> product_id = fields.Many2one('product.product', 'Product Variant',

> check_company=True, help="If not set, the vendor price will apply to all

> variants of this product.") product_tmpl_id =

> fields.Many2one('product.template', 'Product Template', check_company=True,

> index=True, ondelete='cascade')

>

> Am I missing something here or are these the same besides the context and

> some witchcraft in views? While trying to import the product.product

> records when creating product.supplierinfo records there's always

> product_tmpl_id but never product_id. Shouldn't the definition of variant_s

> be like this and defined in product.product model: variant_seller_ids =

> fields.One2many('product.supplierinfo', ' *product_id* ')

>

> What is the purpose of current design? Would anyone be willing to shed some

> light here? Hope such post fits in the mailing list.

>

> Thank you very much.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 Graeme Gellatly - 08:55 - 20 Jan 2022

Re: Vendor Pricelist records for Product Variants - what am I missing?

What's more the field variant_seller_ids is never used anywhere besides that view.

It was introduced into 11.0 by this PR: https://github.com/odoo/odoo/pull/17789

R.S.

On štvrtok 20. januára 2022 8:32:15 CET Radovan Skolnik wrote:

> Hello,

>

> as New Year came it fell upon me to update lots of pricelists. As we use

> Product Variants (product.product) quite a bit I am invalidating (i.e.

> setting date_end) on existing Supplier Pricelist (product.supplierinfo)

> records and creating new ones. Using base_import_match to match the correct

> product variant by internal reference (default_code) and trying to import

> related product.supplierinfo record. Originally I wanted to create small

> helper that would invalidate all existing records (no end date, same

> variant, same template, same supplier, same company) when creating new one.

> Just to save time updating existing records and creating new ones. However

> it never works (more on that below).

>

> Now there are 2 fields defined for product.template and none for

> product.product that would serve what I am wanting to do. Here's what's

> defined for product.template (in 13.0, 14.0 and 15.0 as well): seller_ids =

> fields.One2many('product.supplierinfo', 'product_tmpl_id', 'Vendors',

> depends_context=('company',), help="Define vendor pricelists.")

> variant_seller_ids = fields.One2many('product.supplierinfo',

> 'product_tmpl_id')

>

> In Purchase there is this for product.template view:

> <field name="seller_ids"

> context="{'default_product_tmpl_id':context.get('product_tmpl_id',active_id

> ), 'product_template_invisible_variant': True}" nolabel="1"

> attrs="{'invisible': [('product_variant_count','>',1)]}"/> <field

> name="variant_seller_ids" context="{'default_product_tmpl_id':

> context.get('product_tmpl_id', active_id)}" nolabel="1"

> attrs="{'invisible': [('product_variant_count','<=',1)]}"/>

>

> Just for clarity, here's part from product.supplierinfo:

> product_id = fields.Many2one('product.product', 'Product Variant',

> check_company=True, help="If not set, the vendor price will apply to all

> variants of this product.") product_tmpl_id =

> fields.Many2one('product.template', 'Product Template', check_company=True,

> index=True, ondelete='cascade')

>

> Am I missing something here or are these the same besides the context and

> some witchcraft in views? While trying to import the product.product

> records when creating product.supplierinfo records there's always

> product_tmpl_id but never product_id. Shouldn't the definition of variant_s

> be like this and defined in product.product model: variant_seller_ids =

> fields.One2many('product.supplierinfo', ' *product_id* ')

>

> What is the purpose of current design? Would anyone be willing to shed some

> light here? Hope such post fits in the mailing list.

>

> Thank you very much.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 - 10:26 - 20 Jan 2022

Cash flow statement report

Dear Contributors,

I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?

This is report in enterprise version

Best Regards,
Tharathip C.

by tharathipc - 03:51 - 20 Jan 2022

1 attachments 1 attachments

Selection_916.png
5 replies 5 replies
Re: Cash flow statement report

Great! I will try. Thank you kindly :)

ในวันที่ พฤ. 20 ม.ค. 2022 เวลา 15:22 Roussel, Denis <denis.roussel@acsone.eu> เขียนว่า:
Hi,

If you follow the links, you find this: https://github.com/OCA/account-financial-reporting/tree/14.0/mis_builder_cash_flow

On Thu, Jan 20, 2022 at 9:12 AM Virginie Dewulf <virginie@coopiteasy.be> wrote:
Hello,
I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.
I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154
Maybe someone else here knows where it is!
Good luck,
PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie
0477/64.17.20

-----Original Message-----
From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Cash flow statement report
Date: Thu, 20 Jan 2022 02:52:45 -0000

Dear Contributors,

I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?

This is report in enterprise version

Best Regards,
Tharathip C.

_______________________________________________
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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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 tharathipc - 04:31 - 24 Jan 2022

Re: Cash flow statement report

Dear Virginie,

In my experience, the best way to find modules is the OCA App Store, mainly for functional consultants who don't have GitHub profile.

So the module is

https://github.com/OCA/account-financial-reporting/tree/14.0/mis_builder_cash_flow

And in the screenshot you can see how I found it easyly

My best
Rafael Blasco
@Moduon

El jue., 20 ene. 2022 9:12, Virginie Dewulf <virginie@coopiteasy.be> escribió:
Hello,
I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.
I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154
Maybe someone else here knows where it is!
Good luck,
PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie
0477/64.17.20

-----Original Message-----
From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Cash flow statement report
Date: Thu, 20 Jan 2022 02:52:45 -0000

Dear Contributors,

I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?

This is report in enterprise version

Best Regards,
Tharathip C.

_______________________________________________
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 Rafael Blasco (Moduon) - 09:25 - 20 Jan 2022

1 attachments 1 attachments

Screenshot_20220120-091930.png

Re: Cash flow statement report

Hi,

If you follow the links, you find this: https://github.com/OCA/account-financial-reporting/tree/14.0/mis_builder_cash_flow

On Thu, Jan 20, 2022 at 9:12 AM Virginie Dewulf <virginie@coopiteasy.be> wrote:
Hello,
I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.
I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154
Maybe someone else here knows where it is!
Good luck,
PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie
0477/64.17.20

-----Original Message-----
From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Cash flow statement report
Date: Thu, 20 Jan 2022 02:52:45 -0000

Dear Contributors,

I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?

This is report in enterprise version

Best Regards,
Tharathip C.

_______________________________________________
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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 09:21 - 20 Jan 2022

Re: Cash flow statement report

The OCA apps library is your friend :)

https://odoo-community.org/shop/product/mis-builder-cash-flow-5016#attr=15855

by Pedro M. Baeza - 09:21 - 20 Jan 2022

Re: Cash flow statement report

Hello,
I've heard about a module based on MIS Builder, something like mis_builder_cash_flow, but I can't find on the repo.
I only found this closed PR on v11: https://github.com/OCA/mis-builder/pull/154
Maybe someone else here knows where it is!
Good luck,
PS : the image you added to your email is not displayed (seems to be a feature not managed by our mailing lists). Please attach the image as an attachment next time!
--
Virginie
0477/64.17.20

-----Original Message-----
From: Tharathip Chaweewongphan <tharathipc@ecosoft.co.th>
Reply-To: Odoo Community Association (OCA) Contributors <contributors@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Cash flow statement report
Date: Thu, 20 Jan 2022 02:52:45 -0000

Dear Contributors,

I need to cash flow statement report on CE V.14 like a enterprise version. I try to find on odoo app or oca but still not found. Are there any modules about this ?

This is report in enterprise version

Best Regards,
Tharathip C.

_______________________________________________
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. - 09:10 - 20 Jan 2022

New repositories : cooperative and participative supermarket

Hi all,

At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :

cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.

We will need to

remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.

These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.

Based on the OCA repository policy, we would like to propose to create these 3 new repositories :

cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …

What do you think ? Is there room for these projects at the OCA ?

You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.

All inputs welcome,

Robin Keunen

Robin Keunen

Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

by Robin Keunen - 11:26 - 14 Jan 2022

12 replies 12 replies

Re: New repositories : cooperative and participative supermarket

Hi Robin,

I have created the 3 repositories and the Cooperative PSC.

I set you as PSC representative and added Remy and Houssine as members.
@Enrico, I could not find a user with your name nor Daniel Palomar in the OCA database. Could you register so I can add you as PSC members ?

@Robin, I'll let you initialize the branches you need with `copier copy git+https://github.com/oca/oca-addons-repo-template`. Please answer GitHub to the CI question so it uses GitHub actions.

Let me know if I forgot anything or if you need help setting it up.

Best regards,

-sbi

by Stéphane Bidoul - 07:48 - 27 Feb 2022

Re: New repositories : cooperative and participative supermarket

I would be glad to join.

I agree with Robin. Not sure that the PSC association is suitable as from what I see it covers mainly the membership aspect. While a cooperative verticalization will mainly cover the specifics for a commercial cooperative company as the share management for example.

Anyway there is also a membership aspect for cooperative but it is far different from the way it is conceived for association.

Le jeu. 10 févr. 2022 à 10:46, Enrico Stano <enrico.stano@coopdevs.org> a écrit :

+1 on Rémy and/or Houssine of course.

If needed, from Coopdevs we would be glad to participate (Daniel Palomar or myself). Thanks.

Not sure about the "Association" PSC, it also seems unrelated IMHO. But maybe PSC members from "Association" have a different opinion. Could we ask?

Bye,

Enrico

coopdevs.org

On 2/9/22 19:17, robin@coopiteasy.be wrote:
Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.

Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.

All the best,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40
On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91

/Daniel

On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?

I don't immediately see an existing PSC to cover this scope.

So shall we create one new PSC (named Ccooperative?) for the 3 repos ?

Who would be the PSC representative (Robin?). Who would be the first members ?

-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,

+1 and a big thank you!

Bye,

Enrico Stano

coopdevs.org

On 1/27/22 18:57, Roussel, Denis wrote:

Hi Robin,

+1 for the three repos.

On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:

Hi Denis,

Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)

- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.

- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.

- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards

* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:

Hi Denis,

Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:

Hi Robin,

That's great to hear this!

My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.

For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.

Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !

On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:

Hi all,

At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.

We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.

Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?

You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.

All inputs welcome,

Robin Keunen

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe

--

Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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
--  
Enrico Stano

coopdevs.org
_______________________________________________
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

_______________________________________________
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
--

DANIEL REIS
MANAGING DIRECTOR
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
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
-- 
Enrico Stano

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

by Houssine BAKKALI - 11:01 - 10 Feb 2022

Re: New repositories : cooperative and participative supermarket

+1 on Rémy and/or Houssine of course.

If needed, from Coopdevs we would be glad to participate (Daniel Palomar or myself). Thanks.

Not sure about the "Association" PSC, it also seems unrelated IMHO. But maybe PSC members from "Association" have a different opinion. Could we ask?

Bye,

Enrico

coopdevs.org

On 2/9/22 19:17, robin@coopiteasy.be wrote:

Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.

Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.

All the best,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40
On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:
Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91

/Daniel

On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?

I don't immediately see an existing PSC to cover this scope.

So shall we create one new PSC (named Ccooperative?) for the 3 repos ?

Who would be the PSC representative (Robin?). Who would be the first members ?

-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,

+1 and a big thank you!

Bye,

Enrico Stano

coopdevs.org

On 1/27/22 18:57, Roussel, Denis wrote:

Hi Robin,

+1 for the three repos.

On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:

Hi Denis,

Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)

- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.

- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.

- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards

* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:

Hi Denis,

Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:

Hi Robin,

That's great to hear this!

My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.

For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.

Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !

On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:

Hi all,

At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.

We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.

Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?

You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.

All inputs welcome,

Robin Keunen

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe

--

Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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
--  
Enrico Stano

coopdevs.org
_______________________________________________
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

_______________________________________________
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
--

DANIEL REIS
MANAGING DIRECTOR
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
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

-- 
Enrico Stano

coopdevs.org

by Enrico Stano - 10:45 - 10 Feb 2022

Re: New repositories : cooperative and participative supermarket

Rémy Taymans (remy@coopiteasy.be) should be in the PSC as well. Is there candidates at Coopdevs ? If Houssine Bakkali is still around and interested, he would be a good candidate as well.

Expanding “Association” could work if we need to have people outside of Coop IT Easy in the PSC. Otherwise, it seems unrelated.

All the best,

Robin Keunen

Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 9 Feb 2022, 18:42 +0100, Daniel Reis <dreis@opensourceintegrators.com>, wrote:

Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91

/Daniel

On 09/02/22 17:32, Stéphane Bidoul wrote:
Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?

I don't immediately see an existing PSC to cover this scope.

So shall we create one new PSC (named Ccooperative?) for the 3 repos ?

Who would be the PSC representative (Robin?). Who would be the first members ?

-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,

+1 and a big thank you!

Bye,

Enrico Stano

coopdevs.org

On 1/27/22 18:57, Roussel, Denis wrote:

Hi Robin,

+1 for the three repos.

On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:

Hi Denis,

Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)

- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.

- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.

- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards

* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:

Hi Denis,

Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.
The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:

Hi Robin,

That's great to hear this!

My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.

For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.

Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !

On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:

Hi all,

At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.

We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.

Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?

You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.

All inputs welcome,

Robin Keunen

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe

--

Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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
--  
Enrico Stano

coopdevs.org
_______________________________________________
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

_______________________________________________
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
--

DANIEL REIS
MANAGING DIRECTOR
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe

by Robin Keunen - 07:16 - 9 Feb 2022

Re: New repositories : cooperative and participative supermarket

Would it be simpler to reuse/expand scope of the existing "Association" PSC?
https://odoo-community.org/psc-teams/association-91

/Daniel

On 09/02/22 17:32, Stéphane Bidoul wrote:

Ok, so what do we do in terms of PSC, PSC Representative, and PSC Members ?

I don't immediately see an existing PSC to cover this scope.

So shall we create one new PSC (named Ccooperative?) for the 3 repos ?

Who would be the PSC representative (Robin?). Who would be the first members ?

-sbi
On Wed, Feb 9, 2022 at 10:47 AM Valentin Vinagre Urteaga <valentin.vinagre@sygel.es> wrote:
+1 :D
El mié, 9 feb 2022 a las 10:02, Enrico Stano (<enrico.stano@coopdevs.org>) escribió:
Hi,

+1 and a big thank you!

Bye,

Enrico Stano

coopdevs.org

On 1/27/22 18:57, Roussel, Denis wrote:

Hi Robin,

+1 for the three repos.

On Thu, Jan 27, 2022 at 6:22 PM <robin@coopiteasy.be> wrote:

Hi Denis,

Thank you for your answer, it looks like my last email did not go through. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)

- oca/cooperative would hold the modules allowing to
- Subscribe to a share, transfer a share or sell a share from the cooperative,
- Share subscription can be done online,
- Manage the cooperator registry of a cooperative,
- Generate legal reports for company and cooperators.

- oca/shift-planning would hold the modules allowing to
- Create a planning template of work shifts of the company
- Generate the shifts based on these templates,
- Allow partners to subscribe to regular tasks,
- Allow partners to subscribe to any task with available spot,
- Track the attendance to the shifts.

- oca/vertical-cooperative-supermarket* glues all these together to
- Track who can work in the cooperative
- Track who can shop in the cooperative
- welcome screens and member cards

* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy

robin@coopiteasy.be

+32 488 86 57 40

On 17 Jan 2022, 18:25 +0100, robin@coopiteasy.be, wrote:

Hi Denis,

Thank you for your answer. My suggestion to create an temporary or incubation repository comes from this oca_repository_policy.rst but I may have dug up a deprecated article. In this article, I also read about beta modules :

The incubation approach was introduced to lower the barrier to the entry of new contributors and ease collaboration. Code that is included in the OCA under the incubation process is intended to be actively improved until it reaches a Stable level, or can stands as a challenger to an existing Stable module providing a similar feature. Incubation code that was abandoned should be deleted.
Incubated modules are hosted in the same repositories as stable ones, but are labelled with a Alpha or Beta maturity level.

The idea was to mark the modules as beta while we remove all the references to customer names but it’s all stable in the current state.

As for refining the topics, I can try to rephrase :-)
• oca/cooperative would hold the modules allowing to
• Subscribe to a share, transfer a share or sell a share from the cooperative,
• Share subscription can be done online,
• Manage the cooperator registry of a cooperative,
• Generate legal reports for company and cooperators.
• oca/shift-planning would hold the modules allowing to
• Create a planning template of work shifts of the company
• Generate the shifts based on these templates,
• Allow partners to subscribe to regular tasks,
• Allow partners to subscribe to any task with available spot,
• Track the attendance to the shifts.
• oca/vertical-cooperative-supermarket* glues all these together to
• Track who can work in the cooperative
• Track who can shop in the cooperative
* once cleaned up from all sale, purchase, pos, ... customisations.

I hope it’s clearer that way,

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
On 14 Jan 2022, 18:32 +0100, Roussel, Denis <denis.roussel@acsone.eu>, wrote:

Hi Robin,

That's great to hear this!

My two cents on this. Maybe you should refine the topics the repositories you want to create will cover (it does not help saying they are in beta). Especially for the first one.

For the third, we usually don't create 'temporary' repositories. I suggest you to create issues/PR's directly on OCA specific repos for modules you want to move. It will be more efficient and avoiding creation of one that will be deleted actually.

Don't hesitate if you have more technical questions, but for sure you have a good OCA contact person near you !

On Fri, Jan 14, 2022 at 11:27 AM <robin@coopiteasy.be> wrote:

Hi all,

At Coop IT Easy, we’ve been working for 5 years with cooperative and participatory supermarkets (aka Food Coop, ex: BEES coop). We would like to bring most of that code under the OCA umbrella. The code is now divided into two repositories :
cooperative/vertical-cooperative modules deal with share subscriptions, cooperator registry, online registrations, etc. equivalent to oca/vertical-association ;
beescoop/obeesdoo contains modules to manage the work of the members (planning their shifts) and many customisations to sales, purchase, stock and point of sales.

We will need to
remove all references to Obeesdoo and Easy My Coop (debranding) ;
split modules by features ;
cover more code with unit tests.
These solutions have been used in production for several years now and is now used by 11 supermarkets and 25+ cooperatives (plus a few others by other integrators). Everything is in version 12 and we will soon migrate cooperative modules to version 14.

Based on the OCA repository policy, we would like to propose to create these 3 new repositories :
cooperative with all modules in beta-stage while we debrand them.
shift-planning (or shift-management ?) with all modules dealing with shifts in beta stage as well.
vertical-cooperative-supermarket as an incubation repository while we move all the features to oca/purchase-workflow, oca/pos, …
What do you think ? Is there room for these projects at the OCA ?

You can find more information on these Github Issues RFC Moving Obeesdoo to OCA #247 and RFC Moving Easy My Coop to OCA.

All inputs welcome,

Robin Keunen

Robin Keunen
Coop IT Easy
robin@coopiteasy.be
+32 488 86 57 40
_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post to: mailto:contributors@odoo-community.orgUnsubscribe: https://odoo-community.org/groups?unsubscribe

--

Denis RousselSoftware EngineerT : +32 2 888 31 49M : +32 472 22 00 57
Val Benoit, Quai Banning 6 | B-4000 Liège | BelgiumAtrium Building, Drève Richelle 167 | B-1410 Waterloo | BelgiumZone industrielle 22 | L-8287 Kehlen | Luxembourg_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15Post 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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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
-- 
Enrico Stano

coopdevs.org
_______________________________________________
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

_______________________________________________
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

DANIEL REIS
MANAGING DIRECTOR

M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34

by Daniel Reis - 06:41 - 9 Feb 2022

Happy New Year: 2022 priorities presented!
Hello Community,

New year, New board, New Straegy, New Working Groups (we need you!): everything is in this new blog post from the board:
https://odoo-community.org/blog/the-oca-blog-1/post/happy-new-year-to-our-oca-community-115

Don't hesitate to comment on the blog post or by responding to this mailing list if you want to notify all contributors.

Have a great day and year!
--
Virginie
0477/64.17.20
by Virginie Dewulf. - 09:15 - 13 Jan 2022
New repo proposal: repair

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.
* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.
* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--
Aaron Henríquez Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869

by Aarón Henríquez - 02:10 - 12 Jan 2022
15 replies 15 replies
Re: New repo proposal: repair

Thank you Lois!

On Wed, 19 Jan 2022 at 10:31, Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
Hi,

Branch 15.0 initialized: https://github.com/OCA/repair.

Thanks all!

On Wed, Jan 19, 2022 at 10:02 AM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:
Thank you Community! Thank you Simone!

I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.

Regards,

Aaron

On Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:
Hola,

there you go https://github.com/OCA/repair

I let you bootstrap it.

Happy hacking,
S.

On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.
* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.
* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--
Aaron Henríquez Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

_______________________________________________
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 Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

_______________________________________________
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 Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



by Aarón Henríquez - 10:45 - 19 Jan 2022

Re: New repo proposal: repair

Hi,

Branch 15.0 initialized: https://github.com/OCA/repair.

Thanks all!

On Wed, Jan 19, 2022 at 10:02 AM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:
Thank you Community! Thank you Simone!

I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.

Regards,

Aaron

On Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:
Hola,

there you go https://github.com/OCA/repair

I let you bootstrap it.

Happy hacking,
S.

On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.
* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.
* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--
Aaron Henríquez Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

_______________________________________________
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 Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

by Lois Rilo Antelo - 10:30 - 19 Jan 2022

Re: New repo proposal: repair

Thank you Community! Thank you Simone!

I tried to initialize the repo but I am not part of the @OCA/manufacturing-maintainers group so I will ask someone else to do that.

Regards,

Aaron

On Wed, 19 Jan 2022 at 09:02, Simone Orsi <simahawk@gmail.com> wrote:
Hola,

there you go https://github.com/OCA/repair

I let you bootstrap it.

Happy hacking,
S.

On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.
* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.
* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--
Aaron Henríquez Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

_______________________________________________
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 Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



by Aarón Henríquez - 10:01 - 19 Jan 2022

Re: New repo proposal: repair

Hola,

there you go https://github.com/OCA/repair

I let you bootstrap it.

Happy hacking,
S.

On Wed, Jan 12, 2022 at 2:12 PM Aarón Henríquez Quintana <ahenriquez@forgeflow.com> wrote:

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.
* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.
* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--
Aaron Henríquez Quintana
Technical Consultant
ahenriquez@forgeflow.com
Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 09:01 - 19 Jan 2022

Re: New repo proposal: repair

+1

De: "Antonio M. Vigliotti (gmail)" <antoniomaria.vigliotti@gmail.com>
Para: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
Enviadas: Terça-feira, 18 de janeiro de 2022 13:11:45
Assunto: Re: New repo proposal: repair

Full agree

+1

Antonio M. Vigliotti

Mobile (+39) 342.8740910

Il 12/01/22 14:12, Aarón Henríquez Quintana ha scritto:

Hi Community,

The reasons that support this new repo are:

* Repair module is isolated in Odoo standard. It depends on stock, account, and sale_management. Nothing to do with manufacture nor rma.

* There are several repair modules in OCA/manufacture and OCA/rma but almost none of them dependens on mrp or rma.

* The number of modules related to repairs is growing. 4 modules in OCA/manufacture (and 7 new module proposals and more incoming) and 4 new module proposals in the OCA/rma repo

Now there are no repair modules in 15.0 branches so I think it is a good moment for doing that.

For the PSC of the repo I guess it makes sense for now if we add the repo under the control of the manufacturing team.

WDYT?

Thank you for considering this proposal.

Have a nice day.

--

Aaron Henríquez Quintana
Technical Consultant

ahenriquez@forgeflow.com

Twitter: /AaronHForgeFlow | Linkedin: /aaron-henriquez-quintana-84299869



_______________________________________________
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 Luis F Miléo - 05:31 - 18 Jan 2022
Sale Workflow v14

Hi all,

FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.

That will easy future tests flows : 2 travis jobs instead of 6.

Best wishes for 2022!

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 03:46 - 10 Jan 2022
3 replies 3 replies
Re: Sale Workflow v14

That's nice! Thanks

On Tue, Jan 11, 2022 at 9:52 AM Daniel Reis <dreis@opensourceintegrators.com> wrote:
Thank you for caring and doing this Denis.

/Daniel

On 11/01/22 07:36, David Beal wrote:

Thanks a lot for this fix,

David BEAL

Akretion

Consultant ERP Odoo

Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.

That will easy future tests flows : 2 travis jobs instead of 6.

Best wishes for 2022!

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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

--

DANIEL REIS
MANAGING DIRECTOR
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34

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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

by Lois Rilo Antelo - 05:01 - 11 Jan 2022

Re: Sale Workflow v14

Thank you for caring and doing this Denis.

/Daniel

On 11/01/22 07:36, David Beal wrote:

Thanks a lot for this fix,

David BEAL

Akretion

Consultant ERP Odoo

Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :

Hi all,

FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.

That will easy future tests flows : 2 travis jobs instead of 6.

Best wishes for 2022!

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium

Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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

--

DANIEL REIS
MANAGING DIRECTOR
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, #34

by Daniel Reis - 09:50 - 11 Jan 2022

Re: Sale Workflow v14

Thanks a lot for this fix,

David BEAL
Akretion
Consultant ERP Odoo

Le lun. 10 janv. 2022 à 15:47, Roussel, Denis <denis.roussel@acsone.eu> a écrit :
Hi all,

FYI and thanks to @hailangv, flows have been improved on sale-workflow v14 as now, two modules that were incompatible together are dependent (sale_isolated_quotation depends on sale_quotation_number). Migration scripts have been taken into account and modules updated their major version.

That will easy future tests flows : 2 travis jobs instead of 6.

Best wishes for 2022!

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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 David BEAL - 08:35 - 11 Jan 2022

Odoo v14 - Bank reconciliation flow

Hello All

First, we send our best wishes for this new year, with success in your projects.

We wanted to reach because we are starting to plan migrations to V14.

We are not satisfied with the v14 bank reconciliation process, and the systematic use of transit accounts on payments.

We started to have an analysis on how we could propose a more direct and simple way of managing payments and bank reconciliation.

We wondered if any of you has already started a project of module on which we could contribute, or have any information / feedback to share on this matter.

Ideally, we would have an option to offer end users, enabling them to manage payments and bank reconciliation with a transit account, or with a direct flow close to the one of v12, but this is still an analysis in progress.

Have a great day.

Julien Jézéquel-Bréard - Chargé de projets

NUMIGI SOLUTIONS INC.

julien.jezequel@numigi.com

Longueuil, Québec, Canada

http://www.numigi.com/

by Julien Jézéquel-Bréard - 10:11 - 7 Jan 2022

2 replies 2 replies

Re: Odoo v14 - Bank reconciliation flow

Hi Julien,

what Graeme is saying is what Odoo put here

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

at 1:30 ff 

Best Frederik

Am Freitag, dem 07.01.2022 um 22:52 +0000 schrieb Graeme Gellatly:

> Just watch the official Odoo video on how to do this.

> 

> Now personally as an accountant I prefer the new way. It is more

> accurate, easy to audit and easier to identify and correct issues,

> but to do the old way you just make the transit account and bank

> account the same.

> 

> On Sat, Jan 8, 2022 at 10:12 AM Julien Jezequel <

> julien.jezequel@numigi.com> wrote:

> > Hello All

> > 

> > First, we send our best wishes for this new year, with success in

> > your projects.

> > 

> > We wanted to reach because we are starting to plan migrations to

> > V14. 

> > 

> > We are not satisfied with the v14 bank reconciliation process, and

> > the systematic use of transit accounts on payments. 

> > 

> > We started to have an analysis on how we could propose a more

> > direct and simple way of managing payments and bank

> > reconciliation. 

> > 

> > We wondered if any of you has already started a project of module

> > on which we could contribute, or have any information / feedback to

> > share on this matter. 

> > 

> > Ideally, we would have an option to offer end users, enabling them

> > to manage payments and bank reconciliation with a transit account,

> > or with a direct flow close to the one of v12, but this is still an

> > analysis in progress. 

> > 

> > Have a great day. 

> > 

> > 

> > Julien Jézéquel-Bréard - Chargé de projets

> > NUMIGI SOLUTIONS INC.

> > julien.jezequel@numigi.com

> > 

> > 

> > Longueuil, Québec, Canada

> > http://www.numigi.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

-- 
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 - 12:11 - 8 Jan 2022

Re: Odoo v14 - Bank reconciliation flow

Just watch the official Odoo video on how to do this.

Now personally as an accountant I prefer the new way. It is more accurate, easy to audit and easier to identify and correct issues, but to do the old way you just make the transit account and bank account the same.

On Sat, Jan 8, 2022 at 10:12 AM Julien Jezequel <julien.jezequel@numigi.com> wrote:
Hello All

First, we send our best wishes for this new year, with success in your projects.

We wanted to reach because we are starting to plan migrations to V14.

We are not satisfied with the v14 bank reconciliation process, and the systematic use of transit accounts on payments.

We started to have an analysis on how we could propose a more direct and simple way of managing payments and bank reconciliation.

We wondered if any of you has already started a project of module on which we could contribute, or have any information / feedback to share on this matter.

Ideally, we would have an option to offer end users, enabling them to manage payments and bank reconciliation with a transit account, or with a direct flow close to the one of v12, but this is still an analysis in progress.

Have a great day.

Julien Jézéquel-Bréard - Chargé de projets
NUMIGI SOLUTIONS INC.
julien.jezequel@numigi.com

Longueuil, Québec, Canada
http://www.numigi.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 - 11:51 - 7 Jan 2022

stock: Retroactively removing lots from incompatible products in stock move history
Hi all, I'm a little bit new to Odoo, so please bear with me if I don't get everything right, but I've been told that I have struck a difficult bug. TL:DR: Having removed the lot_id from certain rows (products that are incompatible with that lot) in stock_move_line and stock_quant, how do I know I haven't broken something? I have a database that was migrated from Odoo 9 to Odoo 12. Before the migration, there was a bug that assigned lots to by-products of a dismantling operation (in this case, empty bottles were assigned the lots of full bottles of wine). As a result, during inventory on Odoo 12, the error message from StockMoveLine._check_lot_product() shows up, correctly identifying that these various lots are incompatible with empty bottles, then aborting the validation. Because these lots were added in error, I want to remove them from all past stock moves. This cannot be done through the UI, so I've made these SQL statements to get it done: ``` update stock_move_line set lot_id = null, lot_name = null where product_id in (67, 38, 29) and lot_id is not null; update stock_quant set lot_id = null where product_id in (67, 38, 29) and lot_id is not null; ``` (the product_ids here are empty bottles) Having run the above on a test/staging database, I can now do the inventory without troubles. I have also verified that the quantities in the inventory have correctly added up (the quantities of bottles that previously had lots are added to the lot-less bottles). The quantities on the `product.product` view have remained the same, which makes sense to me. I have also triggered `_compute_quantities()` for 'product.product', and nothing has changed. Although everything works and my problems seem to have disappeared, the problem is that I do not know whether I have inadvertently corrupted the (test!) database. I've been reading the source code of the stock module to find interactions with lot_id and lot_name, but I've not really found anything troubling. Does my approach make sense? Is there anything I can do to verify the integrity of what I've done? Many thanks and best regards, Carmen Bianca Bakker Coop IT Easy
by Carmen Bianca Bakker - 10:46 - 7 Jan 2022
4 replies 4 replies
Re: stock: Retroactively removing lots from incompatible products in stock move history

Oh FYI,

The inventory issue you've had I've had tens of times. What you've done is pretty much what I do.

On Sat, Jan 8, 2022 at 11:42 AM Graeme Gellatly <gdgellatly@gmail.com> wrote:
Personally if they are meant to have lots I wouldn't null them. Just create them new ones and set.

Now as for quants there are 2 choices (these are v14) - first backport the Odoo way with a server action like this (if database is small) or the second is the same thing just specific to products.
Model Server Action
quants = env['stock.quant'].sudo().search([])

move_line_ids = []
move_line_to_recompute_ids = []

logging = ''

for quant in quants:

move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])

move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])

if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.

if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})

move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids)])

move_lines_to_unreserve = []

for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)

if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))

if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'DEBUG',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})

if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

Or if database is large/many users I create a Server Action on Product secured to inventory manager with an action
if records:
quants = env['stock.quant'].sudo().search([('product_id', 'in', records.ids)])

move_line_ids = []
move_line_to_recompute_ids = []

logging = ''

for quant in quants:

move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])

move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])

if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.

if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})

move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids), ('product_id', 'in', records.ids)])

move_lines_to_unreserve = []

for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)

if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))

if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'INFO',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})

if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

On Fri, 7 Jan 2022, 11:27 pm Carmen Bianca Bakker, <carmen@coopiteasy.be> wrote:
Hello, Bedankt Tom, you are right. I have exclusively updated stock_quant from a previous backup, and I get effectively the same behaviour as I did when I updated both. That helps narrow down my research a lot---thank you. With kindness, Carmen

_______________________________________________
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:51 - 7 Jan 2022

Re: stock: Retroactively removing lots from incompatible products in stock move history

Personally if they are meant to have lots I wouldn't null them. Just create them new ones and set.

Now as for quants there are 2 choices (these are v14) - first backport the Odoo way with a server action like this (if database is small) or the second is the same thing just specific to products.
Model Server Action
quants = env['stock.quant'].sudo().search([])

move_line_ids = []
move_line_to_recompute_ids = []

logging = ''

for quant in quants:

move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])

move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])

if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.

if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})

move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids)])

move_lines_to_unreserve = []

for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)

if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))

if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'DEBUG',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})

if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

Or if database is large/many users I create a Server Action on Product secured to inventory manager with an action
if records:
quants = env['stock.quant'].sudo().search([('product_id', 'in', records.ids)])

move_line_ids = []
move_line_to_recompute_ids = []

logging = ''

for quant in quants:

move_lines = env['stock.move.line'].search([
('product_id', '=', quant.product_id.id),
('location_id', '=', quant.location_id.id),
('lot_id', '=', quant.lot_id.id),
('package_id', '=', quant.package_id.id),
('owner_id', '=', quant.owner_id.id),
('product_qty', '!=', 0),
])

move_line_ids += move_lines.ids
reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])

if quant.location_id.should_bypass_reservation():
# If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
# should be 0.
if quant.reserved_quantity != 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
else:
logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
logging += '******************\n'
quant.write({'reserved_quantity': 0})
else:
# If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
# of the `product_qty` of all the partially_available / assigned move lines with the same
# characteristics.

if quant.reserved_quantity == 0:
if move_lines:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
elif quant.reserved_quantity < 0:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` field is negative while it should not happen\n"
quant.write({'reserved_quantity': 0})
if move_lines:
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
logging += '******************\n'
else:
if reserved_on_move_lines != quant.reserved_quantity:
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})
else:
if any(move_line.product_qty < 0 for move_line in
move_lines):
logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
logging += '******************\n'
move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
move_line_to_recompute_ids += move_lines.ids
quant.write({'reserved_quantity': 0})

move_lines = env['stock.move.line'].search([('product_id.type', '=',
'product'), ('product_qty', '!=', 0), ('id', 'not in',
move_line_ids), ('product_id', 'in', records.ids)])

move_lines_to_unreserve = []

for move_line in move_lines:
if not move_line.location_id.should_bypass_reservation():
logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
logging += "There is no exiting quants despite its `reserved_quantity`\n"
logging += '******************\n'
move_lines_to_unreserve.append(move_line.id)
move_line_to_recompute_ids.append(move_line.id)

if len(move_lines_to_unreserve) > 0:
env.cr.execute("""
UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
"""
% (tuple(move_lines_to_unreserve), ))

if logging:
env['ir.logging'].sudo().create({
'name': 'Unreserve stock.quant and stock.move.line',
'type': 'server',
'level': 'INFO',
'dbname': env.cr.dbname,
'message': logging,
'func': '_update_reserved_quantity',
'path': 'addons/stock/models/stock_quant.py',
'line': '0',
})

if move_line_to_recompute_ids:
env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

On Fri, 7 Jan 2022, 11:27 pm Carmen Bianca Bakker, <carmen@coopiteasy.be> wrote:
Hello, Bedankt Tom, you are right. I have exclusively updated stock_quant from a previous backup, and I get effectively the same behaviour as I did when I updated both. That helps narrow down my research a lot---thank you. With kindness, Carmen

_______________________________________________
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:46 - 7 Jan 2022

Re: stock: Retroactively removing lots from incompatible products in stock move history

Hello, Bedankt Tom, you are right. I have exclusively updated stock_quant from a previous backup, and I get effectively the same behaviour as I did when I updated both. That helps narrow down my research a lot---thank you. With kindness, Carmen

by Carmen Bianca Bakker - 11:26 - 7 Jan 2022

Re: stock: Retroactively removing lots from incompatible products in stock move history

On 1/7/22 10:47 AM, Carmen Bianca Bakker wrote:

I have also verified that the quantities in the inventory have correctly added up (the quantities of bottles that previously had lots are added to the lot-less bottles).

I think at least for the stock_quant table, this is all you had to verify, and you have, so that's fine.

As for the modification that you did in "stock_move_line", I'm less sure - you're changing history there. I'm also not sure if doing that was really necessary to achieve your goal to make the inventory work again.

If you want to be sure, I would revert the stock move line table to a recent backup, and then do some more testing in a test database if that modification is really necessary.

by Tom Blauwendraat - 11:06 - 7 Jan 2022
Odoo Users List

Hi,

I would like to see if you or your company is interested in acquiring any Odoo Contact List which can help you to grow your business and boost your sales.

We can also help you with Web Design, WordPress, WordPress Development, WordPress Design, Odoo eCommerce, Odoo CRM, and many more.

Let me know your preferred Target Geography____ so that I can get back to you with the counts and pricing.

I look forward to your response!

Regards,

Caitlyn Drake

Demand Generation

by "Caitlyn Drake" <caitlyn.drake@infodatasource.com> - 05:51 - 6 Jan 2022
Stock Valuation by LOT

Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

by Kitti Upariphutthiphong - 11:26 - 30 Dec 2021
6 replies 6 replies
Re: Stock Valuation by LOT

Thank you very much.

Happy New Year to all OCA members!

On Fri, Dec 31, 2021, 08:42 Graeme Gellatly <gdgellatly@gmail.com> wrote:
Hi Kitti,

I have a module. Its basic usage is to trick FIFO into behaving like actual cost for tracked products.

https://github.com/odoonz/odoonz-addons/tree/14.0/stock_tracked_fifo_valuation

It is well tested on v12, however v14 is only just being deployed.

On Fri, Dec 31, 2021 at 4:51 AM Kitti U. <kittiu@ecosoft.co.th> wrote:
Yes that would be awesome!

On Thu, Dec 30, 2021, 21:12 Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com> wrote:
I have something similar that I make for V13, it's not in OCA but I can make a PR with this module,

I have two modules, one that value stock by lot and other that value stock by warehouse.

I'm a little busy this days, I can make the PR and give you access to continue the PR to comply with OCA standards if you are OK.

El jue., 30 de diciembre de 2021 5:21 a. m., Kitti U. <kittiu@ecosoft.co.th> escribió:
Hi Dominque,

Thanks for the response. Yes, FIFO in fact not matter much, it is the way to give default LOT that is available by FIFO. I found something similar to my need like this,
https://apps.odoo.com/apps/modules/15.0/real_costing_method
https://apps.odoo.com/apps/modules/14.0/oi_stock_account_actual
https://apps.odoo.com/apps/modules/14.0/cost_method_lot (I like this one)

Your suggestions can help me making such module to OCA, thanks!

I want to make sure that OCA don't have anything similar yet.

On Thu, Dec 30, 2021 at 5:56 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
Hi Kitti,
Here (in Singapore), it is accepted that FIFO should not be by lot because FIFO is an accounting policy, independent from the warehouse operations.
And in cases that the users need cost information by lot, e.g. in trading business, with lots of suppliers with various costs for the same product, we added the function to calculate the cost from a lot, by searching the PO that brought the lot in the stock.

My two cents, if that helps.
Dominique

On Thu, 30 Dec 2021 at 18:27, Kitti U. <kittiu@ecosoft.co.th> wrote:
Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

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

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

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

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

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

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

by Kitti Upariphutthiphong - 01:51 - 31 Dec 2021

Re: Stock Valuation by LOT

Hi Kitti,

I have a module. Its basic usage is to trick FIFO into behaving like actual cost for tracked products.

https://github.com/odoonz/odoonz-addons/tree/14.0/stock_tracked_fifo_valuation

It is well tested on v12, however v14 is only just being deployed.

On Fri, Dec 31, 2021 at 4:51 AM Kitti U. <kittiu@ecosoft.co.th> wrote:
Yes that would be awesome!

On Thu, Dec 30, 2021, 21:12 Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com> wrote:
I have something similar that I make for V13, it's not in OCA but I can make a PR with this module,

I have two modules, one that value stock by lot and other that value stock by warehouse.

I'm a little busy this days, I can make the PR and give you access to continue the PR to comply with OCA standards if you are OK.

El jue., 30 de diciembre de 2021 5:21 a. m., Kitti U. <kittiu@ecosoft.co.th> escribió:
Hi Dominque,

Thanks for the response. Yes, FIFO in fact not matter much, it is the way to give default LOT that is available by FIFO. I found something similar to my need like this,
https://apps.odoo.com/apps/modules/15.0/real_costing_method
https://apps.odoo.com/apps/modules/14.0/oi_stock_account_actual
https://apps.odoo.com/apps/modules/14.0/cost_method_lot (I like this one)

Your suggestions can help me making such module to OCA, thanks!

I want to make sure that OCA don't have anything similar yet.

On Thu, Dec 30, 2021 at 5:56 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
Hi Kitti,
Here (in Singapore), it is accepted that FIFO should not be by lot because FIFO is an accounting policy, independent from the warehouse operations.
And in cases that the users need cost information by lot, e.g. in trading business, with lots of suppliers with various costs for the same product, we added the function to calculate the cost from a lot, by searching the PO that brought the lot in the stock.

My two cents, if that helps.
Dominique

On Thu, 30 Dec 2021 at 18:27, Kitti U. <kittiu@ecosoft.co.th> wrote:
Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

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

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

_______________________________________________
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 Graeme Gellatly - 02:36 - 31 Dec 2021

Re: Stock Valuation by LOT

Yes that would be awesome!

On Thu, Dec 30, 2021, 21:12 Jesús Alan Ramos Rodríguez <alan.ramos@jarsa.com> wrote:
I have something similar that I make for V13, it's not in OCA but I can make a PR with this module,

I have two modules, one that value stock by lot and other that value stock by warehouse.

I'm a little busy this days, I can make the PR and give you access to continue the PR to comply with OCA standards if you are OK.

El jue., 30 de diciembre de 2021 5:21 a. m., Kitti U. <kittiu@ecosoft.co.th> escribió:
Hi Dominque,

Thanks for the response. Yes, FIFO in fact not matter much, it is the way to give default LOT that is available by FIFO. I found something similar to my need like this,
https://apps.odoo.com/apps/modules/15.0/real_costing_method
https://apps.odoo.com/apps/modules/14.0/oi_stock_account_actual
https://apps.odoo.com/apps/modules/14.0/cost_method_lot (I like this one)

Your suggestions can help me making such module to OCA, thanks!

I want to make sure that OCA don't have anything similar yet.

On Thu, Dec 30, 2021 at 5:56 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
Hi Kitti,
Here (in Singapore), it is accepted that FIFO should not be by lot because FIFO is an accounting policy, independent from the warehouse operations.
And in cases that the users need cost information by lot, e.g. in trading business, with lots of suppliers with various costs for the same product, we added the function to calculate the cost from a lot, by searching the PO that brought the lot in the stock.

My two cents, if that helps.
Dominique

On Thu, 30 Dec 2021 at 18:27, Kitti U. <kittiu@ecosoft.co.th> wrote:
Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

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

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

_______________________________________________
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 Kitti Upariphutthiphong - 04:51 - 30 Dec 2021

Re: Stock Valuation by LOT

I have something similar that I make for V13, it's not in OCA but I can make a PR with this module,

I have two modules, one that value stock by lot and other that value stock by warehouse.

I'm a little busy this days, I can make the PR and give you access to continue the PR to comply with OCA standards if you are OK.

El jue., 30 de diciembre de 2021 5:21 a. m., Kitti U. <kittiu@ecosoft.co.th> escribió:
Hi Dominque,

Thanks for the response. Yes, FIFO in fact not matter much, it is the way to give default LOT that is available by FIFO. I found something similar to my need like this,
https://apps.odoo.com/apps/modules/15.0/real_costing_method
https://apps.odoo.com/apps/modules/14.0/oi_stock_account_actual
https://apps.odoo.com/apps/modules/14.0/cost_method_lot (I like this one)

Your suggestions can help me making such module to OCA, thanks!

I want to make sure that OCA don't have anything similar yet.

On Thu, Dec 30, 2021 at 5:56 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
Hi Kitti,
Here (in Singapore), it is accepted that FIFO should not be by lot because FIFO is an accounting policy, independent from the warehouse operations.
And in cases that the users need cost information by lot, e.g. in trading business, with lots of suppliers with various costs for the same product, we added the function to calculate the cost from a lot, by searching the PO that brought the lot in the stock.

My two cents, if that helps.
Dominique

On Thu, 30 Dec 2021 at 18:27, Kitti U. <kittiu@ecosoft.co.th> wrote:
Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

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

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

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

by "Jesús Alan Ramos Rodríguez" <alan.ramos@jarsa.com> - 03:11 - 30 Dec 2021

Re: Stock Valuation by LOT

Hi Dominque,

Thanks for the response. Yes, FIFO in fact not matter much, it is the way to give default LOT that is available by FIFO. I found something similar to my need like this,
https://apps.odoo.com/apps/modules/15.0/real_costing_method
https://apps.odoo.com/apps/modules/14.0/oi_stock_account_actual
https://apps.odoo.com/apps/modules/14.0/cost_method_lot (I like this one)

Your suggestions can help me making such module to OCA, thanks!

I want to make sure that OCA don't have anything similar yet.

On Thu, Dec 30, 2021 at 5:56 PM Dominique k <dominique.k@elico-corp.com.sg> wrote:
Hi Kitti,
Here (in Singapore), it is accepted that FIFO should not be by lot because FIFO is an accounting policy, independent from the warehouse operations.
And in cases that the users need cost information by lot, e.g. in trading business, with lots of suppliers with various costs for the same product, we added the function to calculate the cost from a lot, by searching the PO that brought the lot in the stock.

My two cents, if that helps.
Dominique

On Thu, 30 Dec 2021 at 18:27, Kitti U. <kittiu@ecosoft.co.th> wrote:
Dear community,

Currently, I am looking for perpetual stock valuation with FIFO method, using LOT.

So far, I found out that, even though we already use LOT on stock move (same product, different price by LOT), Odoo, the stock valuation report do not show by LOT, but new average cost.

Also, on case Return stock, it also don't use cost by LOT, but the average cost.

Are there module in OCA helping out?

Many thanks!

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

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

by Kitti Upariphutthiphong - 12:20 - 30 Dec 2021

Apply to community PSC

Hi all,

I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.

Thanks.

Regards.

by Pedro M. Baeza - 01:45 - 29 Dec 2021

8 replies 8 replies

Re: Apply to community PSC

Thank you! :)

On Wed, Dec 29, 2021 at 3:47 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:

Thanks for the quick reaction.

Happy Christmas to all!

El mié., 29 dic. 2021 15:57, Frederik Kramer <frederik.kramer@initos.com> escribió:

Of course +1 and thanks for helping on this one 

Best Frederik

Am Mittwoch, dem 29.12.2021 um 12:47 +0000 schrieb Pedro M. Baeza
(Tecnativa):



> Hi all,



> 



> I want to request your approval to be part of the community PSC,



> which is in charge of OCA infrastructure and stuff like CI, for me



> and my colleague Joao, as we both intervene in these processes and



> can contribute with quick reactions over some events like the one



> happened yesterday.



> 



> Thanks.



> 



> Regards.



> _______________________________________________



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



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



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



-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
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

by João Marques - 11:05 - 30 Dec 2021

Re: Apply to community PSC

Thanks for the quick reaction.

Happy Christmas to all!

El mié., 29 dic. 2021 15:57, Frederik Kramer <frederik.kramer@initos.com> escribió:

Of course +1 and thanks for helping on this one 

Best Frederik

Am Mittwoch, dem 29.12.2021 um 12:47 +0000 schrieb Pedro M. Baeza
(Tecnativa):


> Hi all,


> 


> I want to request your approval to be part of the community PSC,


> which is in charge of OCA infrastructure and stuff like CI, for me


> and my colleague Joao, as we both intervene in these processes and


> can contribute with quick reactions over some events like the one


> happened yesterday.


> 


> Thanks.


> 


> Regards.


> _______________________________________________


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


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


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


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
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 Pedro M. Baeza - 04:46 - 29 Dec 2021

Re: Apply to community PSC

Of course +1 and thanks for helping on this one 

Best Frederik

Am Mittwoch, dem 29.12.2021 um 12:47 +0000 schrieb Pedro M. Baeza
(Tecnativa):

> Hi all,

> 

> I want to request your approval to be part of the community PSC,

> which is in charge of OCA infrastructure and stuff like CI, for me

> and my colleague Joao, as we both intervene in these processes and

> can contribute with quick reactions over some events like the one

> happened yesterday.

> 

> Thanks.

> 

> Regards.

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
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 - 03:56 - 29 Dec 2021

Re: Apply to community PSC

Dear Pedro and Joäo,

I've added you to PSC members. As usual the sync will take a while.

Bests,

On Wed, Dec 29, 2021 at 1:57 PM Simone Orsi <simahawk@gmail.com> wrote:
Hola, +1 :)

On Wed, Dec 29, 2021 at 1:47 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Hi all,

I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.

Thanks.

Regards.

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 02:06 - 29 Dec 2021
Re: Apply to community PSC

Hola, +1 :)

On Wed, Dec 29, 2021 at 1:47 PM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Hi all,

I want to request your approval to be part of the community PSC, which is in charge of OCA infrastructure and stuff like CI, for me and my colleague Joao, as we both intervene in these processes and can contribute with quick reactions over some events like the one happened yesterday.

Thanks.

Regards.

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

--
Simone Orsi

Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.

by Simone Orsi - 02:01 - 29 Dec 2021

Boolean grouped line label

Hi there,

Do you know any module to improve the display of the grouped lines on a boolean field ?

In the following example I'd like to see "Active: Yes (5)" (or "Active: True (5)" where true can be translated) instead of "true (5)".

If not, I'm thinking of creating a new PR on the web repo which could be named web_boolean_group_label.

Your comments are appreciated !

Regards,

--
Pierre Verkest
06 81 12 25 20
Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

by Pierre Verkest - 02:36 - 24 Dec 2021

1 attachments 1 attachments

image.png
2 replies 2 replies
Re: Boolean grouped line label

For the record, your image is not visible because odoo hosted on odoo-community.org does not implement this fix:
https://github.com/odoo/odoo/pull/78390

--
Yann PAPOUIN, Ingénieur R&D | DEC

Le ven. 24 déc. 2021 à 14:37, Pierre Verkest <pierreverkest84@gmail.com> a écrit :
Hi there,

Do you know any module to improve the display of the grouped lines on a boolean field ?

In the following example I'd like to see "Active: Yes (5)" (or "Active: True (5)" where true can be translated) instead of "true (5)".

If not, I'm thinking of creating a new PR on the web repo which could be named web_boolean_group_label.

Your comments are appreciated !

Regards,

--
Pierre Verkest
06 81 12 25 20
Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest

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

by Yann Papouin - 05:06 - 29 Dec 2021

Re: Boolean grouped line label

I don't know any about that, but for me it hasn't been something annoying.

Regards.

by Pedro M. Baeza - 03:51 - 24 Dec 2021

Does OCA's runbot use OCB ?

Title says all. Can someone answer this question to complete the OCB faq 
on the wiki ?
https://github.com/OCA/OCB/wiki/FAQ


-- 
Librement,
Xavier Brochard (zeroheure) xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)

by xavier - 10:20 - 15 Dec 2021

stock_inventory repository

Hi all,

As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.

@OCA/board

Thanks

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 11:11 - 14 Dec 2021
8 replies 8 replies
Re: stock_inventory repository

The way they refactor it can work out of the box.

But, I suspect from that version, a bunch of modules will come. As Lois said, a way to group things to do (not simply through the quant tree), ...

Ok, let's wait for now first contribution and decide after.

On Tue, Dec 14, 2021 at 4:46 PM Cyril VINH-TUNG <cyril@invitu.com> wrote:
Dear all

Odoo did a video that explains inventory adjustments in v15

https://youtu.be/GP3bmOrYnTg

--

Best Regards/Cordialement
--------------------------------
Cyril VINH-TUNG
INVITU Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99 contact@invitu.com www.invitu.com

P Please consider the environment before printing this e-mail!

Le mar. 14 déc. 2021 à 03:06, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

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

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 05:11 - 14 Dec 2021

Re: stock_inventory repository

Dear all

Odoo did a video that explains inventory adjustments in v15

https://youtu.be/GP3bmOrYnTg

--

Best Regards/Cordialement
--------------------------------
Cyril VINH-TUNG
INVITU Computer & Network Engineering
BP 32 - 98713 Papeete - French Polynesia
Tél: +689 40 46 11 99 contact@invitu.com www.invitu.com

P Please consider the environment before printing this e-mail!

Le mar. 14 déc. 2021 à 03:06, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

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 Cyril VINH-TUNG - 04:46 - 14 Dec 2021

Re: stock_inventory repository

I agree with you both, I also thought that the new behavior is not usable for large warehouses (cannot really filter, assign work, keep record of operators work...). Also using stock.move.line as history of past inventories seems an over simplification.

For reference, the change was done here: https://github.com/odoo/odoo/pull/68409. They state that they include cycle counts, bulk assignment... but I could not do that on a quick test. I will have a look in detail in the next days, but it seems that maintaining stock.inventory in the OCA is a good idea.

Regards,

El mar, 14 dic 2021 a las 14:06, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:
Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

Regards.

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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

by Lois Rilo Antelo - 02:41 - 14 Dec 2021

Re: stock_inventory repository

Indeed checking quickly in runbot, I see no way of telling "I want to make an inventory of this location (and children)" now, so a module that restores this concept (through a model called `stock.inventory` or whatever), and then present the stock.quant view filtered by that criteria may be enough, and mount the rest over this base.

Regards.

by Pedro M. Baeza - 02:06 - 14 Dec 2021

Re: stock_inventory repository

I think about your cycle_count module(s), inventory_preparation_* modules that are mostly used (as migrated to every version) and to avoid breaking changes (as it is a drawback when you are in a migration process).

@Pedro This has been triggered by Sylvain Legal there https://github.com/OCA/stock-logistics-warehouse/issues/1328 and seems to be legit.

On Tue, Dec 14, 2021 at 1:42 PM Lois Rilo Antelo <lois.rilo@forgeflow.com> wrote:
Hi,

I have seen that change but still haven't analyzed what should be the way to go... are you suggesting that OCA keeps the stock.inventory model and migrate all those modules on top of that?

Regards,

El mar, 14 dic 2021 a las 11:16, Francesco Apruzzese (<cescoap@gmail.com>) escribió:
+1

Il giorno mar 14 dic 2021 alle ore 11:12 Roussel, Denis <denis.roussel@acsone.eu> ha scritto:
Hi all,

As Odoo removed inventory model in v15 and as there are a bunch of modules for inventory in stock-logistics-warehouse repo, I request the creation of stock-inventory repository.

@OCA/board

Thanks

--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | 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

--

Francesco Apruzzese

Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

_______________________________________________
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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 01:51 - 14 Dec 2021
Move purchase_request* and purchase_work_acceptance*

Hi all,

To reduce purchase-workflow repository size, I would suggest to create two new repositories in order to speed up tests.

Thanks
--

Denis Roussel
Software Engineer
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 09:35 - 14 Dec 2021
11 replies 11 replies
Re: Move purchase_request* and purchase_work_acceptance*

We can use readme to store this information. One file, all the info.

Il giorno mar 21 dic 2021 alle ore 13:32 Yann Papouin <ypa@decgroupe.com> ha scritto:
As I was in that case, why not creating a file with the same name for each moved module with a text content:
Module moved to repository xxxxx

--
Yann PAPOUIN, Ingénieur R&D | DEC

Le mar. 21 déc. 2021 à 11:27, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

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

--

Francesco Apruzzese

Profilo professionale: http://it.linkedin.com/in/francescoapruzzese

Il contenuto di questo messaggio elettronico è riservato e tutelato dal segreto professionale ed è rivolto esclusivamente al/ai destinatario/i identificato/i. Pertanto è proibito leggerlo, copiarlo, divulgarlo o utilizzarlo da parte di chiunque salvo il/i destinatario/i. Se non siete il destinatario, vi invitiamo a cancellare il messaggio ed eventuali allegati dandocene immediatamente comunicazione scritta a mezzo posta elettronica.
This e-mail and any attachments are confidential and may contain information intended for the addressee(s) only. Reading, copying, disclosure or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e-mail.

Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.

by Francesco Apruzzese - 02:01 - 21 Dec 2021

Re: Move purchase_request* and purchase_work_acceptance*

El mar, 21 dic 2021 a las 13:32, Yann Papouin (<ypa@decgroupe.com>) escribió:
As I was in that case, why not creating a file with the same name for each moved module with a text content:
Module moved to repository xxxxx

In my experience, that's more maintenance burden on our part with no reward because people still don't look.

Regards.

by Pedro M. Baeza - 01:41 - 21 Dec 2021

Re: Move purchase_request* and purchase_work_acceptance*

As I was in that case, why not creating a file with the same name for each moved module with a text content:
Module moved to repository xxxxx

--
Yann PAPOUIN, Ingénieur R&D | DEC

Le mar. 21 déc. 2021 à 11:27, Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> a écrit :
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

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 Yann Papouin - 01:31 - 21 Dec 2021

Re: Move purchase_request* and purchase_work_acceptance*

I agree with Pedro.

The amount of modules is not the only factor to take into account.

The aim of a repository is also to group functionally modules that do 'quite' the same things and has a specific meaning (I don't like *-workflow stuff as it is too generic - @kitti don't create purchase-extra-workflow as it adds abstraction and has no meaning).

To find modules, we have our shop that leads to the good repository (we maybe need to do marketing on this)

On Tue, Dec 21, 2021 at 11:27 AM Pedro M. Baeza (Tecnativa) <pedro.baeza@tecnativa.com> wrote:
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

Regards.

_______________________________________________
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
T : +32 2 888 31 49
M : +32 472 22 00 57

Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
Zone industrielle 22 | L-8287 Kehlen | Luxembourg

by Denis Roussel - 11:50 - 21 Dec 2021

Re: Move purchase_request* and purchase_work_acceptance*

Hi,

I don't have a strong opinion on this one, if you want to split purchase-workflow, I'm fine with that.

For me the real problem, and to bring another consideration to the table, are the repos with "rebel" addons that forces you to have multiple pipelines with some addons excluded and other with them included, it happens often that a contributor ends having to fix other modules tests when you opening a new PR of a new module. This happens in purchase-workflow but also in sale-workflow.

Regards,

El mar, 21 dic 2021 a las 11:27, Pedro M. Baeza (Tecnativa) (<pedro.baeza@tecnativa.com>) escribió:
Now that having a lot of runboat instances is not too much of a problem, I think it's better to split the maximum repos for smaller sets of modules, so I will go to all of them that we are talking about. Reducing the number of them will:

- Avoid potential conflicts between them.
- Reduce tests size.

On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

Regards.

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

--
Lois Rilo Antelo
Odoo consultant at ForgeFlow S.L.
lois.rilo@forgeflow.com | https://www.forgeflow.com
Twitter: /LoisRForgeFlow

by Lois Rilo Antelo - 11:46 - 21 Dec 2021

Decision tree to solve issues

Hi all,

I think anyone knows about decision trees, if even as jokes:

A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

I can imagine modeling something like this, but doesnt it already exist?

I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

Any ideas?

Tom

by Tom Blauwendraat - 03:16 - 10 Dec 2021

1 attachments 1 attachments

5 replies 5 replies

Re: Decision tree to solve issues

Check out the mermaid widget in web repo.

Also In odoo a decision tree is a multi step wizard. I could see how to do that with some very fancy context passing to a generic wizard.

On Sat, 11 Dec 2021, 7:17 am Xavier Brochard, <xavier@alternatif.org> wrote:

This sound very much like reverting a task with dependencies :

To work the printer need
->to be turned on
-->green light
--->paper
--->toner
-> to be online
-->network cable plugged in
-->no paper jam
etc.

---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)

Le 10.12.2021 17:57, Tom a écrit :


> Hi Pierre


> 


> Thanks!


> 


> What I'm looking for is more something on the lines of:


> 


> - There is a decision.tree model eg "How to fix your printer"


> - It can have decision.tree.node children such as "Is it turned on?"


> - Each question node has a set of conditions as to which next node it


> jumps to like: condition1,node1,condition2,node2...


> - If there are no conditions on a node anymore then this is an end


> node saying like "Your printer is irrefutably broken. Please send it


> back."


> 


> Kind of like a "Choose your own adventure" book.


> 


> -Tom


> 


> 


> Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:


> 


> 


> Hi,


> 


> 


> At anybox the project management was(/is ?) based on top of such idea


> where we could import mindmap as project starting point. Module is


> called anytracker and available on github here:


> https://github.com/anybox/anytracker [1] .


> 


> 


> A project is an anytracker.ticket without parent


> A task is an anytracker.ticket without child


> A node becomes a node when a child appears !


> 


> After a while we add the concept of anytracker.bouquet which is a


> couple of anytracker.ticket which could be a milestone, a release or


> whatever that has some sense to group together without changing the


> ticket tree !


> 


> hope that helps


> 


> 


> 


> 


> 


> Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl


> [2] > a écrit :


> 


> 


> Hi all,


> I think anyone knows about decision trees, if even as jokes:


> 


> A customer wants something like this, not the visualisation per-se,


> but to be able to have users click through it whenever they have an


> issue.


> I can imagine modeling something like this, but doesnt it already 


> exist?


> I guess the Odoo "Survey" modules can do part of it, but i don't know


> if they support structuring the survey as a tree.


> Any ideas?


> Tom


> 


> _______________________________________________ Mailing-List:


> https://odoo-community.org/groups/contributors-15 [3]  Post to:


> mailto: contributors@odoo-community.org [4]  Unsubscribe:


> https://odoo-community.org/groups?unsubscribe [5]


> 


> 


> --


> 


> Pierre


> 


> 


> _______________________________________________ Mailing-List:


> https://odoo-community.org/groups/contributors-15 [6]  Post to:


> mailto:contributors@odoo-community.org Unsubscribe:


> https://odoo-community.org/groups?unsubscribe [7]


> 


> 


> 


> _______________________________________________


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


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


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


> 


> 


> 


> [1] https://github.com/anybox/anytracker


> [2] mailto:tom@sunflowerweb.nl


> [3] https://odoo-community.org/groups/contributors-15


> [4] mailto:contributors@odoo-community.org


> [5] https://odoo-community.org/groups?unsubscribe


> [6] https://odoo-community.org/groups/contributors-15


> [7] https://odoo-community.org/groups?unsubscribe


> [8] https://odoo-community.org/groups/contributors-15


> [9] https://odoo-community.org/groups?unsubscribe

by Graeme Gellatly - 08:25 - 10 Dec 2021

Re: Decision tree to solve issues

This sound very much like reverting a task with dependencies :

To work the printer need
->to be turned on
-->green light
--->paper
--->toner
-> to be online
-->network cable plugged in
-->no paper jam
etc.

---
Librement,
Xavier Brochard xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)

Le 10.12.2021 17:57, Tom a écrit :

> Hi Pierre

> 

> Thanks!

> 

> What I'm looking for is more something on the lines of:

> 

> - There is a decision.tree model eg "How to fix your printer"

> - It can have decision.tree.node children such as "Is it turned on?"

> - Each question node has a set of conditions as to which next node it

> jumps to like: condition1,node1,condition2,node2...

> - If there are no conditions on a node anymore then this is an end

> node saying like "Your printer is irrefutably broken. Please send it

> back."

> 

> Kind of like a "Choose your own adventure" book.

> 

> -Tom

> 

> 

> Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

> 

> 

> Hi,

> 

> 

> At anybox the project management was(/is ?) based on top of such idea

> where we could import mindmap as project starting point. Module is

> called anytracker and available on github here:

> https://github.com/anybox/anytracker [1] .

> 

> 

> A project is an anytracker.ticket without parent

> A task is an anytracker.ticket without child

> A node becomes a node when a child appears !

> 

> After a while we add the concept of anytracker.bouquet which is a

> couple of anytracker.ticket which could be a milestone, a release or

> whatever that has some sense to group together without changing the

> ticket tree !

> 

> hope that helps

> 

> 

> 

> 

> 

> Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl

> [2] > a écrit :

> 

> 

> Hi all,

> I think anyone knows about decision trees, if even as jokes:

> 

> A customer wants something like this, not the visualisation per-se,

> but to be able to have users click through it whenever they have an

> issue.

> I can imagine modeling something like this, but doesnt it already 

> exist?

> I guess the Odoo "Survey" modules can do part of it, but i don't know

> if they support structuring the survey as a tree.

> Any ideas?

> Tom

> 

> _______________________________________________ Mailing-List:

> https://odoo-community.org/groups/contributors-15 [3]  Post to:

> mailto: contributors@odoo-community.org [4]  Unsubscribe:

> https://odoo-community.org/groups?unsubscribe [5]

> 

> 

> --

> 

> Pierre

> 

> 

> _______________________________________________ Mailing-List:

> https://odoo-community.org/groups/contributors-15 [6]  Post to:

> mailto:contributors@odoo-community.org Unsubscribe:

> https://odoo-community.org/groups?unsubscribe [7]

> 

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1] https://github.com/anybox/anytracker

> [2] mailto:tom@sunflowerweb.nl

> [3] https://odoo-community.org/groups/contributors-15

> [4] mailto:contributors@odoo-community.org

> [5] https://odoo-community.org/groups?unsubscribe

> [6] https://odoo-community.org/groups/contributors-15

> [7] https://odoo-community.org/groups?unsubscribe

> [8] https://odoo-community.org/groups/contributors-15

> [9] https://odoo-community.org/groups?unsubscribe

by xavier - 07:16 - 10 Dec 2021

Re: Decision tree to solve issues

hum... ok so not sure that's helps that much then even you could reproduce the tree using title as answer node description as question that would probably not suit as usage...

Le ven. 10 déc. 2021 à 17:57, Tom <tom@sunflowerweb.nl> a écrit :
Hi Pierre

Thanks!

What I'm looking for is more something on the lines of:

- There is a decision.tree model eg "How to fix your printer"
- It can have decision.tree.node children such as "Is it turned on?"
- Each question node has a set of conditions as to which next node it jumps to like: condition1,node1,condition2,node2...
- If there are no conditions on a node anymore then this is an end node saying like "Your printer is irrefutably broken. Please send it back."

Kind of like a "Choose your own adventure" book.

-Tom

Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

Hi,

At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

A project is an anytracker.ticket without parent

A task is an anytracker.ticket without child

A node becomes a node when a child appears !

After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

hope that helps

Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

Hi all,

I think anyone knows about decision trees, if even as jokes:

A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

I can imagine modeling something like this, but doesnt it already exist?

I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

Any ideas?

Tom

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

--

Pierre

_______________________________________________
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

--
Pierre

by Pierre Verkest - 06:31 - 10 Dec 2021
Re: Decision tree to solve issues

Hi Pierre

Thanks!

What I'm looking for is more something on the lines of:

- There is a decision.tree model eg "How to fix your printer"
- It can have decision.tree.node children such as "Is it turned on?"
- Each question node has a set of conditions as to which next node it jumps to like: condition1,node1,condition2,node2...
- If there are no conditions on a node anymore then this is an end node saying like "Your printer is irrefutably broken. Please send it back."

Kind of like a "Choose your own adventure" book.

-Tom

Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

Hi,

At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

A project is an anytracker.ticket without parent

A task is an anytracker.ticket without child

A node becomes a node when a child appears !

After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

hope that helps

Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

Hi all,

I think anyone knows about decision trees, if even as jokes:

A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

I can imagine modeling something like this, but doesnt it already exist?

I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

Any ideas?

Tom

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

--

Pierre

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

by Tom Blauwendraat - 05:55 - 10 Dec 2021
Re: Decision tree to solve issues

Hi,

At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

A project is an anytracker.ticket without parent
A task is an anytracker.ticket without child
A node becomes a node when a child appears !

After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

hope that helps

Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

Hi all,

I think anyone knows about decision trees, if even as jokes:

A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

I can imagine modeling something like this, but doesnt it already exist?

I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

Any ideas?

Tom

_______________________________________________
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 - 05:30 - 10 Dec 2021

How to use oca-ci
Hi, I just read the README.md of the https://github.com/OCA/oca-ci project, Does anyone have experience using this to develop and test locally? I am probably not that smart, but I miss in the README.md information to get started or how tu use this. Kind regards, Ronald
by Ronald Portier - 08:50 - 9 Dec 2021
2 replies 2 replies
Re: How to use oca-ci

Hi Ronald,

I personally never tried to use it for local development. I occasionally ran it locally, mainly to prepare automated tests of the image themselves.

The steps are basically those done by the OCA GitHub action (example here).

I'll be happy to give guidance and answer questions by anyone who wants to explore this and document it further.

Best regards,

-sbi

On Thu, Dec 9, 2021 at 8:51 AM Ronald Portier <ronald@therp.nl> wrote:
Hi, I just read the README.md of the https://github.com/OCA/oca-ci project, Does anyone have experience using this to develop and test locally? I am probably not that smart, but I miss in the README.md information to get started or how tu use this. Kind regards, Ronald

_______________________________________________
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 - 11:46 - 14 Dec 2021

Re: How to use oca-ci

+1

Le jeudi 9 décembre 2021, Ronald Portier <ronald@therp.nl> a écrit :
> Hi,
>
>
> I just read the README.md of the https://github.com/OCA/oca-ci project,
>
>
> Does anyone have experience using this to develop and test locally?
>
>
> I am probably not that smart, but I miss in the README.md information to
> get started or how tu use this.
>
>
> Kind regards,
>
>
> Ronald
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe
>

--
Sylvain LE GAL - Twitter
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.17
Service Informatique : (+33) 09.73.79.64.40
Astreinte Informatique : (+33) 06.81.85.61.43
Member of the OCA (Odoo Community Association)
Web Site | Twitter

by Sylvain LE GAL - 09:31 - 9 Dec 2021
Tracing and in general how can we execute an handler on every request

Hello all,

I have a technical question and I wonder if anyone here already faced this issue.

I am trying to integrate Odoo into our monitoring stack, with the three pillars of observability metrics/logging/tracing, starting with the tracing. My issue is, it doesn't look like we have an easy way to insert the handler which will start the trace. Also no documentation anywhere about how we can easily integrate tracing into Odoo. This is a v12 version but I believe the issue is still here on more recent versions.

We are planning to use Azure Monitor, but the issue will be the same with any other tracing platform : I can't figure a way to override a core function to start the trace and insert the python library I need https://docs.microsoft.com/fr-fr/azure/azure-monitor/app/opencensus-python#tracing

I can of course override some of the most important controllers like https://github.com/odoo/odoo/blob/12.0/addons/web/controllers/main.py#L961:

-----------

from odoo.addons.web.controllers.main import DataSet

class ExtendDataSet(DataSet):

@route()
def call_kw(self, model, method, args, kwargs, path=None):
print("Insert tracer here")
return super(
ExtendDataSet, self).call_kw(
model, method, args, kwargs, path=path)

-----------

But this will force me to override all controllers I can find, and some custom controllers will obviously go under the radar.

I identified some entry point used by all requests like https://github.com/odoo/odoo/blob/12.0/addons/web/controllers/main.py#L961 or https://github.com/odoo/odoo/blob/12.0/odoo/http.py#L316 but I don't think I have a way to override theses functions without having to rely on the terrible idea to patch the core code.

Anything I missed on how we could execute some code on every request ? On Django you would just use a middleware for such purpose https://docs.djangoproject.com/fr/2.2/topics/http/middleware/ and it does the job perfectly, I feel like this is something which is really missing in Odoo when we have such requirements.

Thanks,
Yannick

by Yannick Buron - 12:20 - 8 Dec 2021

Archives

Contributors

Harald Panten López

Valentín Vinagre Urteaga

Harald Panten López

Harald Panten López

Valentín Vinagre Urteaga

Valentín Vinagre Urteaga

Valentín Vinagre Urteaga

Valentín Vinagre Urteaga