Message Threads | The Odoo Community Association

Modeling general business workflows

Hello,

is anyone aware of any module that would allow for some kind of general workflow? I have a requirement for something the customer calls "Personnel Requisition Request" where hiring manager initiates a request to head of department, then when approved moves to another department for filling in some data, then is set back, ...  This particular case involves hiring but I guess such need is more general.

I can handle approvals with existing tier validation modules. I can build an object to represent the request. Using tasks as request and stages came to my mind. But I have a feeling that there is (could be) fomething to automate the business flow. Any ideas are welcome. Thank you very much.

Best regards

	Radovan Skolnik

by Radovan Skolnik - 04:20 - 18 Mar 2024

5 replies 5 replies

Re: Modeling general business workflows

David,

this is quite intriguing... Probably a bit overkill for this case but can be 
very useful... Thank you.

Best regards

	Radovan

On utorok 19. marca 2024 9:22:20 CET David Beal wrote:

> Maybe there

> https://github.com/acsone/scobidoo [1]

> Bonne journée

> David BEAL  Akretion [2]

> Consultant ERP Odoo

> 

> Le lun. 18 mars 2024 à 20:37, Pedro M. Baeza <

> notifications@odoo-community.org [3] > a écrit : Maybe 

> https://github.com/OCA/automation/pull/1 [4] may serve you. Regards.

> _______________________________________________

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

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

> 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/acsone/scobidoo

> [2] https://akretion.com/fr

> [3] mailto:notifications@odoo-community.org

> [4] https://github.com/OCA/automation/pull/1

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

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

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

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

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

by Radovan Skolnik - 09:40 - 19 Mar 2024

Re: Modeling general business workflows

Maybe there

https://github.com/acsone/scobidoo

Bonne journée

David BEAL
Akretion
Consultant ERP Odoo

Le lun. 18 mars 2024 à 20:37, Pedro M. Baeza <notifications@odoo-community.org> a écrit :
Maybe https://github.com/OCA/automation/pull/1 may serve you.

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 David BEAL - 09:20 - 19 Mar 2024
Re: Modeling general business workflows

Maybe https://github.com/OCA/automation/pull/1 may serve you.

Regards.

by Pedro M. Baeza - 08:34 - 18 Mar 2024

Re: Modeling general business workflows

Hi Adam,

I am very much aware of this but that would mean programming all the logic. I 
was looking for something where I would just configure things.

Best regards,

	Radovan

On pondelok 18. marca 2024 18:31:47 CET Adam Heinz wrote:

> Odoo has some special handling for any model with a field named "state" that

> lends itself towards this sort of effort. You can decorate other fields

> with "states" in Python and XML to pay attention to its value, i.e.

> currency_id = fields.Many2one('res.currency', store=True, readonly=True,

> tracking=True, required=True, states={'draft': [('readonly', False)]},

> string='Currency',

> default=_get_default_currency)

> <button name="action_post" states="draft" icon="fa-check" title="Post"

> type="object" groups="account.group_account_invoice"/> This should allow

> you to drive a user through a mostly linear workflow without too much

> trouble, by showing only actions appropriate to the current state and

> marking fields readonly once they should no longer be changed. On Mon, Mar

> 18, 2024 at 11:22 AM Radovan Skolnik < notifications@odoo-community.org [1]

> > wrote: Hello,

> is anyone aware of any module that would allow for some kind of general

> workflow? I have a requirement for something the customer calls "Personnel

> Requisition Request" where hiring manager initiates a request to head of

> department, then when approved moves to another department for filling in

> some data, then is set back, ... This particular case involves hiring but I

> guess such need is more general. I can handle approvals with existing tier

> validation modules. I can build an object to represent the request. Using

> tasks as request and stages came to my mind. But I have a feeling that

> there is (could be) fomething to automate the business flow. Any ideas are

> welcome. Thank you very much. Best regards

> Radovan Skolnik

> 

> 

> _______________________________________________

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

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

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

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1] mailto:notifications@odoo-community.org

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

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

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

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

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

by Radovan Skolnik - 06:36 - 18 Mar 2024

Re: Modeling general business workflows
Odoo has some special handling for any model with a field named "state" that lends itself towards this sort of effort. You can decorate other fields with "states" in Python and XML to pay attention to its value, i.e.

currency_id = fields.Many2one('res.currency', store=True, readonly=True, tracking=True, required=True,
states={'draft': [('readonly', False)]},
string='Currency',
default=_get_default_currency)

<button name="action_post" states="draft" icon="fa-check" title="Post" type="object" groups="account.group_account_invoice"/>

This should allow you to drive a user through a mostly linear workflow without too much trouble, by showing only actions appropriate to the current state and marking fields readonly once they should no longer be changed.

On Mon, Mar 18, 2024 at 11:22 AM Radovan Skolnik <notifications@odoo-community.org> wrote:
Hello, is anyone aware of any module that would allow for some kind of general workflow? I have a requirement for something the customer calls "Personnel Requisition Request" where hiring manager initiates a request to head of department, then when approved moves to another department for filling in some data, then is set back, ... This particular case involves hiring but I guess such need is more general. I can handle approvals with existing tier validation modules. I can build an object to represent the request. Using tasks as request and stages came to my mind. But I have a feeling that there is (could be) fomething to automate the business flow. Any ideas are welcome. Thank you very much. Best regards Radovan Skolnik

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Adam Heinz - 06:31 - 18 Mar 2024

Social Media Management in Odoo Community

Hi,

does OCA has any repository that allows to manage social media like facebook, linkedin or other media in the way that Odoo Enterprise does with modules like social_facebook, social_linkedin etc?

Thanks,

Francesco Ballerini

by Francesco Ballerini - 10:06 - 18 Mar 2024

3 replies 3 replies

Re: Social Media Management in Odoo Community

Thanks for the quick response and sorry for my late answer.

I agree it would be pretty a nice addition to the https://github.com/OCA/social repo, unfortunately it's not one of our priorities at the moment so we cannot invest time in this kind of development.

To be more precise I have been asked from a co-worker if social media connectors were covered for odoo14 Community but it didn't sound like an urgent request. However, if someone has implemented it privately and wants to share its contact I'll keep you in mind if I will be asked to actually implement social media connectors in our infrastructure as I never implemented something similar and I think it's better for us to buy a connector in this case instead of implement a solution by ourselves.

We are mostly interested in linkedin, instagram and facebook.

Thanks as always for your precious help, regards.

Francesco Ballerini

Il giorno lun 18 mar 2024 alle ore 10:22 Daniel Reis <notifications@odoo-community.org> ha scritto:
I would say oca/social is the best place for those features:
https://github.com/OCA/social

On 18/03/2024 09:07, Francesco Ballerini wrote:

Hi,

does OCA has any repository that allows to manage social media like facebook, linkedin or other media in the way that Odoo Enterprise does with modules like social_facebook, social_linkedin etc?

Thanks,

Francesco Ballerini

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

--

DANIEL REIS
MANAGING PARTNER
Meet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

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

by Francesco Ballerini - 09:51 - 19 Mar 2024
Re: Social Media Management in Odoo Community

I would say oca/social is the best place for those features:
https://github.com/OCA/social

On 18/03/2024 09:07, Francesco Ballerini wrote:

Hi,

does OCA has any repository that allows to manage social media like facebook, linkedin or other media in the way that Odoo Enterprise does with modules like social_facebook, social_linkedin etc?

Thanks,

Francesco Ballerini

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

--

DANIEL REIS
MANAGING PARTNER
Meet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

by Daniel Reis - 10:20 - 18 Mar 2024
Re: Social Media Management in Odoo Community

Not for now. It would be good to expand the community edition that way.

Regards.

by Pedro M. Baeza - 10:11 - 18 Mar 2024

posting journal entry for inter warehouse transfer

Hi,

As you know, odoo by default, will post journal entries from stock move if:

- the stock move goes to or is from a customer location, a supplier location, a production location, and an inventory location.

Would anybody has an idea, how to generate a journal. entry when there is an internal transfer, eg. from one warehouse to another ?

Thanks,

Dominique

by dominique.k - 06:06 - 14 Mar 2024

2 replies 2 replies

Generate reports for international warehouse transfer

Hello,

When transferring products from one WH to another WH in different countries.

I need to provide commercial invoice and proforma.

How do you handle such case?

- Add a button to generate a SO to oneself from the internal transfer.

- Create a route on each line of a SO to oneself.

- Create those report (commercial invoice + proforma) directly on the picking (and avoid the SO creation).

Any insight that can help?

Thank you

--

Yves Goldberg

--

by Yves Goldberg - 04:41 - 12 Mar 2024

4 replies 4 replies

Re: Generate reports for international warehouse transfer

@Daniel & @DIT International, it is the same company indeed that is owning the warehouses (and the inventory).
It works fairly well by creating a self SO and PO but since we don't really need those SO/PO I will propose to go with @Dominique k solution to create those reports directly from the picking object.
Again, thanks & cheers.
Yves.

----- Original message -----
From: Dominique k <notifications@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Re: Generate reports for international warehouse transfer
Date: Thursday, March 14, 2024 19:02

Hi,

I think the simplest way is to customise a picking slp into a pro-forma invoice
you "simply" need to add a price unit (== product price) and a total.

Regards,

Dominique

On Tue, 12 Mar 2024 at 23:42, Yves Goldberg <notifications@odoo-community.org> wrote:
Hello,

When transferring products from one WH to another WH in different countries.
I need to provide commercial invoice and proforma.

How do you handle such case?

- Add a button to generate a SO to oneself from the internal transfer.
- Create a route on each line of a SO to oneself.
- Create those report (commercial invoice + proforma) directly on the picking (and avoid the SO creation).
Any insight that can help?
Thank you
--
Yves Goldberg
--

_______________________________________________
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 Yves Goldberg - 12:41 - 19 Mar 2024
Re: Generate reports for international warehouse transfer

Hi,

I think the simplest way is to customise a picking slp into a pro-forma invoice
you "simply" need to add a price unit (== product price) and a total.

Regards,

Dominique

On Tue, 12 Mar 2024 at 23:42, Yves Goldberg <notifications@odoo-community.org> wrote:
Hello,

When transferring products from one WH to another WH in different countries.
I need to provide commercial invoice and proforma.

How do you handle such case?

- Add a button to generate a SO to oneself from the internal transfer.
- Create a route on each line of a SO to oneself.
- Create those report (commercial invoice + proforma) directly on the picking (and avoid the SO creation).
Any insight that can help?
Thank you
--
Yves Goldberg
--

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

by dominique.k - 06:01 - 14 Mar 2024
Re: Generate reports for international warehouse transfer

Usually the different warehous at different countries under different entities, SO is can not avoid

Yves Goldberg <notifications@odoo-community.org> 于 2024年3月13日周三 02:42写道：
Hello,

When transferring products from one WH to another WH in different countries.
I need to provide commercial invoice and proforma.

How do you handle such case?

- Add a button to generate a SO to oneself from the internal transfer.
- Create a route on each line of a SO to oneself.
- Create those report (commercial invoice + proforma) directly on the picking (and avoid the SO creation).
Any insight that can help?
Thank you
--
Yves Goldberg
--

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

by DIT INTL - 10:46 - 12 Mar 2024
Re: Generate reports for international warehouse transfer

*If* it is not a problem to have different Companies for each country, I would start the process with an SO, and setup multicompany to automatically generate the corresponding PO in the destination country.
You then have a profirma, Delivery and Invoice; and a Reception on the destination WH, with the out of the box routes.

If it has to be a single company two Warehouses it is trickier.
The SO gives you a proforma, but I'm not seeing how you can actually invoice yourself...

/Daniel

On 12/03/2024 15:42, Yves Goldberg wrote:

Hello,

When transferring products from one WH to another WH in different countries.

I need to provide commercial invoice and proforma.

How do you handle such case?

- Add a button to generate a SO to oneself from the internal transfer.

- Create a route on each line of a SO to oneself.

- Create those report (commercial invoice + proforma) directly on the picking (and avoid the SO creation).

Any insight that can help?

Thank you

--

Yves Goldberg

--

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

--

DANIEL REIS
MANAGING PARTNER
Meet with me.
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office Center, 2649-517 Cascais

by Daniel Reis - 08:04 - 12 Mar 2024

Expert-comptable FR

Bonjour la communauté Odoo,

Nous sommes à la recherche d'un expert-comptable (Free-lance/indépendant) français qui maîtrise Odoo.

A dispo pour plus de renseignements,

Sandrine Brassel

Sandrine BRASSEL

Partner

4 rue du Fort Wallis L-2714 Luxembourg

DISCLAIMER: This email and any attachments are confidential and intended solely for the use of the addressee. You should not copy or disclose its contents to any other person. If you have received this email in error please notify the sender immediately. Replies to this email may be monitored.

by sbrassel - 12:46 - 11 Mar 2024

1 replies 1 replies

Receiving in the Purchase UoM

Hello, maybe some of you came across this need:

I keep my Glycerine stock in Kg.
My supplier sells it in Liters.
I know that the density of Glycerine is 1.26, so 1 Liter = 1.26 Kg.

I would like to:
1. Send a Purchase Order for 100 Liters.
2. Receive from the Supplier the 100 Liters delivered.
3. View my stock as 126 Kg.

Setting a Purchase UoM works for 1. and 3., but does not work for 2.
Using Packagings does not work either.

Any advice?

Thank you

--

DANIEL REIS
MANAGING PARTNER

M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais

by Daniel Reis - 04:25 - 9 Mar 2024

4 replies 4 replies

Re: Receiving in the Purchase UoM

Hi Stefano,

I could but currently don't have time (esp. to create tests). So here's the contents of what I did if you wanted to go and create PR yourself. It allows you to either ent factor or factor_inv and the other gets recomputed:

from odoo import _, api, fields, models
from odoo.exceptions import ValidationError

class ProductSecondaryUnit(models.Model):
   _inherit = "product.secondary.unit"
   factor_inv = fields.Float(
       "Secondary Unit Factor Inv.",
       compute="_compute_factor_inv",
       inverse="_set_factor_inv",
   )
   @api.depends("factor")
   def _compute_factor_inv(self):
       for unit in self:
           if unit.factor == 0:
               raise ValidationError(_("The value of factor could not be Zero"))
           else:
               unit.factor_inv = 1 / unit.factor
   def _set_factor_inv(self):
       for unit in self:
           if unit.factor_inv == 0:
               raise ValidationError(
                   _("The value of inversed factor could not be Zero")
               )
           else:
               unit.factor = 1 / unit.factor_inv

And you just add the factor_inv into view:

   <record id="product_template_form_view" model="ir.ui.view">
       <field name="name">Product template Secondary Unit</field>
       <field name="model">product.template</field>
       <field name="inherit_id" ref="product.product_template_form_view" />
       <field name="arch" type="xml">
           <xpath expr="//field[@name='secondary_uom_ids']/tree/field[@name='uom_id']" position="before">
               <field name="factor_inv"/>
           </xpath>
       </field>
   </record>

Best regards

    Radovan

On pondelok 11. marca 2024 8:26:54 CET Stefano Consolaro wrote:

> Hi Radovan, do you think that the "small module" for product_secondary_unit

> can be refactored as a configuration options? If so, can you do a PR fot

> it? Thanks Stefano

> Da "Radovan Skolnik" notifications@odoo-community.org

> A "Contributors" contributors@odoo-community.org

> Cc

> Data Sat, 09 Mar 2024 15:38:21 -0000

> Oggetto Re: Receiving in the Purchase UoM

>

> Hi,

>

> I was dealing with this just recently. What works (although it's not 100%

> what yo want) is using those 2 modules:

>

> product_secondary_unit - allows you to add secondary UoM(s) with their

> factor - i.e. you add secondary UoM of kg with conversion factor of 1/1.26

> (this seems a bit awkward but it's inverted - I have created a small module

> to be able to add inverse factor of 1.26 and ocmpute the original factor)

> stock_secondary_unit - this basically allows you to choose one of the

> product's secondary UoM to show (besides qty in original UoM) qty on hand

> as well as in stock moves. Actually in stock moves it does not work - see

> https://github.com/OCA/stock-logistics-warehouse/pull/1769 [1] for my

> proposal to fix it.

>

> Best regards

>

> Radovan

>

> On sobota 9. marca 2024 16:27:22 CET Daniel Reis wrote:

> > Hello, maybe some of you came across this need:

> > I keep my Glycerine stock in Kg.

> > My supplier sells it in Liters.

> > I know that the density of Glycerine is 1.26, so 1 Liter = 1.26 Kg.

> > I would like to:

> > 1. Send a Purchase Order for 100 Liters.

> > 2. Receive from the Supplier the 100 Liters delivered.

> > 3. View my stock as 126 Kg.

> > Setting a Purchase UoM works for 1. and 3., but does not work for 2.

> > Using Packagings does not work either.

> > Any advice?

> >

> > Thank you

> > --

> > DANIEL

> > REIS*

> > MANAGING PARTNER

> > M:*

> > +351 919 991 307

> > E:*

> > dreis@OpenSourceIntegrators.com [1]

> > A:*

> > Avenida da República 3000, Estoril Office B, 3º Escr.34,

> > 2649-517 Cascais

> >

> >

> >

> >

> > _______________________________________________

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

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

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

> >

> >

> >

> > [1] mailto:dreis@OpenSourceIntegrators.com

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

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

>

> _______________________________________________

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

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

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

>

>

>

> Stefano Consolaro

> www.mymage.it

>

> _______________________________________________

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

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

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

>

>

>

> [1] https://github.com/OCA/stock-logistics-warehouse/pull/1769

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

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

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

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

by Radovan Skolnik - 11:56 - 11 Mar 2024
Re: Receiving in the Purchase UoM
Hi Radovan,
do you think that the "small module" for product_secondary_unit can be refactored as a configuration options?
If so, can you do a PR fot it?

Thanks
Stefano

Da "Radovan Skolnik" notifications@odoo-community.org

A "Contributors" contributors@odoo-community.org

Cc

Data Sat, 09 Mar 2024 15:38:21 -0000

Oggetto Re: Receiving in the Purchase UoM

Hi,

I was dealing with this just recently. What works (although it's not 100% what yo want) is using those 2 modules:

product_secondary_unit - allows you to add secondary UoM(s) with their factor - i.e. you add secondary UoM of kg with conversion factor of 1/1.26 (this seems a bit awkward but it's inverted - I have created a small module to be able to add inverse factor of 1.26 and ocmpute the original factor)

stock_secondary_unit - this basically allows you to choose one of the product's secondary UoM to show (besides qty in original UoM) qty on hand as well as in stock moves. Actually in stock moves it does not work - see https://github.com/OCA/stock-logistics-warehouse/pull/1769 for my proposal to fix it.

Best regards

Radovan

On sobota 9. marca 2024 16:27:22 CET Daniel Reis wrote:

> Hello, maybe some of you came across this need:

> I keep my Glycerine stock in Kg.

> My supplier sells it in Liters.

> I know that the density of Glycerine is 1.26, so 1 Liter = 1.26 Kg.

> I would like to:

> 1. Send a Purchase Order for 100 Liters.

> 2. Receive from the Supplier the 100 Liters delivered.

> 3. View my stock as 126 Kg.

> Setting a Purchase UoM works for 1. and 3., but does not work for 2.

> Using Packagings does not work either.

> Any advice?

>

> Thank you

> --

> DANIEL

> REIS*

> MANAGING PARTNER

> M:*

> +351 919 991 307

> E:*

> dreis@OpenSourceIntegrators.com [1]

> A:*

> Avenida da República 3000, Estoril Office B, 3º Escr.34,

> 2649-517 Cascais

>

>

>

>

> _______________________________________________

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

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

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

>

>

>

> [1] mailto:dreis@OpenSourceIntegrators.com

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

> [3] 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

Stefano Consolaro
www.mymage.it
by Stefano Consolaro - 08:26 - 11 Mar 2024
Re: Receiving in the Purchase UoM

Hi Daniel,

I created a module that I think does exactly what you want (or at least quite close), using some OCA modules as product_secondary_unit and purchase_secondary_unit.

So definitely, you need custom code for that purpose.

Regards
Jorge Ayala
Biwise
+525517927019

El 9 mar 2024 9:27 a. m., Daniel Reis <notifications@odoo-community.org> escribió:
Hello, maybe some of you came across this need:

I keep my Glycerine stock in Kg.
My supplier sells it in Liters.
I know that the density of Glycerine is 1.26, so 1 Liter = 1.26 Kg.

I would like to:
1. Send a Purchase Order for 100 Liters.
2. Receive from the Supplier the 100 Liters delivered.
3. View my stock as 126 Kg.

Setting a Purchase UoM works for 1. and 3., but does not work for 2.
Using Packagings does not work either.

Any advice?

Thank you

--

DANIEL REIS
MANAGING PARTNER
M: +351 919 991 307
E: dreis@OpenSourceIntegrators.com
A: Avenida da República 3000, Estoril Office B, 3º Escr.34, 2649-517 Cascais

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

by jorge.ayala - 05:51 - 9 Mar 2024
Re: Receiving in the Purchase UoM
Hi,

I was dealing with this just recently. What works (although it's not 100% what yo want) is using those 2 modules:

product_secondary_unit - allows you to add secondary UoM(s) with their factor - i.e. you add secondary UoM of kg with conversion factor of 1/1.26 (this seems a bit awkward but it's inverted - I have created a small module to be able to add inverse factor of 1.26 and ocmpute the original factor)

stock_secondary_unit - this basically allows you to choose one of the product's secondary UoM to show (besides qty in original UoM) qty on hand as well as in stock moves. Actually in stock moves it does not work - see https://github.com/OCA/stock-logistics-warehouse/pull/1769 for my proposal to fix it.

Best regards

Radovan

On sobota 9. marca 2024 16:27:22 CET Daniel Reis wrote:

> Hello, maybe some of you came across this need:

> I keep my Glycerine stock in Kg.

> My supplier sells it in Liters.

> I know that the density of Glycerine is 1.26, so 1 Liter = 1.26 Kg.

> I would like to:

> 1. Send a Purchase Order for 100 Liters.

> 2. Receive from the Supplier the 100 Liters delivered.

> 3. View my stock as 126 Kg.

> Setting a Purchase UoM works for 1. and 3., but does not work for 2.

> Using Packagings does not work either.

> Any advice?

>

> Thank you

> --

> DANIEL

> REIS*

> MANAGING PARTNER

> M:*

> +351 919 991 307

> E:*

> dreis@OpenSourceIntegrators.com [1]

> A:*

> Avenida da República 3000, Estoril Office B, 3º Escr.34,

> 2649-517 Cascais

>

>

>

>

> _______________________________________________

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

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

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

>

>

>

> [1] mailto:dreis@OpenSourceIntegrators.com

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

> [3] https://odoo-community.org/groups?unsubscribe
by Radovan Skolnik - 04:36 - 9 Mar 2024

Proposing myself as CRM/Sales/Marketing PSC member

Dear community,

My area of expertise is CRM/Sales/Marketing is limited to several modules, yet I can top it up by my other PSC membership for other repos.

Kind regards,
Alexey

by Alexey Pelykh - 03:25 - 8 Mar 2024

6 replies 6 replies

How do I copy a websitebuilder block in a theme

Hi friends in odoo

I would like to duplicate and edit a website builder block in odoo V17.

I was of the impression, that I saw that this is possible in a website builder 
tutorial, but I can not
find that tutorial again, and neither a way to do it in the website builder.


Thanks a lot for your help
and all the best

Robert

by robert - 05:06 - 4 Mar 2024

1 replies 1 replies

ERROR: could not serialize access due to concurrent update (case using Job Queue)

Dear community,

We have a case that needs to process a lot of transactions (500k arrive on the last day of month). And so we rely on our best friend OCA's Job Queue and have things run in parallel.

Most process are OK, but the one creates stock picking, jobs can't run in parallel because there is a concurrent issue on the "stock_quant" table, which looks like many separated job is updating the same record.

bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)

ERROR: could not serialize access due to concurrent update

bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)

ERROR: could not serialize access due to concurrent update

.....

Concurrent updates are very common issues we always face. How do you get around with this problem?

Thank you,

Kitti U.

by Kitti Upariphutthiphong - 02:16 - 4 Mar 2024

6 replies 6 replies

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Thanks everyone!

Reservation Method = Manual, sounds like a valid solution. We will test and report the result.

On Mon, Mar 4, 2024 at 9:32 PM Pedro M. Baeza <notifications@odoo-community.org> wrote:
If talking about picking generation, I wouldn't do reserve at that time, and do a general "reserve round" at the end of the batch, and thus, you remove the quant lock constraint.

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 Kitti Upariphutthiphong - 05:00 - 4 Mar 2024
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

If talking about picking generation, I wouldn't do reserve at that time, and do a general "reserve round" at the end of the batch, and thus, you remove the quant lock constraint.

Regards.

by Pedro M. Baeza - 03:31 - 4 Mar 2024

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

On 3/4/24 15:07, Kitti Upariphutthiphong wrote:

>

> I was thinking if there are anyway to unlock the table at least 

> temporarily during execution. But as far as I researching, I still 

> can't find the way.

I don't think "temporary unlock" is possible, or advisable, but another 
way is to lock the table as late as possible, so, closest before 
commit() of your transaction. That way, the time that your lock persists 
is smallest and the chance for conflict is lowest (the lower you get it, 
the more viable it will be to just rely on RetryableJobError for the 
small amount of cases where a conflict arises).

A strategy for this can be to do the thing that locks, and right after 
that, fire a new queue job that will do the rest of the stuff.

We've had success with this in cases whereby you have for example:

Process payment transaction job:

1. Start database transaction
2. Create payment transaction
3. Confirm sale.order, which may generate a stock.picking and confirm 
it, thereby locking quant table
4. Generate invoice (during this time some rows in quant table will 
still be locked, conflicts can occur)
5. Send out invoice by mail (during this time some rows in quant table 
will still be locked, conflicts can occur)
6. End of database transaction (commit)

Instead, you will add "with_delay()" around steps 4+5 so that these are 
run in a separate queue job, for which the locking does not apply.

Of course this requires refactoring of core or custom code so it might 
not be a viable solution in your case.

by Tom Blauwendraat - 03:26 - 4 Mar 2024

Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Hello,

Your problem seems to be linked to stock reservation. By default, picking types (Operation types) are configured to make the stock reservation at picking confirmation. If this is the case, these concurrent update errors are not surprising if the created pickings contain the same product.
You could try to change the "Reservation Method" on the concerned picking type(s) to "manual". And then manage the stock reservation on picking one by one afterward.

Regards,
Florian

Le lun. 4 mars 2024 à 15:07, Kitti Upariphutthiphong <notifications@odoo-community.org> a écrit :
Thanks Adam,

In fact, if we don't have time constraints, it will work.

The problem is we really need to have many job (like 10 processes that create picking) to run simultaneously and without locking in order to achieve 500k records (more in the future) in very limit time (couple hours).

I was thinking if there are anyway to unlock the table at least temporarily during execution. But as far as I researching, I still can't find the way yet.

On Mon, Mar 4, 2024 at 8:37 PM Adam Heinz <notifications@odoo-community.org> wrote:
I have a couple of strategies that I use, neither of which I am in love with:

1. Catch the serialization error and reraise a RetryableJobError. This works well enough when serialization errors are intermittent and the job has no side-effects.
2. Set ODOO_QUEUE_JOB_CHANNELS=root:32,single:1 in the environment, and put problematic jobs into the `single` channel. This is a tool of last resort as it slows problematic jobs down to single threaded, but I have found it necessary when the serialization errors occur on basically every execution.

On Mon, Mar 4, 2024 at 8:17 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
Dear community,

We have a case that needs to process a lot of transactions (500k arrive on the last day of month). And so we rely on our best friend OCA's Job Queue and have things run in parallel.

Most process are OK, but the one creates stock picking, jobs can't run in parallel because there is a concurrent issue on the "stock_quant" table, which looks like many separated job is updating the same record.

bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
.....

Concurrent updates are very common issues we always face. How do you get around with this problem?

Thank you,
Kitti U.

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

_______________________________________________
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 Florian da Costa - 03:15 - 4 Mar 2024
Re: ERROR: could not serialize access due to concurrent update (case using Job Queue)

Thanks Adam,

In fact, if we don't have time constraints, it will work.

The problem is we really need to have many job (like 10 processes that create picking) to run simultaneously and without locking in order to achieve 500k records (more in the future) in very limit time (couple hours).

I was thinking if there are anyway to unlock the table at least temporarily during execution. But as far as I researching, I still can't find the way yet.

On Mon, Mar 4, 2024 at 8:37 PM Adam Heinz <notifications@odoo-community.org> wrote:
I have a couple of strategies that I use, neither of which I am in love with:

1. Catch the serialization error and reraise a RetryableJobError. This works well enough when serialization errors are intermittent and the job has no side-effects.
2. Set ODOO_QUEUE_JOB_CHANNELS=root:32,single:1 in the environment, and put problematic jobs into the `single` channel. This is a tool of last resort as it slows problematic jobs down to single threaded, but I have found it necessary when the serialization errors occur on basically every execution.

On Mon, Mar 4, 2024 at 8:17 AM Kitti Upariphutthiphong <notifications@odoo-community.org> wrote:
Dear community,

We have a case that needs to process a lot of transactions (500k arrive on the last day of month). And so we rely on our best friend OCA's Job Queue and have things run in parallel.

Most process are OK, but the one creates stock picking, jobs can't run in parallel because there is a concurrent issue on the "stock_quant" table, which looks like many separated job is updating the same record.

bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
bad query: update stock_quant set reserved_quantity = 10.00 ... where id in (100)
ERROR: could not serialize access due to concurrent update
.....

Concurrent updates are very common issues we always face. How do you get around with this problem?

Thank you,
Kitti U.

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

_______________________________________________
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 - 03:05 - 4 Mar 2024

Product qty constraints for services

Fellow contributors,

I'm looking for a module - prior to jumping onto a train of making one - that would allow setting min/max/multiplier for products that are services.
In v14, it could've been accomplished by sale_by_packaging module, yet as it was refactored in v16 this unintended feature is no longer available for services.

My justification for possibly making a new module only for qty constraints is as follows: services like support or consulting can also be sold in packs of 5 hours.
Yet that has nothing to do with inventory or stock.

Yet it feels like such thing has already been implemented somewhere - I just can't find the place.

Is there a known module that does that?
Are there any objections making the module?

Kind regards,
Alexey

by Alexey Pelykh - 08:10 - 4 Mar 2024

6 replies 6 replies

Re: Product qty constraints for services

Absolutely, just my preference :)

On 5 Mar 2024, at 08:52, Radovan Skolnik <notifications@odoo-community.org> wrote:

Hi,

glad I could help. One small note: you do not have to port through all 
versions to get to 17.0 You can port directly from 14.0 to 17.0 if you wanted.

Best regards

	Radovan

On utorok 5. marca 2024 7:57:27 CET Alexey Pelykh wrote:

> Hi Radovan,

> Indeed! It seems like this module could use some maintenance and some UX

> improvement, it does the job. 

> https://github.com/OCA/sale-workflow/pull/2991 [1] 

> https://github.com/OCA/sale-workflow/pull/2992 [2] My plan is to port it

> all the way to v17 and do the UX suggestions there. Kind regards, Alexey

> On 4 Mar 2024, at 16:37, Radovan Skolnik <notifications@odoo-community.org>

> wrote: Hi,

> what about this one:

> https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty [3]  ?

> There is PR for 16.0: https://github.com/OCA/sale-workflow/pull/2757 [4] 

> In cobination with UoM of 10 I think it could work. Best regards

> Radovan

> On pondelok 4. marca 2024 12:53:01 CET Alexey Pelykh wrote: > Hi Radovan, >

> In my specific case it's "min 500 with increase of 100", so UoM won't

> really > do the thing. Yep, I've been following your question - apparently,

> there's > nothing in existence? Kind regards, Alexey > On 4 Mar 2024, at

> 11:07, Radovan Skolnik <notifications@odoo-community.org> > wrote: Hi, >

> would not a "5-pack" UoM (i.e. 5 units of 1 working hour) solve this? You >

> would be selling by these so you'd always end up with multiplies of 5... >

> I was just recently asking something very similar but on the purchase side

> > of things... > Best regards > Radovan Skolnik >  > On pondelok 4. marca

> 2024 8:12:14 CET Alexey Pelykh wrote: > > Fellow contributors, > > I'm

> looking for a module - prior to jumping onto a train of making one - > >

> that would allow setting min/max/multiplier for products that are > >

> services. > > In v14, it could've been accomplished by sale_by_packaging

> module, yet as > > it was refactored in v16 this unintended feature is no

> longer available > > for > > services. My justification for possibly making

> a new module only for qty > > constraints is as follows: services like

> support or consulting can also be > > sold in packs of 5 hours. Yet that

> has nothing to do with inventory or > > stock. > > Yet it feels like such

> thing has already been implemented somewhere - I > > just can't find the

> place. Is there a known module that does that? > > Are there any objections

> making the module? > > Kind regards, > > Alexey > >

> _______________________________________________ > > 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 [1] > Post to:

> mailto:contributors@odoo-community.org > Unsubscribe:

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

> _______________________________________________ > Mailing-List:

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

> mailto:contributors@odoo-community.org > Unsubscribe:

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

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

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

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

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

> 

> 

> _______________________________________________

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

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

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

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1] https://github.com/OCA/sale-workflow/pull/2991

> [2] https://github.com/OCA/sale-workflow/pull/2992

> [3] https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty

> [4] https://github.com/OCA/sale-workflow/pull/2757

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

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

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

> [8] 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 Alexey Pelykh - 08:56 - 5 Mar 2024

Re: Product qty constraints for services

Hi,

glad I could help. One small note: you do not have to port through all 
versions to get to 17.0 You can port directly from 14.0 to 17.0 if you wanted.

Best regards

	Radovan

On utorok 5. marca 2024 7:57:27 CET Alexey Pelykh wrote:

> Hi Radovan,

> Indeed! It seems like this module could use some maintenance and some UX

> improvement, it does the job. 

> https://github.com/OCA/sale-workflow/pull/2991 [1] 

> https://github.com/OCA/sale-workflow/pull/2992 [2] My plan is to port it

> all the way to v17 and do the UX suggestions there. Kind regards, Alexey

> On 4 Mar 2024, at 16:37, Radovan Skolnik <notifications@odoo-community.org>

> wrote: Hi,

> what about this one:

> https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty [3]  ?

> There is PR for 16.0: https://github.com/OCA/sale-workflow/pull/2757 [4] 

> In cobination with UoM of 10 I think it could work. Best regards

> Radovan

> On pondelok 4. marca 2024 12:53:01 CET Alexey Pelykh wrote: > Hi Radovan, >

> In my specific case it's "min 500 with increase of 100", so UoM won't

> really > do the thing. Yep, I've been following your question - apparently,

> there's > nothing in existence? Kind regards, Alexey > On 4 Mar 2024, at

> 11:07, Radovan Skolnik <notifications@odoo-community.org> > wrote: Hi, >

> would not a "5-pack" UoM (i.e. 5 units of 1 working hour) solve this? You >

> would be selling by these so you'd always end up with multiplies of 5... >

> I was just recently asking something very similar but on the purchase side

> > of things... > Best regards > Radovan Skolnik >  > On pondelok 4. marca

> 2024 8:12:14 CET Alexey Pelykh wrote: > > Fellow contributors, > > I'm

> looking for a module - prior to jumping onto a train of making one - > >

> that would allow setting min/max/multiplier for products that are > >

> services. > > In v14, it could've been accomplished by sale_by_packaging

> module, yet as > > it was refactored in v16 this unintended feature is no

> longer available > > for > > services. My justification for possibly making

> a new module only for qty > > constraints is as follows: services like

> support or consulting can also be > > sold in packs of 5 hours. Yet that

> has nothing to do with inventory or > > stock. > > Yet it feels like such

> thing has already been implemented somewhere - I > > just can't find the

> place. Is there a known module that does that? > > Are there any objections

> making the module? > > Kind regards, > > Alexey > >

> _______________________________________________ > > 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 [1] > Post to:

> mailto:contributors@odoo-community.org > Unsubscribe:

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

> _______________________________________________ > Mailing-List:

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

> mailto:contributors@odoo-community.org > Unsubscribe:

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

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

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

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

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

> 

> 

> _______________________________________________

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

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

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

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1] https://github.com/OCA/sale-workflow/pull/2991

> [2] https://github.com/OCA/sale-workflow/pull/2992

> [3] https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty

> [4] https://github.com/OCA/sale-workflow/pull/2757

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

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

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

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

by Radovan Skolnik - 08:50 - 5 Mar 2024

Re: Product qty constraints for services

Hi Radovan,

Indeed! It seems like this module could use some maintenance and some UX improvement, it does the job.
https://github.com/OCA/sale-workflow/pull/2991
https://github.com/OCA/sale-workflow/pull/2992

My plan is to port it all the way to v17 and do the UX suggestions there.

Kind regards,
Alexey

On 4 Mar 2024, at 16:37, Radovan Skolnik <notifications@odoo-community.org> wrote:

Hi,

what about this one: https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty ? There is PR for 16.0: https://github.com/OCA/sale-workflow/pull/2757
In cobination with UoM of 10 I think it could work.

Best regards

Radovan

On pondelok 4. marca 2024 12:53:01 CET Alexey Pelykh wrote:
> Hi Radovan,
> In my specific case it's "min 500 with increase of 100", so UoM won't really
> do the thing. Yep, I've been following your question - apparently, there's
> nothing in existence? Kind regards, Alexey
> On 4 Mar 2024, at 11:07, Radovan Skolnik <notifications@odoo-community.org>
> wrote: Hi,
> would not a "5-pack" UoM (i.e. 5 units of 1 working hour) solve this? You
> would be selling by these so you'd always end up with multiplies of 5...
> I was just recently asking something very similar but on the purchase side
> of things...
> Best regards
> Radovan Skolnik
>
> On pondelok 4. marca 2024 8:12:14 CET Alexey Pelykh wrote:
> > Fellow contributors,
> > I'm looking for a module - prior to jumping onto a train of making one -
> > that would allow setting min/max/multiplier for products that are
> > services.
> > In v14, it could've been accomplished by sale_by_packaging module, yet as
> > it was refactored in v16 this unintended feature is no longer available
> > for
> > services. My justification for possibly making a new module only for qty
> > constraints is as follows: services like support or consulting can also be
> > sold in packs of 5 hours. Yet that has nothing to do with inventory or
> > stock.
> > Yet it feels like such thing has already been implemented somewhere - I
> > just can't find the place. Is there a known module that does that?
> > Are there any objections making the module?
> > Kind regards,
> > Alexey
> > _______________________________________________
> > 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 [1]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [2]
>
>
> _______________________________________________
> Mailing-List: https://odoo-community.org/groups/contributors-15 [3]
> Post to: mailto:contributors@odoo-community.org
> Unsubscribe: https://odoo-community.org/groups?unsubscribe [4]
>
>
>
> [1] https://odoo-community.org/groups/contributors-15
> [2] https://odoo-community.org/groups?unsubscribe
> [3] https://odoo-community.org/groups/contributors-15
> [4] 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 Alexey Pelykh - 07:56 - 5 Mar 2024
Re: Product qty constraints for services

Hi,

what about this one: https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty ? There is PR for 16.0: https://github.com/OCA/sale-workflow/pull/2757

In cobination with UoM of 10 I think it could work.

Best regards

Radovan

On pondelok 4. marca 2024 12:53:01 CET Alexey Pelykh wrote:

> Hi Radovan,

> In my specific case it's "min 500 with increase of 100", so UoM won't really

> do the thing. Yep, I've been following your question - apparently, there's

> nothing in existence? Kind regards, Alexey

> On 4 Mar 2024, at 11:07, Radovan Skolnik <notifications@odoo-community.org>

> wrote: Hi,

> would not a "5-pack" UoM (i.e. 5 units of 1 working hour) solve this? You

> would be selling by these so you'd always end up with multiplies of 5...

> I was just recently asking something very similar but on the purchase side

> of things...

> Best regards

> Radovan Skolnik

>

> On pondelok 4. marca 2024 8:12:14 CET Alexey Pelykh wrote:

> > Fellow contributors,

> > I'm looking for a module - prior to jumping onto a train of making one -

> > that would allow setting min/max/multiplier for products that are

> > services.

> > In v14, it could've been accomplished by sale_by_packaging module, yet as

> > it was refactored in v16 this unintended feature is no longer available

> > for

> > services. My justification for possibly making a new module only for qty

> > constraints is as follows: services like support or consulting can also be

> > sold in packs of 5 hours. Yet that has nothing to do with inventory or

> > stock.

> > Yet it feels like such thing has already been implemented somewhere - I

> > just can't find the place. Is there a known module that does that?

> > Are there any objections making the module?

> > Kind regards,

> > Alexey

> > _______________________________________________

> > 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 [1]

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

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

>

>

> _______________________________________________

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

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

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

>

>

>

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

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

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

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

by Radovan Skolnik - 04:36 - 4 Mar 2024

Re: Product qty constraints for services

Hi Radovan,

In my specific case it's "min 500 with increase of 100", so UoM won't really do the thing.

Yep, I've been following your question - apparently, there's nothing in existence?

Kind regards,

Alexey

On 4 Mar 2024, at 11:07, Radovan Skolnik <notifications@odoo-community.org> wrote:

Hi,

would not a "5-pack" UoM (i.e. 5 units of 1 working hour) solve this? You 
would be selling by these so you'd always end up with multiplies of 5...

I was just recently asking something very similar but on the purchase side of 
things...

Best regards

	Radovan Skolnik

On pondelok 4. marca 2024 8:12:14 CET Alexey Pelykh wrote:

> Fellow contributors,

> I'm looking for a module - prior to jumping onto a train of making one -

> that would allow setting min/max/multiplier for products that are services.

> In v14, it could've been accomplished by sale_by_packaging module, yet as

> it was refactored in v16 this unintended feature is no longer available for

> services. My justification for possibly making a new module only for qty

> constraints is as follows: services like support or consulting can also be

> sold in packs of 5 hours. Yet that has nothing to do with inventory or

> stock.

> Yet it feels like such thing has already been implemented somewhere - I just

> can't find the place. Is there a known module that does that?

> Are there any objections making the module?

> Kind regards,

> Alexey

> _______________________________________________

> 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 Alexey Pelykh - 12:51 - 4 Mar 2024

Making a redirect from "/" to "/shop" is bad idea for indexing Odoo website?

Hello,

I am trying to build an e-Commerce with odoo14 and I have noticed that home route is an empty page. Basically everything I need in the home is already in the "/shop" page. Main template that I need are

- product grid

- e-Commerce categories

- featured products (introduced with 3rd party module)

- new arrivals (introduced with 3rd party module)

It would be a pain to bring all these into a new route (home route) and it would be so much reasonable to just make a redirect from "/" to "/shop".

My issue is that my knowledge of "indexing" is basically non-existent, so I'm not aware of the consequences, it's hard for me to formulate a specific question about this topic so I'm just going to ask, in general: the "redirect approach" would be a BAD approach considering the way Odoo is designed ?

In case it is not the right approach would you be so kind to suggest me a better possible solution to bring all template and controllers that I need from "/shop" to "/" ?

I ask this mainly because have been told that generally keeping your home on "/" will improve the indexing, but I am not sure if that also applies to the Odoo structure.

Will really appreciate your feedbacks

Thank you

--

Francesco Ballerini

Privo di virus.www.avast.com

by Francesco Ballerini - 02:31 - 3 Mar 2024

4 replies 4 replies

Re: Making a redirect from "/" to "/shop" is bad idea for indexing Odoo website?

Le 4 mars 2024 14:42:23 GMT+01:00, Francesco Ballerini <notifications@odoo-community.org> a écrit :

>Hi Xavier,

>thanks for this valuable feedback!

>I wasn't aware of SEO redirection module, it as I generally watch in 14.0, sometimes on 12.0 repositories, I see the module it's stuck on v10 but good to know that something like this exists.

>We are currently supporting our website with another infrastructure and planning to switch to Odoo soon. About the analytics, from what I have been told a consistent amount of our customers search specific products by submitting the internal reference of the product in the search box and our current "Home" isn't too different compared to the /shop page served by Odoo standard + OCA with the addition of a bunch of modules.

>I generally like to design new widgets and templates, in this specific case though I think I will follow your first advice and map the /shop into the domain, or similar solution, really good to know it's not relevant for SEO.

>Thank you very much -- Francesco Ballerini

Hi
I can't check, but i am quite sure that the OCA module is available also in v14.

by xavier - 12:36 - 5 Mar 2024

Re: Making a redirect from "/" to "/shop" is bad idea for indexing Odoo website?

Hi Xavier,

thanks for this valuable feedback!

I wasn't aware of SEO redirection module, it as I generally watch in 14.0, sometimes on 12.0 repositories, I see the module it's stuck on v10 but good to know that something like this exists.

We are currently supporting our website with another infrastructure and planning to switch to Odoo soon. About the analytics, from what I have been told a consistent amount of our customers search specific products by submitting the internal reference of the product in the search box and our current "Home" isn't too different compared to the /shop page served by Odoo standard + OCA with the addition of a bunch of modules.

I generally like to design new widgets and templates, in this specific case though I think I will follow your first advice and map the /shop into the domain, or similar solution, really good to know it's not relevant for SEO.

Thank you very much

--

Francesco Ballerini

Il giorno lun 4 mar 2024 alle ore 12:15 Xavier <notifications@odoo-community.org> ha scritto:

Le 3 mars 2024 14:32:19 GMT+01:00, Francesco Ballerini <notifications@odoo-community.org> a écrit :


>Hello,


>


>I am trying to build an e-Commerce with odoo14 and I have noticed that home route is an empty page. Basically everything I need in the home is already in the "/shop" page. Main template that I need are


>


>- product grid


>- e-Commerce categories


>- featured products (introduced with 3rd party module)


>- new arrivals  (introduced with 3rd party module)


>


>It would be a pain to bring all these into a new route (home route) and it would be so much reasonable to just make a redirect from "/" to "/shop".


>


>My issue is that my knowledge of "indexing" is basically non-existent, so I'm not aware of the consequences, it's hard for me to formulate a specific question about this topic so I'm just going to ask, in general: the "redirect approach"  would be a BAD approach considering the way Odoo is designed ?


>


>In case it is not the right approach would you be so kind to suggest me a better possible solution to bring all template and controllers that I need from "/shop" to "/" ?


>


>I ask this mainly because have been told that *generally *keeping your home on "/" will improve the indexing, but I am not sure if that also applies to the Odoo structure.


>


>Will really appreciate your feedbacks


>Thank you


>--


>


>Francesco Ballerini


>


>


>


>


>None [1]  Privo di virus. www.avast.com [2]   None [3]


>_______________________________________________


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


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


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


>


>


>


>[1] https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail


>[2] https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail


>[3] #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2


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


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

Hi
The obvious way is by setting your home url in the web server (domain.tld/shop). You can also use an OCA module "website SEO redirection" that let you redirect any url.

But you may find more interesting to keep your home as is and add some useful widgets like featured products, new products, products more often buy, sales, etc. Regarding categories the mega menu will do the same.

In any case, this is not bad for SEO.

Anyway, don't forget to keep an eye on your website analytics. Because most visitors comes directly on a product page. So this question about home or shop is mostly irelevant.

Hope this help
Xavier

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

by Francesco Ballerini - 02:41 - 4 Mar 2024

Re: Making a redirect from "/" to "/shop" is bad idea for indexing Odoo website?

Le 3 mars 2024 14:32:19 GMT+01:00, Francesco Ballerini <notifications@odoo-community.org> a écrit :

>Hello,

>

>I am trying to build an e-Commerce with odoo14 and I have noticed that home route is an empty page. Basically everything I need in the home is already in the "/shop" page. Main template that I need are

>

>- product grid

>- e-Commerce categories

>- featured products (introduced with 3rd party module)

>- new arrivals  (introduced with 3rd party module)

>

>It would be a pain to bring all these into a new route (home route) and it would be so much reasonable to just make a redirect from "/" to "/shop".

>

>My issue is that my knowledge of "indexing" is basically non-existent, so I'm not aware of the consequences, it's hard for me to formulate a specific question about this topic so I'm just going to ask, in general: the "redirect approach"  would be a BAD approach considering the way Odoo is designed ?

>

>In case it is not the right approach would you be so kind to suggest me a better possible solution to bring all template and controllers that I need from "/shop" to "/" ?

>

>I ask this mainly because have been told that *generally *keeping your home on "/" will improve the indexing, but I am not sure if that also applies to the Odoo structure.

>

>Will really appreciate your feedbacks

>Thank you

>--

>

>Francesco Ballerini

>

>

>

>

>None [1]  Privo di virus. www.avast.com [2]   None [3]

>_______________________________________________

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

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

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

>

>

>

>[1] https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

>[2] https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail

>[3] #DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2

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

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

Hi
The obvious way is by setting your home url in the web server (domain.tld/shop). You can also use an OCA module "website SEO redirection" that let you redirect any url.

But you may find more interesting to keep your home as is and add some useful widgets like featured products, new products, products more often buy, sales, etc. Regarding categories the mega menu will do the same.

In any case, this is not bad for SEO.

Anyway, don't forget to keep an eye on your website analytics. Because most visitors comes directly on a product page. So this question about home or shop is mostly irelevant.

Hope this help
Xavier

by xavier - 12:15 - 4 Mar 2024

Re: Making a redirect from "/" to "/shop" is bad idea for indexing Odoo website?

Sorry for bottom posting, I recently have found a possible configuration by this post

https://www.odoo.com/forum/help-1/how-to-load-direct-shop-page-on-website-198236

From what I can see with this configuration you will not be redirected to /shop, you stay on home but instead of loading home you are going to load /shop template and data.
It seems to be compatible with the need I described before, what do you think?

Thank you
--

Francesco Ballerini

Privo di virus.www.avast.com

Il giorno dom 3 mar 2024 alle ore 14:26 Francesco Ballerini <francescobl.lavoro@gmail.com> ha scritto:
Hello,

I am trying to build an e-Commerce with odoo14 and I have noticed that home route is an empty page. Basically everything I need in the home is already in the "/shop" page. Main template that I need are

- product grid
- e-Commerce categories
- featured products (introduced with 3rd party module)
- new arrivals (introduced with 3rd party module)

It would be a pain to bring all these into a new route (home route) and it would be so much reasonable to just make a redirect from "/" to "/shop".

My issue is that my knowledge of "indexing" is basically non-existent, so I'm not aware of the consequences, it's hard for me to formulate a specific question about this topic so I'm just going to ask, in general: the "redirect approach" would be a BAD approach considering the way Odoo is designed ?

In case it is not the right approach would you be so kind to suggest me a better possible solution to bring all template and controllers that I need from "/shop" to "/" ?

I ask this mainly because have been told that generally keeping your home on "/" will improve the indexing, but I am not sure if that also applies to the Odoo structure.

Will really appreciate your feedbacks
Thank you
--

Francesco Ballerini

Privo di virus.www.avast.com

by Francesco Ballerini - 03:01 - 3 Mar 2024

Show product "sold" quantity on purchase order lines

Hi,

I have been asked to be able to show, on a purchase order, the quantity of product that has been sold on a period (e.g. last 90 days or last 180 days) on every purchase order line.

I am struggling to find any module, do you know something similar?

Thanks

--

Francesco Ballerini

Privo di virus.www.avast.com

by Francesco Ballerini - 08:33 - 2 Mar 2024

Purchasing "packaging-like" products

Hello,

I am dealing with a situation where the customer purchases many products that are like this: "Flora Margarine 8x1kg" It is not packaging, because it is not possible to buy just 1kg. This is quite confusing for the customer and I am trying to make it easier for them to manage. One of the problems is that they perceive that the UoM here should be kg (because they just see it there in the name). This can be handled by product_secondary_unit and stock_secondary_unit to get the amount in kgs.

What I think could help is this: when ordering 1 unit of that product somehow turn in into 8 units of virtual "Flora Margarine 1kg" I am trying to wrap my head around this with no success. I have considered these modules but none seem to be doing what I would like to:

* product_supplierinfo_qty_multiplier
* purchase_only_by_packaging
* product_pack

Any ideas on how to approach this? Thank you very much.

Best regards

	Radovan Skolnik

by Radovan Skolnik - 08:36 - 1 Mar 2024

4 replies 4 replies

Re: Purchasing "packaging-like" products

Actually, no need to fiddle with price as the product.supplierinfo holds price 
for purchase UoM. Even better.

Best regards

	Radovan

On sobota 2. marca 2024 16:41:16 CET Radovan Skolnik wrote:

> Hi Tom,

> 

> 

> thank you for tip. That's probably the way to go even it requires some

> tweaking of the product name / purchase description / price. What I mean is

> if we have the original product like "Flora Margarine 8x1kg" for 40EUR and

> we create UoM of 8-pack, the product internally should have name of "Flora

> Margarine 1kg", purchase description of "Flora Margarine 8x1kg" and cost of

> 5EUR. However that is doable even with hundreds of products - regular

> expressions in Libre Office can do magic to help.

> 

> Few things then remain when purchasing like:

> 1) On purchase order use only purchase description so it seems like the

> original product. There used to be purchase_order_line_description, but

> latest version is stuck at 12.0 Will port to 17.0 2) Only allow the

> purchase_uom_id of that 8-pack to be selected on purchase order as no other

> UoM is really available. Something like Aymerick suggested but not aware of

> something dealing with this 3) Maybe hiding the name of the UoM from

> purchase order as it would confuse the supplier

> 

> Best regards

> 

> 	Radovan

> 

> On piatok 1. marca 2024 22:12:14 CET Tom Blauwendraat wrote:

> > Hi Radovan

> > I had to deal with a similar situation for a supermarket, where

> > an external database had to be imported as products in the system.

> > It had a lot of similar examples like "package of 6 eggs" or

> > "crate of 20 bottles" whereby the purchase and sales units are

> > different.

> > 

> > I ended up creating separate "uom" records for each, which

> > correspond to a certain number of another "uom". So a "12 pack" is

> > 12 times a "unit". You can then decide to purchase in a different

> > unit and sell in another unit. Odoo also has some documentation on

> > it:

> > https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/

> > in ventory/product_management/product_replenishment/uom.html [1] Maybe

> > this could help

> > 

> > -Tom

> > 

> > 

> > 

> > 

> > 

> > On 3/1/24 20:36, Radovan Skolnik wrote:

> > 

> > 

> > Hello,

> > I am dealing with a situation where the customer purchases many products

> > that are like this: "Flora Margarine 8x1kg" It is not packaging, because

> > it

> > is not possible to buy just 1kg. This is quite confusing for the customer

> > and I am trying to make it easier for them to manage. One of the problems

> > is that they perceive that the UoM here should be kg (because they just

> > see

> > it there in the name). This can be handled by product_secondary_unit and

> > stock_secondary_unit to get the amount in kgs. What I think could help is

> > this: when ordering 1 unit of that product somehow turn in into 8 units of

> > virtual "Flora Margarine 1kg" I am trying to wrap my head around this with

> > no success. I have considered these modules but none seem to be doing what

> > I would like to: * product_supplierinfo_qty_multiplier

> > * purchase_only_by_packaging

> > * product_pack

> > Any ideas on how to approach this? Thank you very much.

> > Best regards

> > Radovan Skolnik

> > 

> > 

> > _______________________________________________

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

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

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

> > 

> > 

> > 

> > _______________________________________________

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

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

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

> > 

> > 

> > 

> > [1]

> > https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/

> > i

> > nventory/product_management/product_replenishment/uom.html [2]

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

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

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

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

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

by Radovan Skolnik - 04:51 - 2 Mar 2024

Re: Purchasing "packaging-like" products

Hi Tom,


thank you for tip. That's probably the way to go even it requires some tweaking of the product name / purchase description / price. What I mean is if we have the original product like "Flora Margarine 8x1kg" for 40EUR and we create UoM of 8-pack, the product internally should have name of "Flora Margarine 1kg", purchase description of "Flora Margarine 8x1kg" and cost of 5EUR. However that is doable even with hundreds of products - regular expressions in Libre Office can do magic to help.

Few things then remain when purchasing like:
1) On purchase order use only purchase description so it seems like the original product. There used to be purchase_order_line_description, but latest version is stuck at 12.0 Will port to 17.0
2) Only allow the purchase_uom_id of that 8-pack to be selected on purchase order as no other UoM is really available. Something like Aymerick suggested but not aware of something dealing with this
3) Maybe hiding the name of the UoM from purchase order as it would confuse the supplier

Best regards

	Radovan


On piatok 1. marca 2024 22:12:14 CET Tom Blauwendraat wrote:

> Hi Radovan

> I had to deal with a similar situation for a supermarket, where

> an external database had to be imported as products in the system.

> It had a lot of similar examples like "package of 6 eggs" or

> "crate of 20 bottles" whereby the purchase and sales units are

> different.

> 

> I ended up creating separate "uom" records for each, which

> correspond to a certain number of another "uom". So a "12 pack" is

> 12 times a "unit". You can then decide to purchase in a different

> unit and sell in another unit. Odoo also has some documentation on

> it:

> https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/in

> ventory/product_management/product_replenishment/uom.html [1] Maybe this

> could help

> 

> -Tom

> 

> 

> 

> 

> 

> On 3/1/24 20:36, Radovan Skolnik wrote:

> 

> 

> Hello,

> I am dealing with a situation where the customer purchases many products

> that are like this: "Flora Margarine 8x1kg" It is not packaging, because it

> is not possible to buy just 1kg. This is quite confusing for the customer

> and I am trying to make it easier for them to manage. One of the problems

> is that they perceive that the UoM here should be kg (because they just see

> it there in the name). This can be handled by product_secondary_unit and

> stock_secondary_unit to get the amount in kgs. What I think could help is

> this: when ordering 1 unit of that product somehow turn in into 8 units of

> virtual "Flora Margarine 1kg" I am trying to wrap my head around this with

> no success. I have considered these modules but none seem to be doing what

> I would like to: * product_supplierinfo_qty_multiplier

> * purchase_only_by_packaging

> * product_pack

> Any ideas on how to approach this? Thank you very much.

> Best regards

> Radovan Skolnik

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1]

> https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/i

> nventory/product_management/product_replenishment/uom.html [2]

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

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

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

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

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

by Radovan Skolnik - 04:46 - 2 Mar 2024

Re: Purchasing "packaging-like" products
This option with UoM is nice for food business because UoM is shown by default on the pdf reports (SO, INV).

To go a step further (in standard) your customer could create differents categories of UoM by type of products or by brand if there is a lot of differences. This would help to avoid having hundreds of UoM into the same category and limit the mistake of selecting « pack of X » if this specific UoM is not available for the product.

Aymerick Glowacki

Le ven. 1 mars 2024 à 22:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :

Hi Radovan

I had to deal with a similar situation for a supermarket, where an external database had to be imported as products in the system. It had a lot of similar examples like "package of 6 eggs" or "crate of 20 bottles" whereby the purchase and sales units are different.

I ended up creating separate "uom" records for each, which correspond to a certain number of another "uom". So a "12 pack" is 12 times a "unit". You can then decide to purchase in a different unit and sell in another unit. Odoo also has some documentation on it:

https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.html

Maybe this could help

-Tom

On 3/1/24 20:36, Radovan Skolnik wrote:

Hello, I am dealing with a situation where the customer purchases many products that are like this: "Flora Margarine 8x1kg" It is not packaging, because it is not possible to buy just 1kg. This is quite confusing for the customer and I am trying to make it easier for them to manage. One of the problems is that they perceive that the UoM here should be kg (because they just see it there in the name). This can be handled by product_secondary_unit and stock_secondary_unit to get the amount in kgs. What I think could help is this: when ordering 1 unit of that product somehow turn in into 8 units of virtual "Flora Margarine 1kg" I am trying to wrap my head around this with no success. I have considered these modules but none seem to be doing what I would like to: * product_supplierinfo_qty_multiplier * purchase_only_by_packaging * product_pack Any ideas on how to approach this? Thank you very much. Best regards Radovan Skolnik

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

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by glowacki.aymerick - 11:26 - 1 Mar 2024
Re: Purchasing "packaging-like" products
Hi Radovan

I had to deal with a similar situation for a supermarket, where an external database had to be imported as products in the system. It had a lot of similar examples like "package of 6 eggs" or "crate of 20 bottles" whereby the purchase and sales units are different.

I ended up creating separate "uom" records for each, which correspond to a certain number of another "uom". So a "12 pack" is 12 times a "unit". You can then decide to purchase in a different unit and sell in another unit. Odoo also has some documentation on it:

https://www.odoo.com/documentation/17.0/nl/applications/inventory_and_mrp/inventory/product_management/product_replenishment/uom.html

Maybe this could help

-Tom

On 3/1/24 20:36, Radovan Skolnik wrote:

Hello, I am dealing with a situation where the customer purchases many products that are like this: "Flora Margarine 8x1kg" It is not packaging, because it is not possible to buy just 1kg. This is quite confusing for the customer and I am trying to make it easier for them to manage. One of the problems is that they perceive that the UoM here should be kg (because they just see it there in the name). This can be handled by product_secondary_unit and stock_secondary_unit to get the amount in kgs. What I think could help is this: when ordering 1 unit of that product somehow turn in into 8 units of virtual "Flora Margarine 1kg" I am trying to wrap my head around this with no success. I have considered these modules but none seem to be doing what I would like to: * product_supplierinfo_qty_multiplier * purchase_only_by_packaging * product_pack Any ideas on how to approach this? Thank you very much. Best regards Radovan Skolnik

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Tom Blauwendraat - 10:11 - 1 Mar 2024

[PSA] mail template editor group, mass mailing user group

Hi all,

today I got aware that Odoo by default (and by design) assigns the mail 
template editor group to all backend users. Sounds harmless, but being a 
member of this group allows you to run code, and when you can run code you can 
do all kinds of nefarious things in the database.

Given I'm busy with Odoo for a very long time, I'm a little ashamed that this 
is news for me, but as a few colleagues I asked were also not aware of this, 
it seems a good idea to me to spread awareness.

On https://github.com/OCA/social/pull/1319 you find a module that helps you 
removing this potentially dangerous group from your users.

A very similar issue is mass_mailing with the mass mailing user group, the 
above PR also contains a module to address that.

My (and my customers') expectation is: Nobody can run code unless being added 
to some high privilege group like mass mailing user explicitly, and those 
modules help implementing this.

Best regards,
Holger


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

by Holger Brunn - 04:41 - 29 Feb 2024

1 attachments 1 attachments

5 replies 5 replies

Re: [PSA] mail template editor group, mass mailing user group
Interesting. In a v16 enterprise migration it does not give that permission.

This meant that the built in followup letters could not be edited. It is fairly easy to work around as the ability to edit a rendered message is not determined by group but by computed field. The biggest issues with giving users access to template editing is not security by the way, it is the fact they will cock it up as you need to understand object notation, translation management and that you are affecting everyone.

We have written a lot of security changes/enhancements as I'm sure many others have. A lot have been to mitigate unforeseen multicompany effects but not all. Off the top of my head these are some of the things we could give fairly immediately although like most internal code, it will need some generalizing/refactoring..

Master Data Security - basically stops regular users doing crud on warehouses, products, uom's, locations except for a very few whitelisted fields.
Partner Lock - Allows to lock a partner so it cannot be changed unless unlocked (e.g. a key supplier where clowns change the email address, or a company partner record)
The stuff for mail templates.
Sane Accounting Access defaults - this actually adds functionality to Billing User so they don't have to be given Accounting Access to do things like view Payable/Receivable Report or reconciliation screen.
Adding an intracompany user (different to inter) locked to a single company rather than using uid 1 or OdooBot.

I think maybe access management is a better term than security for this, as we are really only talking about User Access.

On Fri, Mar 1, 2024 at 7:32 AM Holger Brunn <notifications@odoo-community.org> wrote:
> I think a security repository sounds like a great idea. I am less > enthusiastic about auto-installation, as its use is a bit contentious and > has spawned modules like module_change_auto_install [1] . but exactly that repository would be for people who want an installation that is, well, for however we define it 'secure by default'. There I'd find it a feature that if you have the repo, and install some module from core that does things violating our idea of 'secure by default', you get the module that squelches that violation immediately. If we don't have the auto install, every integrator will have to depend on those modules explicitly, which I will do anyways for my customers, so for me it doesn't really matter. Still I think it will be more convenient for most people to just pull this repo into however they do their deployment, and then the magic happens. But I agree, much less modules than authors think are a good idea to auto install in the general case. -- Your partner for the hard Odoo problems https://hunki-enterprises.com

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by "Graeme Gellatly" <graeme@moahub.nz> - 08:34 - 29 Feb 2024

Re: [PSA] mail template editor group, mass mailing user group

> I think a security repository sounds like a great idea. I am less

> enthusiastic about auto-installation, as its use is a bit contentious and

> has spawned modules like  module_change_auto_install [1] .

but exactly that repository would be for people who want an installation that 
is, well, for however we define it 'secure by default'. There I'd find it a 
feature that if you have the repo, and install some module from core that does 
things violating our idea of 'secure by default', you get the module that 
squelches that violation immediately.

If we don't have the auto install, every integrator will have to depend on 
those modules explicitly, which I will do anyways for my customers, so for me 
it doesn't really matter. Still I think it will be more convenient for most 
people to just pull this repo into however they do their deployment, and then 
the magic happens.

But I agree, much less modules than authors think are a good idea to auto 
install in the general case.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

by Holger Brunn - 07:31 - 29 Feb 2024

1 attachments 1 attachments

Re: [PSA] mail template editor group, mass mailing user group

I think a security repository sounds like a great idea. I am less enthusiastic about auto-installation, as its use is a bit contentious and has spawned modules like module_change_auto_install.

On Thu, Feb 29, 2024 at 11:52 AM Holger Brunn <notifications@odoo-community.org> wrote:

> Did you report this vulnerability to Odoo SA?


> https://www.odoo.com/security-report [1]

yes, but I learned this was a choice they made. You're supposed to click the 
'restrict mail templates' flag in the general settings if you disagree. (which 
still doesn't change the fact that everyone is a mail template editor as soon 
as you install mass_mailing)

Seems a different philosophy, I want secure by default, they want easy. 
Actually, I was a bit frightened about this being a conscious choice so now 
I'm sifting through other core modules if I find similar choices.

If so, a secure-by-default oca repo might be in order, where we collect 
modules like the ones I propose above, and set them to auto install.



-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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

by "Adam Heinz" <adam.heinz@metricwise.com> - 07:16 - 29 Feb 2024

Re: [PSA] mail template editor group, mass mailing user group

> Did you report this vulnerability to Odoo SA?

> https://www.odoo.com/security-report [1]

yes, but I learned this was a choice they made. You're supposed to click the 
'restrict mail templates' flag in the general settings if you disagree. (which 
still doesn't change the fact that everyone is a mail template editor as soon 
as you install mass_mailing)

Seems a different philosophy, I want secure by default, they want easy. 
Actually, I was a bit frightened about this being a conscious choice so now 
I'm sifting through other core modules if I find similar choices.

If so, a secure-by-default oca repo might be in order, where we collect 
modules like the ones I propose above, and set them to auto install.


-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

by Holger Brunn - 05:51 - 29 Feb 2024

1 attachments 1 attachments

Re: [PSA] mail template editor group, mass mailing user group

Did you report this vulnerability to Odoo SA?

https://www.odoo.com/security-report

On Thu, Feb 29, 2024 at 10:42 AM Holger Brunn <notifications@odoo-community.org> wrote:

Hi all,

today I got aware that Odoo by default (and by design) assigns the mail 
template editor group to all backend users. Sounds harmless, but being a 
member of this group allows you to run code, and when you can run code you can 
do all kinds of nefarious things in the database.

Given I'm busy with Odoo for a very long time, I'm a little ashamed that this 
is news for me, but as a few colleagues I asked were also not aware of this, 
it seems a good idea to me to spread awareness.

On https://github.com/OCA/social/pull/1319 you find a module that helps you 
removing this potentially dangerous group from your users.

A very similar issue is mass_mailing with the mass mailing user group, the 
above PR also contains a module to address that.

My (and my customers') expectation is: Nobody can run code unless being added 
to some high privilege group like mass mailing user explicitly, and those 
modules help implementing this.

Best regards,
Holger



-- 
Your partner for the hard Odoo problems
https://hunki-enterprises.com

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

by "Adam Heinz" <adam.heinz@metricwise.com> - 05:10 - 29 Feb 2024

Empty SQL argument and ANY operator

Hello everyone,

I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.

The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email

I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.

I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.

My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.

Any idea ?

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

by Yann Papouin - 12:52 - 21 Feb 2024

1 attachments 1 attachments

4 replies 4 replies

Re: Empty SQL argument and ANY operator

After a few months, I'm coming back on this issue as my initial dirty fix was wrong, the culprit comes from the hard-coded SQL query because the following statement is invalid:
and p.id != ANY(%s)
and should be replaced with following statement to have the expected result
and not p.id = ANY(%s)

That's awkward as it works perfectly for
and (p.email != ANY(%s) or p.email is null)

---------------------------------------------------------------
SELECT
P.ID, P.EMAIL
FROM
RES_PARTNER P

"id","email"
1,"contact1@dec.sarl"
2,"contact2@dec.sarl"
3,"contact3@dec.sarl"
4,null

---------------------------------------------------------------
SELECT
P.ID,
P.EMAIL
FROM
RES_PARTNER P
WHERE
p.id != ANY((ARRAY[1,2]))

"id","email"
1,"contact1@dec.sarl"
2,"contact2@dec.sarl"
3,"contact3@dec.sarl"
4,NULL

---------------------------------------------------------------
SELECT
P.ID,
P.EMAIL
FROM
RES_PARTNER P
WHERE
not p.id = ANY((ARRAY[1,2]))

"id","email"
3,"contact3@dec.sarl"
4,NULL

---------------------------------------------------------------
SELECT
P.ID,
P.EMAIL
FROM
RES_PARTNER P
WHERE
NOT P.EMAIL = ANY ((ARRAY['contact1@dec.sarl']))
OR P.EMAIL IS NULL

"id","email"
2,"contact2@dec.sarl"
3,"contact3@dec.sarl"
4,NULL

---------------------------------------------------------------
SELECT
P.ID,
P.EMAIL
FROM
RES_PARTNER P
WHERE
P.EMAIL != ANY ((ARRAY['contact1@dec.sarl']))
OR P.EMAIL IS NULL

"id","email"
2,"contact2@dec.sarl"
3,"contact3@dec.sarl"
4,NULL

by Yann Papouin - 09:09 - 29 May 2024
Re: Empty SQL argument and ANY operator

Looks like a bug indeed, in 14.0 and lower. In 15.0 the code seems refactored.

>>> env.cr.execute("select count(1) from res_users where id != any(%s)", (([1,],)))
>>> env.cr.query
b'select count(1) from res_users where id != any(ARRAY[1])'
>>> env.cr.fetchall()
[(248,)]

>>> env.cr.execute("select count(1) from res_users where id != any(%s)", (([],)))
>>> env.cr.query
b"select count(1) from res_users where id != any('{}')"
>>> env.cr.fetchall()
[(0,)]

Probably the Odoo programmers misinterpreted what kind of query psycopg would generate in such a case.

On 2/21/24 15:22, Yann Papouin wrote:

I forgot again that this OCA's mailing-list bug is not fixed (if someone interested: https://github.com/decgroupe/odoo-ocb/commit/5d07dba81e05d44fdbd593017e13de5c22a1c46e)

You can see the image here: https://odoo-community.org/groups/contributors-15/contributors-1702031?mode=thread&date_begin=&date_end=

The relevant code is: https://github.com/odoo/odoo/blob/b7777c50d40cc56e094f43d8f35753d713e17f77/addons/mail/models/mail_thread.py#L2523-L2541

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

Le mer. 21 févr. 2024 à 15:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :

For some reason I can't see the image, can you maybe send it as attachment?

Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?

On 2/21/24 12:52, Yann Papouin wrote:

Hello everyone,

I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.

The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email

I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.

I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.

My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.

Any idea ?

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

_______________________________________________
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 Tom Blauwendraat - 07:51 - 21 Feb 2024
Re: Empty SQL argument and ANY operator

I forgot again that this OCA's mailing-list bug is not fixed (if someone interested: https://github.com/decgroupe/odoo-ocb/commit/5d07dba81e05d44fdbd593017e13de5c22a1c46e)

You can see the image here: https://odoo-community.org/groups/contributors-15/contributors-1702031?mode=thread&date_begin=&date_end=
The relevant code is: https://github.com/odoo/odoo/blob/b7777c50d40cc56e094f43d8f35753d713e17f77/addons/mail/models/mail_thread.py#L2523-L2541

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

Le mer. 21 févr. 2024 à 15:12, Tom Blauwendraat <notifications@odoo-community.org> a écrit :

For some reason I can't see the image, can you maybe send it as attachment?

Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?

On 2/21/24 12:52, Yann Papouin wrote:

Hello everyone,

I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.

The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email

I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.

I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.

My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.

Any idea ?

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

_______________________________________________
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 Yann Papouin - 03:21 - 21 Feb 2024
Re: Empty SQL argument and ANY operator

For some reason I can't see the image, can you maybe send it as attachment?

Also, can you provide a link to the relevant part of the Odoo source code that defines "except_partner"?

On 2/21/24 12:52, Yann Papouin wrote:

Hello everyone,

I'm trying to debug Odoo 14.0 to understand why some emails received on one of our public channel are not forwarded to all members of the list.

The SQL query is made to retrieve all partners members of a channel that will be notified with a copy of the received email

I tracked down the issue to the fact that an empty list (except_partner) is converted to '{}' (empty array literal) when used as an argument in the SQL query and the result of the query with this condition is always empty.

I'm pretty sure that it is something tricky around the SQL language but as I'm not an expert on this, I don't know how to fix it.

My current dirty fix is to add except_partner.append(0) to have a valid query but I would prefer to have the real SQL fix.

Any idea ?

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

_______________________________________________
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 - 03:10 - 21 Feb 2024

Status of different branches and reasoning to choose

Hi,

oca hosts a lot of repositories whith branches for the different 
versions of odoo (..14,16,17). What's missing for me is a big picture of 
the overall state of the different versions... Is community still most 
complete/stable on 14, 16 oder 17 (or maybe even 12)?

What version would you suggest to start with?

What's also missing for me is a good big picture on the difference in 
code/features beetween odoo enterprise, odoo open-source and oca on the 
different versions.

thx for any feedback,
Peter

by Peter Niederlag - 01:16 - 18 Feb 2024

3 replies 3 replies

Re: Status of different branches and reasoning to choose

More on this:

First about stability: as Pedro explained today there is no difference in stability between pair and odd versions. The thing is there is a resonance happening where pair versions are a bit more popular among skilled integrators and have more OCA modules. This can be observed by looking at the number of modules OCA by version in the attachment.

Usually in the 1st year after the release around 90 modules per month are migrated in the OCA and it slows down after some 3 years. For some reason, the situation with v17 isn't as good today yet the version is reputed "stable". Note that this is only "merged" modules, there are a lot more modules with a valid migration Pull Request proposition that is just not merged yet (there a lot of such PRs for v17).

I would add: you can choose a recent version both for large and small projects because small projects will need just a few modules and large ones might have money to migrate whatever is required. Mid sized projects however might be tricky if you choose a version that is too recent like version 17 today.

On Thu, Feb 22, 2024 at 9:37 AM Pedro M. Baeza <notifications@odoo-community.org> wrote:
Good summary from Xavier. Just one clarification: the question about even versions being more stable is a myth propagated by some interested parties. You may find the same number of problems in even or odd versions (as in any software), and nowadays, they have been reduced a lot thanks to the maturity the software has. Anyway, any just released version is expected to have some of them, requiring a bit of time to get the proper coverage. But I also want to distinguish here the scope of these bugs: most of the time they are really edge cases or special use cases that are uncovered or not tested when a refactoring is done, and only after someone faces such use case, it's discovered and fixed. We are now discovering some of them in 15.0 2 years after their release with a special case with stock packages while having dozens of customers without problem because they don't use that specific flow with the packages.

You have to analyze the cust omer requirements, and see the gap between them and:

- Odoo core features in that version.
- Already migrated OCA modules to that version.

and always trying to push to the latest version if possible, as it can be considered always the best version released. Only if the gap can be covered with a lot of OCA modules that are not migrated, then you may think about putting a prior version, but I invite you to reverse the thing: dedicate a bit of budget to migrate that modules to the latest version, and you will save having a lot of features including by Odoo S. A. itself in that version (they have more than 300 developers investing their full time each year to improve the product).

Regards.

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

--
Raphaël Valyi
Founder and consultant
http://twitter.com/rvalyi
www.akretion.com

by "Raphaël Valyi" <rvalyi@akretion.com> - 05:35 - 22 Feb 2024

1 attachments 1 attachments

2024-02-22_13-27.png
Re: Status of different branches and reasoning to choose

Good summary from Xavier. Just one clarification: the question about even versions being more stable is a myth propagated by some interested parties. You may find the same number of problems in even or odd versions (as in any software), and nowadays, they have been reduced a lot thanks to the maturity the software has. Anyway, any just released version is expected to have some of them, requiring a bit of time to get the proper coverage. But I also want to distinguish here the scope of these bugs: most of the time they are really edge cases or special use cases that are uncovered or not tested when a refactoring is done, and only after someone faces such use case, it's discovered and fixed. We are now discovering some of them in 15.0 2 years after their release with a special case with stock packages while having dozens of customers without problem because they don't use that specific flow with the packages.

You have to analyze the customer requirements, and see the gap between them and:

- Odoo core features in that version.
- Already migrated OCA modules to that version.

and always trying to push to the latest version if possible, as it can be considered always the best version released. Only if the gap can be covered with a lot of OCA modules that are not migrated, then you may think about putting a prior version, but I invite you to reverse the thing: dedicate a bit of budget to migrate that modules to the latest version, and you will save having a lot of features including by Odoo S. A. itself in that version (they have more than 300 developers investing their full time each year to improve the product).

Regards.

by Pedro M. Baeza - 01:36 - 22 Feb 2024

Re: Status of different branches and reasoning to choose

Le 18.02.2024 13:18, Peter Niederlag a écrit :

> Hi,

> oca hosts a lot of repositories whith branches for the different

> versions of odoo (..14,16,17). What's missing for me is a big picture 

> of

> the overall state of the different versions... Is community still most

> complete/stable on 14, 16 oder 17 (or maybe even 12)?

> What version would you suggest to start with?

> What's also missing for me is a good big picture on the difference in

> code/features beetween odoo enterprise, odoo open-source and oca on the

> different versions.

Because of rigorous OCA policy, the code is allways in a very good 
state. All OCA modules are stables (some are in alpha or beta version 
but it is told in the Readme). Obviously, Odoo extend its 
functionlitiezs and some OCA modules become obsoletes -- but some of 
them are still there for various reasons (like a different workflow).

Regarding versions, I had the same questions years ago. The answer 
depends of what you really need instead of which version has more 
functionalities. First of all, Odoo tends to be more stable in pair 
versions and OCA is run by volunteers who are not allways using a recent 
version of Odoo. Some modules are also very generic because OCA members 
use them as a base for their need.

Also, you have to understand that OCA's modules are useful for both Odoo 
Enterprise and Odoo Community Edition. OCA doesn't intend to complete 
the Odoo CE, it share module or libs that are useful for integrators.

If you need a big picture, it help to browse apps.odoo.com (both free 
and paid modules) using categories to understand what is missing in 
Odoo.

Finally you allways have to wait some months before choosing an Odoo 
version because a lot of bugs are fixed during the year (for example, 
Odoo 16 has 4 "dot realases").

I will advice the Odoo 16 CE version from the OCB repository (see OCB 
faq in the corresponding wiki). A lot of modules are already migrated. 
If you need some other modules, wait a bit or choose the 14 version -- 
or better, help the migration (money, code, ...).

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

by xavier - 03:25 - 18 Feb 2024

Concurrency write check

Hi,

I haven't found a way to check if the concurrency check here works: https://github.com/odoo/odoo/blob/14.0/odoo/models.py#L3251

Shouldn't it warn/block if someone tries to write on a field that has been modified in the meanwhile?

Sergio Corato

by Sergio Corato - 06:26 - 14 Feb 2024

11 replies 11 replies

Re: Concurrency write check
> I guess it's easy to (re)build this as an OCA module, although instances that install it will probably also run into the problems that made Odoo ditch it.
I agree, a less impacting solution should be better.

Il giorno ven 16 feb 2024 alle ore 15:12 David Vidal <notifications@odoo-community.org> ha scritto:
> From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.

In the web_editor there's a kind of concurrence protection: https://github.com/OCA/OCB/blob/15.0/addons/web_editor/controllers/main.py#L32-L39

Interesting, but it's only implemented for collaborative pages on web (events? I couldn't find where).

Sergio Corato

El vie, 16 feb 2024 a las 14:32, Sergio Corato (<notifications@odoo-community.org>) escribió:
From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.
Sergio Corato

Il giorno ven 16 feb 2024 alle ore 10:32 Ronald Portier <notifications@odoo-community.org> ha scritto:

So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.

In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.

In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.

Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.

An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.

Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.

On 15-02-2024 23:11, Tom Blauwendraat wrote:

Closest I could come in finding some info about it is this:

https://github.com/odoo/odoo/pull/87756

Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.

On 2/15/24 19:07, Sergio Corato wrote:

The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).

Debugging didn't help, the context is never passed with the field '__last_update'.

However it's not a requested function, I'll give up for now ;)

Thanks

Sergio Corato

Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue

_______________________________________________
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 Sergio Corato - 04:11 - 16 Feb 2024
Re: Concurrency write check
> From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.

In the web_editor there's a kind of concurrence protection: https://github.com/OCA/OCB/blob/15.0/addons/web_editor/controllers/main.py#L32-L39

El vie, 16 feb 2024 a las 14:32, Sergio Corato (<notifications@odoo-community.org>) escribió:
From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.
Sergio Corato

Il giorno ven 16 feb 2024 alle ore 10:32 Ronald Portier <notifications@odoo-community.org> ha scritto:

So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.

In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.

In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.

Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.

An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.

Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.

On 15-02-2024 23:11, Tom Blauwendraat wrote:

Closest I could come in finding some info about it is this:

https://github.com/odoo/odoo/pull/87756

Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.

On 2/15/24 19:07, Sergio Corato wrote:

The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).

Debugging didn't help, the context is never passed with the field '__last_update'.

However it's not a requested function, I'll give up for now ;)

Thanks

Sergio Corato

Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue

_______________________________________________
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 David Vidal - 03:11 - 16 Feb 2024
Re: Concurrency write check
I guess it's easy to (re)build this as an OCA module, although instances that install it will probably also run into the problems that made Odoo ditch it.

On 2/16/24 14:32, Sergio Corato wrote:

From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.

Sergio Corato

Il giorno ven 16 feb 2024 alle ore 10:32 Ronald Portier <notifications@odoo-community.org> ha scritto:

So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.

In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.

In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.

Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.

An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.

Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.

On 15-02-2024 23:11, Tom Blauwendraat wrote:

Closest I could come in finding some info about it is this:

https://github.com/odoo/odoo/pull/87756

Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.

On 2/15/24 19:07, Sergio Corato wrote:

The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).

Debugging didn't help, the context is never passed with the field '__last_update'.

However it's not a requested function, I'll give up for now ;)

Thanks

Sergio Corato

Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue

_______________________________________________
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 Tom Blauwendraat - 03:11 - 16 Feb 2024
Re: Concurrency write check
From my pov, a simple advice, on the UI with a js, should be enough to point out the fact.
Sergio Corato

Il giorno ven 16 feb 2024 alle ore 10:32 Ronald Portier <notifications@odoo-community.org> ha scritto:

So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.

In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.

In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.

Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.

An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.

Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.

On 15-02-2024 23:11, Tom Blauwendraat wrote:

Closest I could come in finding some info about it is this:

https://github.com/odoo/odoo/pull/87756

Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.

On 2/15/24 19:07, Sergio Corato wrote:

The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).

Debugging didn't help, the context is never passed with the field '__last_update'.

However it's not a requested function, I'll give up for now ;)

Thanks

Sergio Corato

Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue

_______________________________________________
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 Sergio Corato - 02:27 - 16 Feb 2024
Re: Concurrency write check
So basically Odoo has no longer any mechanism to prevent the changes of one user undoing the changes of another user.

In applications traditionally two mechanisms existed that intended to prevent this problem, respectively pessimistic and optimistic locking.

In pessimistic locking anybody touching a record with the potential to update it, would establish a lock on the record, other users would be prevented from reading the same record for update. This has the potential for lots of access problems, especially as databases and transactions became more complicated and would no longer involve single records but whole networks of records.

Optimistic locking would, as Odoo does, timestamp all records. The idea that most reads that have a potential to update a record, mostly would not be updating anything. But when updating, the timestamp of the record read would be compared with the current timestamp and any previous change would result in an Exception.

An alternative method for optimistic locking, not depending on timestamps, would be to save the original record image and compare with the actual record image just before the actual update.

Missing either pessimistic locking or optimistic locking, for some applications it might be needed to implement a mechanism where a user must specifically claim a main application object for change, before being allowed to update it. A claim made preventing other users from making the same claim, before the application object being released. A main application object could be a Customer, an Order or a Helpdesk Ticket. Such a claim would work like a "check out" in document management systems, or a kind of Semaphore on OS level.

On 15-02-2024 23:11, Tom Blauwendraat wrote:

Closest I could come in finding some info about it is this:

https://github.com/odoo/odoo/pull/87756

Apparently it caused problems and was already long ago removed from the frontend, and by 16.0 they killed the backend part as well.

On 2/15/24 19:07, Sergio Corato wrote:

The logic isn't implemented/enabled in any version that I checked, this seems at least strange (I saw this function working in other softwares decades ago).

Debugging didn't help, the context is never passed with the field '__last_update'.

However it's not a requested function, I'll give up for now ;)

Thanks

Sergio Corato

Il giorno gio 15 feb 2024 alle ore 17:07 Tom Blauwendraat <notifications@odoo-community.org> ha scritto:

I also looked for unit tests and didn't find, and also saw this function was deleted in 16.0 (but maybe renamed). I think debugging is the only way to find out! pdb to the rescue

_______________________________________________
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 "Ronald Portier" <rportier@therp.nl> - 10:31 - 16 Feb 2024

Group all related stock picking

Hello,

I am looking for a way to search and group all related stock picking.

In the following snapshot I am resupplying in 1 step between 2 warehouses: a delivery from WH2 to transit and then another reception from transit to WH1.

How may search/group these two pickings (or move or move.lines)?

I thought that the module stock_request would help me by setting the procurement group but it is not propagated to further legs (after first picking).

Is there an existing app that can help? How may I do this?

Thank you.

by Yves Goldberg - 04:25 - 12 Feb 2024

1 attachments 1 attachments

2 replies 2 replies

Re: Group all related stock picking

Thank you Vincent. Will further test it.

----- Original message -----
From: Vincent Van Rossem <notifications@odoo-community.org>
To: Contributors <contributors@odoo-community.org>
Subject: Re: Group all related stock picking
Date: Monday, February 12, 2024 18:36

Hello Yves,

Could stock_picking_show_linked help you?

This module should allow a user to display, on smart buttons in a picking:

Destination pickings: the pickings associated to destination moves indicated in the moves in this picking
Origin pickings: the pickings associated to origin moves indicated in the moves in this picking

On Mon, Feb 12, 2024 at 4:27 PM Yves Goldberg <notifications@odoo-community.org> wrote:
Hello,
I am looking for a way to search and group all related stock picking.
In the following snapshot I am resupplying in 1 step between 2 warehouses: a delivery from WH2 to transit and then another reception from transit to WH1.

How may search/group these two pickings (or move or move.lines)?
I thought that the module stock_request would help me by setting the procurement group but it is not propagated to further legs (after first picking).
Is there an existing app that can help? How may I do this?
Thank you.

_______________________________________________
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 Yves Goldberg - 03:25 - 13 Feb 2024
Re: Group all related stock picking

Hello Yves,

Could stock_picking_show_linked help you?

This module should allow a user to display, on smart buttons in a picking:

Destination pickings: the pickings associated to destination moves indicated in the moves in this picking
Origin pickings: the pickings associated to origin moves indicated in the moves in this picking

On Mon, Feb 12, 2024 at 4:27 PM Yves Goldberg <notifications@odoo-community.org> wrote:
Hello,
I am looking for a way to search and group all related stock picking.
In the following snapshot I am resupplying in 1 step between 2 warehouses: a delivery from WH2 to transit and then another reception from transit to WH1.

How may search/group these two pickings (or move or move.lines)?
I thought that the module stock_request would help me by setting the procurement group but it is not propagated to further legs (after first picking).
Is there an existing app that can help? How may I do this?
Thank you.

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

by vincent.vanrossem - 05:36 - 12 Feb 2024

Count sale orders in sale analysis

Dear all

I'm trying to inherit sale report analysis in order to be able to count sale orders (not sale order lines)

It should be easy but I don't find the way...

Thank in advance for your help

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

by Cyril VINH-TUNG - 10:56 - 9 Feb 2024

1 replies 1 replies

Invoice Factur-X, l10n_fr_account_invoice_facturx

Hello all,

I've got questions about the factur-x generation xml file attached to the pdf. I'm working on the Odoo 12 version.

When i print my PDF report or use the "Send to Chorus" button, at the begining of the process a factur-x xml flux in well generated and is valid against the xsd schema. But at the the end of the process the _post_pdf method base IrActionsReport class (server\odoo\addons\account_facturx\models\ir_actions_report.py) is called.

==== CODE =======

@api.multi

def _post_pdf(self, save_in_attachment, pdf_content=None, res_ids=None):

# OVERRIDE

if self.model == 'account.invoice' and res_ids and len(res_ids) == 1:

invoice = self.env['account.invoice'].browse(res_ids)

if invoice.type in ('out_invoice', 'out_refund') and invoice.state != 'draft':

xml_content = invoice._export_as_facturx_xml()

# Add attachment.

reader_buffer = io.BytesIO(pdf_content)

reader = PdfFileReader(reader_buffer)

writer = PdfFileWriter()

writer.cloneReaderDocumentRoot(reader)

writer.addAttachment('factur-x.xml', xml_content)

buffer = io.BytesIO()

writer.write(buffer)

pdf_content = buffer.getvalue()

reader_buffer.close()

buffer.close()

return super(IrActionsReport, self)._post_pdf(save_in_attachment, pdf_content=pdf_content, res_ids=res_ids)

=================

As you can see, if the invoice is not in the 'draft' sale, the xml flux is re-generated according to another method invoice._export_as_facturx_xml() and attached to the PDF as factur-x.xml. And this factur-x xml content is not valid against the xsd schema. (see next)

==== COMMAND =======

"C:\DATA\Odoo 12.0\python\python.exe" "C:\DATA\Odoo 12.0\python\Scripts\facturx-xmlcheck" factur-x.xml

==== RESULT COMMAND =======

024-02-09 11:13:16,872 [INFO] Flavor is factur-x (autodetected)

2024-02-09 11:13:16,873 [INFO] Level is en16931 (autodetected)

2024-02-09 11:13:16,885 [ERROR] The XML file is invalid against the XML Schema Definition

2024-02-09 11:13:16,885 [ERROR] XSD Error: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40

2024-02-09 11:13:16,886 [ERROR] The Factur-x XML file is not valid against the official XML Schema Definition. Here is the error, which may give you an idea on the cause of the problem: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40.

=================

My final question is that when i "Send to Chorus", the invoice is rejected by the Chorus platform. I don't know why. I just can suppose that it comes from the fact that the xml flux is not valid.

Thanks to all to your help, hints.

Cedric

by Cedric DEBARD - 11:36 - 9 Feb 2024

3 replies 3 replies

Re: Invoice Factur-X, l10n_fr_account_invoice_facturx
Hi Rémi,

Many thanks for your help. It is better now.

Regards

Cédric

De : Rémi CAZENAVE - Le Filament <notifications@odoo-community.org>
A : Contributors <contributors@odoo-community.org>
Envoyé : 09/02/2024 13:12
Objet : Re: Invoice Factur-X, l10n_fr_account_invoice_facturx

Sorry, I made a mistake in my previous answer, the module from Odoo to be removed is of course account_facturx and not account_e-invoice_generate (which is the one from OCA)

Le 09/02/2024 à 11:57, Rémi CAZENAVE - Le Filament a écrit :

Hi Cedric,

You do not mention which modules you are using to generate Factur-X and send to Chorus, so I would assume you use OCA ones from l10n-france repository.

There is a known discrepancy between Odoo modules and OCA ones regarding factur-x generation.

Normally, if you installed factur-x and Chorus ones from OCA l10n-france directory, you should have also installed account_e-invoice_generate from OCA EDI repository (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate).

The README of that module mentions the following which is probably the cause of your issue (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate/README.rst#installation) :

The project OCA/edi provides modules to generate UBL and Factur-X invoices. This solution designed by OCA is an alternative to the solution provided by Odoo S.A. in the official addons (Community version), it is not a solution built above it.

As a consequence, before installing this module, you should uninstall the module account_facturx of Odoo S.A. The module account_facturx is an auto-install module, so it is probably installed by default on your Odoo.

If you want to generate Factur-X invoices, you should install the OCA module account_invoice_factur-x available on OCA/edi.

Do you have both account_e-invoice_generate and account_facturx installed ?

If so you should remove the one from Odoo (account_facturx). Be careful however that Odoo module account_facturx is auto-installable so it may reinstall on its own if you do not pay attention. This module may help in overcoming this behaviour : https://github.com/OCA/server-tools/tree/12.0/module_change_auto_install

Best Regards,

Rémi

Le 09/02/2024 à 11:37, DEBARD Cédric a écrit :

Hello all,

I've got questions about the factur-x generation xml file attached to the pdf. I'm working on the Odoo 12 version.

When i print my PDF report or use the "Send to Chorus" button, at the begining of the process a factur-x xml flux in well generated and is valid against the xsd schema. But at the the end of the process the _post_pdf method base IrActionsReport class (server\odoo\addons\account_facturx\models\ir_actions_report.py) is called.

==== CODE =======

@api.multi

def _post_pdf(self, save_in_attachment, pdf_content=None, res_ids=None):

# OVERRIDE

if self.model == 'account.invoice' and res_ids and len(res_ids) == 1:

invoice = self.env['account.invoice'].browse(res_ids)

if invoice.type in ('out_invoice', 'out_refund') and invoice.state != 'draft':

xml_content = invoice._export_as_facturx_xml()

# Add attachment.

reader_buffer = io.BytesIO(pdf_content)

reader = PdfFileReader(reader_buffer)

writer = PdfFileWriter()

writer.cloneReaderDocumentRoot(reader)

writer.addAttachment('factur-x.xml', xml_content)

buffer = io.BytesIO()

writer.write(buffer)

pdf_content = buffer.getvalue()

reader_buffer.close()

buffer.close()

return super(IrActionsReport, self)._post_pdf(save_in_attachment, pdf_content=pdf_content, res_ids=res_ids)

=================

As you can see, if the invoice is not in the 'draft' sale, the xml flux is re-generated according to another method invoice._export_as_facturx_xml() and attached to the PDF as factur-x.xml. And this factur-x xml content is not valid against the xsd schema. (see next)

==== COMMAND =======

"C:\DATA\Odoo 12.0\python\python.exe" "C:\DATA\Odoo 12.0\python\Scripts\facturx-xmlcheck" factur-x.xml

==== RESULT COMMAND =======

024-02-09 11:13:16,872 [INFO] Flavor is factur-x (autodetected)

2024-02-09 11:13:16,873 [INFO] Level is en16931 (autodetected)

2024-02-09 11:13:16,885 [ERROR] The XML file is invalid against the XML Schema Definition

2024-02-09 11:13:16,885 [ERROR] XSD Error: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40

2024-02-09 11:13:16,886 [ERROR] The Factur-x XML file is not valid against the official XML Schema Definition. Here is the error, which may give you an idea on the cause of the problem: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40.

=================

My final question is that when i "Send to Chorus", the invoice is rejected by the Chorus platform. I don't know why. I just can suppose that it comes from the fact that the xml flux is not valid.

Thanks to all to your help, hints.

Cedric

_______________________________________________
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 Cedric DEBARD - 05:31 - 9 Feb 2024
Re: Invoice Factur-X, l10n_fr_account_invoice_facturx
Sorry, I made a mistake in my previous answer, the module from Odoo to be removed is of course account_facturx and not account_e-invoice_generate (which is the one from OCA)

Le 09/02/2024 à 11:57, Rémi CAZENAVE - Le Filament a écrit :

Hi Cedric,

You do not mention which modules you are using to generate Factur-X and send to Chorus, so I would assume you use OCA ones from l10n-france repository.

There is a known discrepancy between Odoo modules and OCA ones regarding factur-x generation.

Normally, if you installed factur-x and Chorus ones from OCA l10n-france directory, you should have also installed account_e-invoice_generate from OCA EDI repository (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate).

The README of that module mentions the following which is probably the cause of your issue (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate/README.rst#installation) :

The project OCA/edi provides modules to generate UBL and Factur-X invoices. This solution designed by OCA is an alternative to the solution provided by Odoo S.A. in the official addons (Community version), it is not a solution built above it.

As a consequence, before installing this module, you should uninstall the module account_facturx of Odoo S.A. The module account_facturx is an auto-install module, so it is probably installed by default on your Odoo.

If you want to generate Factur-X invoices, you should install the OCA module account_invoice_factur-x available on OCA/edi.

Do you have both account_e-invoice_generate and account_facturx installed ?

If so you should remove the one from Odoo (account_facturx). Be careful however that Odoo module account_facturx is auto-installable so it may reinstall on its own if you do not pay attention. This module may help in overcoming this behaviour : https://github.com/OCA/server-tools/tree/12.0/module_change_auto_install

Best Regards,

Rémi

Le 09/02/2024 à 11:37, DEBARD Cédric a écrit :

Hello all,

I've got questions about the factur-x generation xml file attached to the pdf. I'm working on the Odoo 12 version.

When i print my PDF report or use the "Send to Chorus" button, at the begining of the process a factur-x xml flux in well generated and is valid against the xsd schema. But at the the end of the process the _post_pdf method base IrActionsReport class (server\odoo\addons\account_facturx\models\ir_actions_report.py) is called.

==== CODE =======

@api.multi

def _post_pdf(self, save_in_attachment, pdf_content=None, res_ids=None):

# OVERRIDE

if self.model == 'account.invoice' and res_ids and len(res_ids) == 1:

invoice = self.env['account.invoice'].browse(res_ids)

if invoice.type in ('out_invoice', 'out_refund') and invoice.state != 'draft':

xml_content = invoice._export_as_facturx_xml()

# Add attachment.

reader_buffer = io.BytesIO(pdf_content)

reader = PdfFileReader(reader_buffer)

writer = PdfFileWriter()

writer.cloneReaderDocumentRoot(reader)

writer.addAttachment('factur-x.xml', xml_content)

buffer = io.BytesIO()

writer.write(buffer)

pdf_content = buffer.getvalue()

reader_buffer.close()

buffer.close()

return super(IrActionsReport, self)._post_pdf(save_in_attachment, pdf_content=pdf_content, res_ids=res_ids)

=================

As you can see, if the invoice is not in the 'draft' sale, the xml flux is re-generated according to another method invoice._export_as_facturx_xml() and attached to the PDF as factur-x.xml. And this factur-x xml content is not valid against the xsd schema. (see next)

==== COMMAND =======

"C:\DATA\Odoo 12.0\python\python.exe" "C:\DATA\Odoo 12.0\python\Scripts\facturx-xmlcheck" factur-x.xml

==== RESULT COMMAND =======

024-02-09 11:13:16,872 [INFO] Flavor is factur-x (autodetected)

2024-02-09 11:13:16,873 [INFO] Level is en16931 (autodetected)

2024-02-09 11:13:16,885 [ERROR] The XML file is invalid against the XML Schema Definition

2024-02-09 11:13:16,885 [ERROR] XSD Error: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40

2024-02-09 11:13:16,886 [ERROR] The Factur-x XML file is not valid against the official XML Schema Definition. Here is the error, which may give you an idea on the cause of the problem: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40.

=================

My final question is that when i "Send to Chorus", the invoice is rejected by the Chorus platform. I don't know why. I just can suppose that it comes from the fact that the xml flux is not valid.

Thanks to all to your help, hints.

Cedric

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rémi Cazenave - 01:10 - 9 Feb 2024
Re: Invoice Factur-X, l10n_fr_account_invoice_facturx
Hi Cedric,

You do not mention which modules you are using to generate Factur-X and send to Chorus, so I would assume you use OCA ones from l10n-france repository.

There is a known discrepancy between Odoo modules and OCA ones regarding factur-x generation.

Normally, if you installed factur-x and Chorus ones from OCA l10n-france directory, you should have also installed account_e-invoice_generate from OCA EDI repository (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate).

The README of that module mentions the following which is probably the cause of your issue (https://github.com/OCA/edi/blob/12.0/account_e-invoice_generate/README.rst#installation) :

The project OCA/edi provides modules to generate UBL and Factur-X invoices. This solution designed by OCA is an alternative to the solution provided by Odoo S.A. in the official addons (Community version), it is not a solution built above it.

As a consequence, before installing this module, you should uninstall the module account_facturx of Odoo S.A. The module account_facturx is an auto-install module, so it is probably installed by default on your Odoo.

If you want to generate Factur-X invoices, you should install the OCA module account_invoice_factur-x available on OCA/edi.

Do you have both account_e-invoice_generate and account_facturx installed ?

If so you should remove the one from Odoo (account_e-invoice_generate). Be careful however that Odoo module account_e-invoice_generate is auto-installable so it may reinstall on its own if you do not pay attention. This module may help in overcoming this behaviour : https://github.com/OCA/server-tools/tree/12.0/module_change_auto_install

Best Regards,

Rémi

Le 09/02/2024 à 11:37, DEBARD Cédric a écrit :

Hello all,

I've got questions about the factur-x generation xml file attached to the pdf. I'm working on the Odoo 12 version.

When i print my PDF report or use the "Send to Chorus" button, at the begining of the process a factur-x xml flux in well generated and is valid against the xsd schema. But at the the end of the process the _post_pdf method base IrActionsReport class (server\odoo\addons\account_facturx\models\ir_actions_report.py) is called.

==== CODE =======

@api.multi

def _post_pdf(self, save_in_attachment, pdf_content=None, res_ids=None):

# OVERRIDE

if self.model == 'account.invoice' and res_ids and len(res_ids) == 1:

invoice = self.env['account.invoice'].browse(res_ids)

if invoice.type in ('out_invoice', 'out_refund') and invoice.state != 'draft':

xml_content = invoice._export_as_facturx_xml()

# Add attachment.

reader_buffer = io.BytesIO(pdf_content)

reader = PdfFileReader(reader_buffer)

writer = PdfFileWriter()

writer.cloneReaderDocumentRoot(reader)

writer.addAttachment('factur-x.xml', xml_content)

buffer = io.BytesIO()

writer.write(buffer)

pdf_content = buffer.getvalue()

reader_buffer.close()

buffer.close()

return super(IrActionsReport, self)._post_pdf(save_in_attachment, pdf_content=pdf_content, res_ids=res_ids)

=================

As you can see, if the invoice is not in the 'draft' sale, the xml flux is re-generated according to another method invoice._export_as_facturx_xml() and attached to the PDF as factur-x.xml. And this factur-x xml content is not valid against the xsd schema. (see next)

==== COMMAND =======

"C:\DATA\Odoo 12.0\python\python.exe" "C:\DATA\Odoo 12.0\python\Scripts\facturx-xmlcheck" factur-x.xml

==== RESULT COMMAND =======

024-02-09 11:13:16,872 [INFO] Flavor is factur-x (autodetected)

2024-02-09 11:13:16,873 [INFO] Level is en16931 (autodetected)

2024-02-09 11:13:16,885 [ERROR] The XML file is invalid against the XML Schema Definition

2024-02-09 11:13:16,885 [ERROR] XSD Error: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40

2024-02-09 11:13:16,886 [ERROR] The Factur-x XML file is not valid against the official XML Schema Definition. Here is the error, which may give you an idea on the cause of the problem: Element '{urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}SpecifiedLineTradeAgreement': Missing child element(s). Expected is ( {urn:un:unece:uncefact:data:standard:ReusableAggregateBusinessInformationEntity:100}NetPriceProductTradePrice )., line 40.

=================

My final question is that when i "Send to Chorus", the invoice is rejected by the Chorus platform. I don't know why. I just can suppose that it comes from the fact that the xml flux is not valid.

Thanks to all to your help, hints.

Cedric

_______________________________________________
Mailing-List: https://odoo-community.org/groups/contributors-15
Post to: mailto:contributors@odoo-community.org
Unsubscribe: https://odoo-community.org/groups?unsubscribe
by Rémi Cazenave - 12:01 - 9 Feb 2024

Archives

Contributors