Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • 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

    • Re: How do I copy a websitebuilder block in a theme
      Answer to myself.

      to duplicate e a block just add it to the actual page and then click into it.
      you the get a copy icon just below the "Blocks Customize Theme" line in the right side of the screen.
      However this is not the case fr the "Header" Block.
      Unfortunately this is the one I would like to duplicate/customize.

      If somebody knows how to do that, I am still eager to learn how to do it.

      thanks for listening

      Robert (the greYt)


      On 04.03.24 17:07, robert@redo2oo.ch wrote:
      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

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


      by robert - 07:26 - 4 Mar 2024
  • 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.

      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,

      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 


      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 Aymerick Glowacki - 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

    signature.asc

    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

      signature.asc
    • 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

      signature.asc
    • Re: [PSA] mail template editor group, mass mailing user group
      Did you report this vulnerability to Odoo SA?


      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.

    image.png

    Any idea ?

    --
    Yann PAPOUIN, Ingénieur R&D | DEC
    by Yann Papouin - 12:52 - 21 Feb 2024

    1 attachments 1 attachments

    image.png

    4 replies 4 replies

  • 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

      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

    image.png

    2 replies 2 replies

  • 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
  • Consuming stock internally while using the its costs in project 
    Hello,

I am dealing with a customer who provides catering services. The price is 
dependent only on how many portions they serve regardless of the costs of 
labour and/or ingredients used.

I am planning to use projects (analytic accounts) to keep track of 
profitability related to Sale Orders that will be invoiced based od delivered 
quantities (of portions). Now I am scratching my head as on how to consume 
storable stock (ingredients) in a way that its value would be added as a cost 
to the project. Internal transfers? Purchase Order within the organization?

The cost of staff should be possible to be dealt with with timesheets. Is that 
so?

Any advice is highly welcome. Thank you

Best regards

	Radovan Skolnik
    by Radovan Skolnik - 08:40 - 7 Feb 2024

    3 replies 3 replies

    • Re: Consuming stock internally while using the its costs in project 
      Graeme & others,

thank you for your input. I went for option 2. and it seems to be working. I have wanted to keep this tied to the project as other inputs affect profitability (timesheets for example) and it is created from sale order. The general scenario is:

1. I use OCA stock_analytic and stock_picking_analytic modules to get analytic distribution into stock.picking and stock.move and stock.move.line
2. I have created a scrap location representing the kitchen where I consume/expense/scrap the ingredients
3. I have an automatic inventory valuation setup (AVCO but I guess would work with any other)
4. I have created a module that includes valuation records for scrap operations into project profitability.

So when I want to expens the ingredients I create an stock picking to the scrap (kitchen) location using the project's analytical tag. The ingredients will get scrapped creating a negative valuation record with analytic distribution from the stock picking. The project module adds account.analytic.lines (the valuation) records with (quite naive but works) domain like this into profitability calculation: 

            ("account_id", "=", self.analytic_account_id.id),
            (
                "move_line_id.move_id.stock_move_id.location_dest_id.usage",
                "=",
                "inventory",
            ),
            ("category", "!=", "manufacturing_order"),

Any comments on this are welcome. I have migrated stock_analytic and stock_picking_analytic to 17.0 and will open PRs soon. If there was an interest into my module I will gladly donate to OCA.

Best regards

	Radovan Skolnik

On streda 7. februára 2024 21:12:41 CET Graeme Gellatly wrote:

> There are a couple of things I can think of.

> 1. Manufacturing Orders - ingredients as raw materials, portions as outputs,

> workorders as labour. Delivery Order for what is delivered, Analytic

> Accounts on sale. Can be done with/without projects. Will add up all your

> costs. 2. Stock locations - this is not quite the same fit, but many times

> I have faced scenarios where stocked goods are required for internal

> projects and the easiest way has been a stock transfer to a location with a

> different account set. Analytics could be added to both manufacturing and

> stock easily enough and I believe OCA has modules to do so. Also for

> linking MO's to projects. If you had a separate product / customer and used

> anglosaxon you would end up with effectively actual cost, unfortunately

> actual cost is an Odoo Enterprise only direct from Odoo feature at the

> moment, but for something this basic it could be done quite simply.

> Otherwise you could use average cost and rely on analytics/other reporting

> for actuals. On Thu, Feb 8, 2024 at 8:41 AM Radovan Skolnik <

> notifications@odoo-community.org [1] > wrote: Hello,

> I am dealing with a customer who provides catering services. The price is

> dependent only on how many portions they serve regardless of the costs of

> labour and/or ingredients used.

> I am planning to use projects (analytic accounts) to keep track of

> profitability related to Sale Orders that will be invoiced based od

> delivered quantities (of portions). Now I am scratching my head as on how

> to consume storable stock (ingredients) in a way that its value would be

> added as a cost to the project. Internal transfers? Purchase Order within

> the organization? The cost of staff should be possible to be dealt with

> with timesheets. Is that so?

> Any advice is highly welcome. Thank you

> 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 - 10:31 - 12 Feb 2024
    • Re: Consuming stock internally while using the its costs in project
      I've done something quite similar, and the report part on project overview was quite a headache!

      In my use cases I Haven't use stock at all, only consumable product that user are able to report from task or in a new list view likes timesheets.

      The branch (for Odoo 14.0) was stalled but this is still in production and working pretty well https://github.com/OCA/project/pull/814

      So based on this work, setting your stockable product as  `project_ok` and generating analytic lines somehow while consuming the product seems a good solution to mee.

      Hope this can help !



      Le mer. 7 févr. 2024 à 21:12, Graeme Gellatly <notifications@odoo-community.org> a écrit :
      There are a couple of things I can think of.

      1. Manufacturing Orders - ingredients as raw materials, portions as outputs, workorders as labour. Delivery Order for what is delivered, Analytic Accounts on sale. Can be done with/without projects. Will add up all your costs.
      2. Stock locations - this is not quite the same fit, but many times I have faced scenarios where stocked goods are required for internal projects and the easiest way has been a stock transfer to a location with a different account set. 

      Analytics could be added to both manufacturing and stock easily enough and I believe OCA has modules to do so. Also for linking MO's to projects. If you had a separate product / customer and used anglosaxon you would end up with effectively actual cost, unfortunately actual cost is an Odoo Enterprise only direct from Odoo feature at the moment, but for something this basic it could be done quite simply. Otherwise you could use average cost and rely on analytics/other reporting for actuals.

      On Thu, Feb 8, 2024 at 8:41 AM Radovan Skolnik <notifications@odoo-community.org> wrote:
      Hello,

I am dealing with a customer who provides catering services. The price is 
dependent only on how many portions they serve regardless of the costs of 
labour and/or ingredients used.

I am planning to use projects (analytic accounts) to keep track of 
profitability related to Sale Orders that will be invoiced based od delivered 
quantities (of portions). Now I am scratching my head as on how to consume 
storable stock (ingredients) in a way that its value would be added as a cost 
to the project. Internal transfers? Purchase Order within the organization?

The cost of staff should be possible to be dealt with with timesheets. Is that 
so?

Any advice is highly welcome. Thank you

Best regards

	Radovan Skolnik

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

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



      --
      Pierre
      by Pierre Verkest - 01:31 - 8 Feb 2024
    • Re: Consuming stock internally while using the its costs in project
      There are a couple of things I can think of.

      1. Manufacturing Orders - ingredients as raw materials, portions as outputs, workorders as labour. Delivery Order for what is delivered, Analytic Accounts on sale. Can be done with/without projects. Will add up all your costs.
      2. Stock locations - this is not quite the same fit, but many times I have faced scenarios where stocked goods are required for internal projects and the easiest way has been a stock transfer to a location with a different account set. 

      Analytics could be added to both manufacturing and stock easily enough and I believe OCA has modules to do so. Also for linking MO's to projects. If you had a separate product / customer and used anglosaxon you would end up with effectively actual cost, unfortunately actual cost is an Odoo Enterprise only direct from Odoo feature at the moment, but for something this basic it could be done quite simply. Otherwise you could use average cost and rely on analytics/other reporting for actuals.

      On Thu, Feb 8, 2024 at 8:41 AM Radovan Skolnik <notifications@odoo-community.org> wrote:
      Hello,

I am dealing with a customer who provides catering services. The price is 
dependent only on how many portions they serve regardless of the costs of 
labour and/or ingredients used.

I am planning to use projects (analytic accounts) to keep track of 
profitability related to Sale Orders that will be invoiced based od delivered 
quantities (of portions). Now I am scratching my head as on how to consume 
storable stock (ingredients) in a way that its value would be added as a cost 
to the project. Internal transfers? Purchase Order within the organization?

The cost of staff should be possible to be dealt with with timesheets. Is that 
so?

Any advice is highly welcome. Thank you

Best regards

	Radovan Skolnik

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

      by "Graeme Gellatly" <graeme@moahub.nz> - 09:11 - 7 Feb 2024
  • Updating translations

    Hi,


    Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


    In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


    In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


    Kind regards, Ronald


    by "Ronald Portier" <rportier@therp.nl> - 01:36 - 7 Feb 2024

    5 replies 5 replies

    • Re: Updating translations

      Hi Ronald,

      to complete Stéphane answer, you can have a look at the slides from the presentation I gave on Weblate during last OCA days : https://cloud.le-filament.com/s/4tdqw6xFxZs27BD

      You get the workflow on page 10.


      To sum up, Weblate waits for 2h before sending translations (in order to group as many translations as possible in a single commit). If needed you can force push updates using Web interface.


      With respect to nl_NL we had the same issue with French where we add both fr and fr_FR. fr_FR should not be used anymore and only fr should be used (+ fr_BE or fr_CA or fr_CH for delta translation for these localized versions of French language). As far as I remember I think Alexis produced a script to remove all fr_FR translations from repos a few months back.

      Probably you may want to apply the same (using only nl for Netherlands, discarding nl_NL, and maybe nl_BE only for specific terms used in Belgium) ?

      As Stéphane mentioned, the .po file that ends up in module code is generated by Weblate directly, so you need to be careful when you create a new translation in Weblate to use Dutch and not Dutch (nl_NL).


      Best Regards,

      Rémi


      Le 07/02/2024 à 16:56, Stéphane Bidoul a écrit :
      Hi Ronald,

      > Would still like to know how this works anyway.

      Weblate pushes translations back to GitHub "a few times a day". I don't remember the exact configuration.

      > Another problem is that I do not actually intent to use a language variant (nl_NL, Dutch as in the Netherlands), but just Dutch (nl). I actually have to rename nl_NL.po to nl.po in my instance, otherwise the language will not load at all.
      > Is it in any way possible to configure the settings on the translation server to generate / update the nl.po file instead of nl_NL.po?

      Actually weblate does not generate nl.po nor nl_NL.po. It's the translators who chose which one to create and use.

      Best regards,

      -Stéphane


      On Wed, Feb 7, 2024 at 4:32 PM Ronald Portier <notifications@odoo-community.org> wrote:

      Hi,


      Indeed after a few hours the nl_NL.po file is refreshed. Would still like to know how this works anyway.


      Another problem is that I do not actually intent to use a language variant (nl_NL, Dutch as in the Netherlands), but just Dutch (nl). I actually have to rename nl_NL.po to nl.po in my instance, otherwise the language will not load at all.


      Is it in any way possible to configure the settings on the translation server to generate / update the nl.po file instead of nl_NL.po?


      Kind regards, Ronald


      On 07-02-2024 14:36, Enric Tobella Alomar wrote:
      You should wait some time before it is sent.

      I think it is already there :D

      Kind regards,

      El mié, 7 feb 2024 a las 14:22, Stefano Consolaro (<notifications@odoo-community.org>) escribió:
      Hi Ronald,
      what I know is that it takes some time from the Weblate server to be tranfered on GitHub.
      So wait some hours and then check if the nl_NL.po file is updated.

      Cc
      Data Wed, 07 Feb 2024 12:37:22 -0000
      Oggetto Updating translations

      Hi,


      Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


      In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


      In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


      Kind regards, Ronald


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



      Stefano Consolaro

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



      --
      Enric Tobella Alomar
      CEO & Founder

      _______________________________________________
      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 Rémi Cazenave - 12:11 - 8 Feb 2024
    • Re: Updating translations
      Hi Ronald,

      > Would still like to know how this works anyway.

      Weblate pushes translations back to GitHub "a few times a day". I don't remember the exact configuration.

      > Another problem is that I do not actually intent to use a language variant (nl_NL, Dutch as in the Netherlands), but just Dutch (nl). I actually have to rename nl_NL.po to nl.po in my instance, otherwise the language will not load at all.
      > Is it in any way possible to configure the settings on the translation server to generate / update the nl.po file instead of nl_NL.po?

      Actually weblate does not generate nl.po nor nl_NL.po. It's the translators who chose which one to create and use.

      Best regards,

      -Stéphane


      On Wed, Feb 7, 2024 at 4:32 PM Ronald Portier <notifications@odoo-community.org> wrote:

      Hi,


      Indeed after a few hours the nl_NL.po file is refreshed. Would still like to know how this works anyway.


      Another problem is that I do not actually intent to use a language variant (nl_NL, Dutch as in the Netherlands), but just Dutch (nl). I actually have to rename nl_NL.po to nl.po in my instance, otherwise the language will not load at all.


      Is it in any way possible to configure the settings on the translation server to generate / update the nl.po file instead of nl_NL.po?


      Kind regards, Ronald


      On 07-02-2024 14:36, Enric Tobella Alomar wrote:
      You should wait some time before it is sent.

      I think it is already there :D

      Kind regards,

      El mié, 7 feb 2024 a las 14:22, Stefano Consolaro (<notifications@odoo-community.org>) escribió:
      Hi Ronald,
      what I know is that it takes some time from the Weblate server to be tranfered on GitHub.
      So wait some hours and then check if the nl_NL.po file is updated.

      Cc
      Data Wed, 07 Feb 2024 12:37:22 -0000
      Oggetto Updating translations

      Hi,


      Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


      In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


      In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


      Kind regards, Ronald


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



      Stefano Consolaro

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



      --
      Enric Tobella Alomar
      CEO & Founder

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

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

      by Stéphane Bidoul - 04:51 - 7 Feb 2024
    • Re: Updating translations

      Hi,


      Indeed after a few hours the nl_NL.po file is refreshed. Would still like to know how this works anyway.


      Another problem is that I do not actually intent to use a language variant (nl_NL, Dutch as in the Netherlands), but just Dutch (nl). I actually have to rename nl_NL.po to nl.po in my instance, otherwise the language will not load at all.


      Is it in any way possible to configure the settings on the translation server to generate / update the nl.po file instead of nl_NL.po?


      Kind regards, Ronald


      On 07-02-2024 14:36, Enric Tobella Alomar wrote:
      You should wait some time before it is sent.

      I think it is already there :D

      Kind regards,

      El mié, 7 feb 2024 a las 14:22, Stefano Consolaro (<notifications@odoo-community.org>) escribió:
      Hi Ronald,
      what I know is that it takes some time from the Weblate server to be tranfered on GitHub.
      So wait some hours and then check if the nl_NL.po file is updated.

      Cc
      Data Wed, 07 Feb 2024 12:37:22 -0000
      Oggetto Updating translations

      Hi,


      Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


      In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


      In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


      Kind regards, Ronald


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



      Stefano Consolaro

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



      --
      Enric Tobella Alomar
      CEO & Founder

      _______________________________________________
      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> - 04:31 - 7 Feb 2024
    • Re: Updating translations
      You should wait some time before it is sent.

      I think it is already there :D

      Kind regards,

      El mié, 7 feb 2024 a las 14:22, Stefano Consolaro (<notifications@odoo-community.org>) escribió:
      Hi Ronald,
      what I know is that it takes some time from the Weblate server to be tranfered on GitHub.
      So wait some hours and then check if the nl_NL.po file is updated.

      Cc
      Data Wed, 07 Feb 2024 12:37:22 -0000
      Oggetto Updating translations

      Hi,


      Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


      In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


      In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


      Kind regards, Ronald


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



      Stefano Consolaro

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



      --
      Enric Tobella Alomar
      CEO & Founder

      by Enric Tobella Alomar - 02:35 - 7 Feb 2024
    • Re:Updating translations
      Hi Ronald,
      what I know is that it takes some time from the Weblate server to be tranfered on GitHub.
      So wait some hours and then check if the nl_NL.po file is updated.

      Da "Ronald Portier" notifications@odoo-community.org
      A "Contributors" contributors@odoo-community.org
      Cc
      Data Wed, 07 Feb 2024 12:37:22 -0000
      Oggetto Updating translations

      Hi,


      Can somebody give insight in how translations are moved from https://translation.odoo-community.org to the actual project?


      In my case I translated helpdesk_mgmt to Dutch for 16.0. There is one commit added to helpdesk repo from when I just started the translations (basically just containing the untranslated nl_NL.po file). Translation is complete now, but nothing happens anymore.


      In the past we could just add a po file and put translations in there. I understand this is maybe not so easy for non developers contributing translations, but is this still possible to do as well, or will stuff just be overwritten from the translation website?


      Kind regards, Ronald


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



      Stefano Consolaro
      www.mymage.it
      by Stefano Consolaro - 02:21 - 7 Feb 2024
  • AW: Mounting location of part upon production

    AW: Mounting location of part upon production


    Hey,


    I would give a unique number to every product in stock and put this number in a bar code on the product for witch you need this mounting location.

    Your worker scans the final product ( the chair ) from the work order and he takes the first leg, scans it and put it first position given by the work order. So he can take the legs out the box without any worry and you knows exact with leg is in with position. And it is simple for the worker, taking him little time ( just scan each leg ) and it is not hard to code. Only maybe the work order that have to automaticaly give the positions and write the leg number on the work order ( here I have no experians -) ).


    With kind regards,


    Van Hirtum Johan



    -----Oorspronkelijk bericht-----
    Afzender: Daniel Reis <notifications@odoo-community.org>
    Verstuurd: Maandag 5 Februari 2024 16:02
    Aan: Contributors <contributors@odoo-community.org>
    Onderwerp: Re: Mounting location of part upon production
    Hi Tom,

    Option 2 will be problematic as it introduces artificial restrictions on component usage.
    Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot numbers for this?


    On 05/02/2024 11:57, Tom Blauwendraat wrote:
    Hello,

I'm dealing with a situation where upon production, the mounting 
location of the parts needs to be registered.

Imagine a chair with 4 identical legs, but it needs to be registered 
which leg is placed where: front right, front left, rear right or rear left.

Is there something for this case in Odoo? What I could come up with is:

- Requiring work orders for "leg mounting", and specifying the mount 
location on the work order

- Having separate products eg "Left rear leg" and producing these from 
"Leg" (seems a bit of a hassle)

- Adding a required field on stock move line in case certain products 
are produced, where the mount location is filled in; also enforce 1.0 as 
a quantity

- ...

-Tom

    _______________________________________________
    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

    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 johan - 12:07 - 6 Feb 2024
  • Have you organised your 2024 OCA membership yet?
    Dear OCA-ers and Odooers,

    Read the latest OCA news item about the 2024 OCA membership and purchase process.

    If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.

    I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.

    Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.



    Best regards,


    Michel Stroom

    by Michel Stroom - 09:21 - 5 Feb 2024

    3 replies 3 replies

    • Re: Have you organised your 2024 OCA membership yet?
      Has any thought been given to using GitHub Sponsorships to track membership and collect money?


      On Mon, Feb 5, 2024 at 3:21 PM Michel Stroom <notifications@odoo-community.org> wrote:
      Dear OCA-ers and Odooers,

      Read the latest OCA news item about the 2024 OCA membership and purchase process.

      If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.

      I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.

      Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.



      Best regards,


      Michel Stroom

      _______________________________________________
      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:06 - 9 Feb 2024
    • Re: Have you organised your 2024 OCA membership yet? 
      Thank you, Gijs-Jan, for the coffee invitation, and I will be in contact soon. 
We have almost 500 OCA Members, as Rebecca wrote in the latest OCA news update. 
Let’s try to double this amount to 1000 OCA Members by the end of the year.



> On 5 Feb 2024, at 22:42, Gijs-Jan Otten <notifications@odoo-community.org> wrote:

> 

> Hi Michel,

> 

> I suspect the list will soon be expanded by quite a bit since I can imagine other companies having done the same as we did: process the due invoice on Membership near the end of January via PO, meaning OCA accounting now has to reconcile quite the number of transactions :-)

> 

> In any case, depending on whether or my colleagues and I are all filed away under the same country, we might see an 1100% increase on that NL list!

> 

> If you’re anywhere near Amersfoort we’d be glad to treat you to a coffee.

> 

> Met vriendelijke groet, Sincerely,

> 

> Gijs-Jan Otten

> Therp BV | gjotten@therp.nl | 

> +31 20 309 30 93

> 

>> On 5 Feb 2024, at 21:21, Michel Stroom <notifications@odoo-community.org> wrote:

>> 

>> 

>> Dear OCA-ers and Odooers,

>> 

>> Read the latest OCA news item about the 2024 OCA membership and purchase process.

>> https://odoo-community.org/blog/news-updates-1/oca-membership-2024-153

>> 

>> If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.

>> https://odoo-community.org/shop/24-msm-2024-oca-member-503809#attr=

>> 

>> I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.

>> https://odoo-community.org/members

>> 

>> Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.

>> 

>> 

>> 

>> Best regards,

>> 

>> 

>> Michel Stroom

>> 

>> -- 

>> Office Everywhere

>> t: +31 6 53360677

>> e: mstroom@office-everywhere.com

>> w: Office-Everywhere.com

>> 

>> 

>> 

>> _______________________________________________

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

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

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

> _______________________________________________

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

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

> Unsubscribe: https://odoo-community.org/groups?unsubscribe
      by Michel Stroom - 01:31 - 6 Feb 2024
    • Re: Have you organised your 2024 OCA membership yet?
      Hi Michel,

      I suspect the list will soon be expanded by quite a bit since I can imagine other companies having done the same as we did: process the due invoice on Membership near the end of January via PO, meaning OCA accounting now has to reconcile quite the number of transactions :-)

      In any case, depending on whether or my colleagues and I are all filed away under the same country, we might see an 1100% increase on that NL list!

      If you’re anywhere near Amersfoort we’d be glad to treat you to a coffee.

      Met vriendelijke groet, Sincerely,

      Gijs-Jan Otten
      Therp BV | gjotten@therp.nl | 
      +31 20 309 30 93

      On 5 Feb 2024, at 21:21, Michel Stroom <notifications@odoo-community.org> wrote:

      
      Dear OCA-ers and Odooers,

      Read the latest OCA news item about the 2024 OCA membership and purchase process.

      If you haven’t purchased the 2024 OCA membership yet, help yourself through the website.

      I’m looking forward to seeing more OCA members in the Netherlands folder directory soon.

      Would like to collaborate and increase the Odoo popularity in the Netherlands together with other OCA members in 2024. Please feel free to contact me in the meantime.



      Best regards,


      Michel Stroom

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

      by Gijs-Jan Otten - 10:41 - 5 Feb 2024
  • Please approve PR [17.0][MIG] stock_mts_mto_rule: Migration to 17.0

    Hello,

     

    Please approve my Pull Request

    https://github.com/OCA/stock-logistics-warehouse/pull/1932

    It will take you just 2 minutes!

     

    BR,

    Aleksander Milinkevich

     

    by "Aleksander Milinkevich" <aleksander@versada.eu> - 02:06 - 5 Feb 2024

    3 replies 3 replies

  • Mounting location of part upon production 
    Hello,

I'm dealing with a situation where upon production, the mounting 
location of the parts needs to be registered.

Imagine a chair with 4 identical legs, but it needs to be registered 
which leg is placed where: front right, front left, rear right or rear left.

Is there something for this case in Odoo? What I could come up with is:

- Requiring work orders for "leg mounting", and specifying the mount 
location on the work order

- Having separate products eg "Left rear leg" and producing these from 
"Leg" (seems a bit of a hassle)

- Adding a required field on stock move line in case certain products 
are produced, where the mount location is filled in; also enforce 1.0 as 
a quantity

- ...

-Tom
    by Tom Blauwendraat - 12:57 - 5 Feb 2024

    7 replies 7 replies

    • Re: Mounting location of part upon production
      Hi Tom,
      You should be able to have each of the items (specified legs) be on one BOM and when the Manufacturing order is created, you select the serial numbers being used on those individual line items.

      I might need to build up a test case to be able to show you, and I should check to see what modules I have running that are beyond standard to enable that.

      I would be happy to connect directly.  If I build a test case I could likely share a video or some images.
      I should add, perhaps I am wrong,  but this seems pretty doable.  If not doable, it should be.

      Landis

      Landis Arnold
      Nomadic Inc.
      Niwot, CO USA

      larnold@nomadic.net


      From: "Tom Blauwendraat" <notifications@odoo-community.org>
      To: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Sent: Friday, February 16, 2024 7:31:46 AM
      Subject: Re: Mounting location of part upon production

      On 2/16/24 15:17, Landis Arnold wrote:


>


> One way to accomplish some of this is to simply use "structured 


> serialization".


> If you were to apply  to your Chair use case, you might do the following:


>


> 200 Legs become 200 serialized items.


> In your BOM you would apply a Top Down with Chair, Leg position 1, 2, 


> 3 and 4, Other components


> Focusing on the Leg Positions:  Basically a BOM for each would allow 


> the Serialized Legs to be used for their source.


> You would Select a Serial Number for each in the BOM positions for 


> each (leg1, leg2, leg3, leg4)

Hi Landis,

this sounds exactly like what I need, but I'm not sure that I follow - 
if you say you need a "bom for each", then you basically mean defining 
each leg as a separate product, which you include in the main BoM; so 
there's a production step in between where a leg becomes a leg1, and 
then becomes part of the table. Am I right? Or are you talking about 
some other kind of serialization, that I don't yet know about?

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


      by Landis Arnold - 06:51 - 16 Feb 2024
    • Re: Mounting location of part upon production 
      On 2/16/24 15:17, Landis Arnold wrote:

>

> One way to accomplish some of this is to simply use "structured 

> serialization".

> If you were to apply  to your Chair use case, you might do the following:

>

> 200 Legs become 200 serialized items.

> In your BOM you would apply a Top Down with Chair, Leg position 1, 2, 

> 3 and 4, Other components

> Focusing on the Leg Positions:  Basically a BOM for each would allow 

> the Serialized Legs to be used for their source.

> You would Select a Serial Number for each in the BOM positions for 

> each (leg1, leg2, leg3, leg4)

Hi Landis,

this sounds exactly like what I need, but I'm not sure that I follow - 
if you say you need a "bom for each", then you basically mean defining 
each leg as a separate product, which you include in the main BoM; so 
there's a production step in between where a leg becomes a leg1, and 
then becomes part of the table. Am I right? Or are you talking about 
some other kind of serialization, that I don't yet know about?
      by Tom Blauwendraat - 03:30 - 16 Feb 2024
    • Re: Mounting location of part upon production
      Perhaps related to your request Tom,
      I have worked through something "similar" to this recently.  My use case involved "halves" of a paddle tracked by incoming lots,  right and left side, weights and lengths, and quality.
      The objective of the process was to primarily match pairs, such that left and right side would be balanced,  we would know the combined maximum length of the two sides, and we would flush out any blemishes, and in fact also try to pair blemishes.

      I used Serialization of Incoming as well as BOM processes for this.
      In parallel I built a system in Filemaker which would allow quick sorting of weights/lengths etc.  That sorting allowed relatively simple processing of components into pairs.  Then at time of final build the pairs are combined to built paddle in specific length, twists and control hand specifications.
      Back in Odoo, the traceability report shows the full flow of components used in each paddle.  In the Inventory/Warehouse App, if you look at Serial Numbers. then unselect "product" in the filter/search box, you can then see all of the serial numbers and if used, where they have been used.  This would go "up or down" in terms of a flow from initial part, paired part, built part.

      -------

      But about your Chair and Chair Leg approach.

      One way to accomplish some of this is to simply use "structured serialization".  
      If you were to apply  to your Chair use case, you might do the following:

      200 Legs become 200 serialized items.
      In your BOM you would apply a Top Down with Chair, Leg position 1, 2, 3 and 4, Other components
      Focusing on the Leg Positions:  Basically a BOM for each would allow the Serialized Legs to be used for their source.
      You would Select a Serial Number for each in the BOM positions for each (leg1, leg2, leg3, leg4)  

      ----
      I have been doing this with Odoo 14  Community.    There could definitely be different/better reports for some of this, but if you look well enough, and jump to the correct app, most things are findable.

      I hope that some of this above may be helpful.

      Landis Arnold

      Nomadic Inc.
      Niwot, CO USA

      From: "Tom Blauwendraat" <notifications@odoo-community.org>
      To: "Odoo Community Association, (OCA) Contributors" <contributors@odoo-community.org>
      Sent: Tuesday, February 6, 2024 1:17:27 PM
      Subject: Re: Mounting location of part upon production

      That could indeed be a nice idea - based on where the leg is placed at the moment, we modify a field on the serial number indicating the position.
      That said, maybe it could then also be an extra field that we store the information on in stock.move or stock.quant table, to avoid write traffic on the lot table. Let me think about that some more.

      Thanks, Graeme!

      Therp - Open Source ERP solutions built on Odoo

      On 6 Feb 2024, at 12:22, Graeme Gellatly <notifications@odoo-community.org> wrote:

      Yes, but there is a second field on serials, I don't recall its name, but I use it a lot to store information and lot names are surprisingly accessible during manufacturing processes. I wouldn't discount the idea, it is a pretty simple workaround.

      On Tue, Feb 6, 2024 at 5:42 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:
      On 2/5/24 16:02, Daniel Reis wrote:



> Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot 



> numbers for this?

Good idea in theory, but in my case we're already using serial numbers 
to track the parts

      _______________________________________________
      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 Landis Arnold - 03:16 - 16 Feb 2024
    • Re: Mounting location of part upon production
      That could indeed be a nice idea - based on where the leg is placed at the moment, we modify a field on the serial number indicating the position.

      That said, maybe it could then also be an extra field that we store the information on in stock.move or stock.quant table, to avoid write traffic on the lot table. Let me think about that some more.

      Thanks, Graeme!

      Therp - Open Source ERP solutions built on Odoo

      On 6 Feb 2024, at 12:22, Graeme Gellatly <notifications@odoo-community.org> wrote:

      Yes, but there is a second field on serials, I don't recall its name, but I use it a lot to store information and lot names are surprisingly accessible during manufacturing processes. I wouldn't discount the idea, it is a pretty simple workaround.

      On Tue, Feb 6, 2024 at 5:42 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:
      On 2/5/24 16:02, Daniel Reis wrote:


> Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot 


> numbers for this?

Good idea in theory, but in my case we're already using serial numbers 
to track the parts

      _______________________________________________
      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 - 09:16 - 6 Feb 2024
    • Re: Mounting location of part upon production
      Yes, but there is a second field on serials, I don't recall its name, but I use it a lot to store information and lot names are surprisingly accessible during manufacturing processes. I wouldn't discount the idea, it is a pretty simple workaround.

      On Tue, Feb 6, 2024 at 5:42 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:
      On 2/5/24 16:02, Daniel Reis wrote:


> Option 3 looks similar to Lot/Serial usage. What if you (ab)used Lot 


> numbers for this?

Good idea in theory, but in my case we're already using serial numbers 
to track the parts

      _______________________________________________
      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> - 12:20 - 6 Feb 2024

  • Travis sunset
    Hi everyone,

    As previously announced we have cancelled the OCA Travis subscription.

    This means Travis CI tests will stop working in OCA repos mid February.

    Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

    Best regards,

    -Stéphane
    by Stéphane Bidoul - 11:21 - 3 Feb 2024

    3 replies 3 replies

    • Re: Travis sunset

      Hi,


      With some limitations it is possible to use github actions for older versions. Check the 9.0 branch of the Dutch localization: https://github.com/OCA/l10n-netherlands/tree/9.0. The move from .travis to .github actions is in the last 4 commits.


      Kind regards, Ronald


      On 05-02-2024 15:17, Adam Heinz wrote:
      I cringe a bit at the idea of removing automated testing. Is there some reason that it doesn't make sense to migrate these old versions to runboat or some other build tool? If it is a matter of cost, "GitHub Actions usage is free for standard GitHub-hosted runners in public repositories" [1].


      On Sun, Feb 4, 2024 at 5:59 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:

      Nice progress, Stephane!

      This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

      --> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

      Should we:

      A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

      B. Refuse complex PR's; manually merge in smaller or bugfix PR's

      C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

      D. Any of the above, as agreed as a policy between the PSC's of the particular repo

      I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

      -Tom

      On 2/3/24 11:22, Stéphane Bidoul wrote:
      Hi everyone,

      As previously announced we have cancelled the OCA Travis subscription.

      This means Travis CI tests will stop working in OCA repos mid February.

      Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

      Best regards,

      -Stéphane

      _______________________________________________
      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> - 03:41 - 5 Feb 2024
    • Re: Travis sunset
      I cringe a bit at the idea of removing automated testing. Is there some reason that it doesn't make sense to migrate these old versions to runboat or some other build tool? If it is a matter of cost, "GitHub Actions usage is free for standard GitHub-hosted runners in public repositories" [1].


      On Sun, Feb 4, 2024 at 5:59 AM Tom Blauwendraat <notifications@odoo-community.org> wrote:

      Nice progress, Stephane!

      This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

      --> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

      Should we:

      A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

      B. Refuse complex PR's; manually merge in smaller or bugfix PR's

      C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

      D. Any of the above, as agreed as a policy between the PSC's of the particular repo

      I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

      -Tom

      On 2/3/24 11:22, Stéphane Bidoul wrote:
      Hi everyone,

      As previously announced we have cancelled the OCA Travis subscription.

      This means Travis CI tests will stop working in OCA repos mid February.

      Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

      Best regards,

      -Stéphane

      _______________________________________________
      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 "Adam Heinz" <adam.heinz@metricwise.com> - 03:16 - 5 Feb 2024
    • Re: Travis sunset

      Nice progress, Stephane!

      This is a good hook for me to ask a question that I had, based on the previous discussion around stopping support for Python 2 and Odoo <10.0:

      --> How should PSC's deal (from now on) with incoming PR's for Odoo 8.0 and 9.0? (And maybe 10.0 as well)

      Should we:

      A. Refuse/close any incoming PR's, citing unsupported version (Odoo SA method); perhaps even lock branches on repos

      B. Refuse complex PR's; manually merge in smaller or bugfix PR's

      C. Treat PR's like any PR, just without CI, so we merge manually when there are enough approving reviews

      D. Any of the above, as agreed as a policy between the PSC's of the particular repo

      I guess opinions might differ on this, perhaps if people want to chip in with their particular preference and vote?

      -Tom

      On 2/3/24 11:22, Stéphane Bidoul wrote:
      Hi everyone,

      As previously announced we have cancelled the OCA Travis subscription.

      This means Travis CI tests will stop working in OCA repos mid February.

      Older branches that still use Travis can be converted to GitHub actions by applying the OCA repo template [1]. Odoo >= 11 is supported.

      Best regards,

      -Stéphane

      _______________________________________________
      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 - 11:59 - 4 Feb 2024