Archives
- By thread 1419
-
By date
- August 2019 59
- September 2019 118
- October 2019 165
- November 2019 97
- December 2019 35
- January 2020 58
- February 2020 204
- March 2020 121
- April 2020 172
- May 2020 50
- June 2020 158
- July 2020 85
- August 2020 94
- September 2020 193
- October 2020 277
- November 2020 100
- December 2020 159
- January 2021 38
- February 2021 87
- March 2021 146
- April 2021 73
- May 2021 90
- June 2021 86
- July 2021 123
- August 2021 50
- September 2021 68
- October 2021 66
- November 2021 74
- December 2021 75
- January 2022 98
- February 2022 77
- March 2022 68
- April 2022 31
- May 2022 59
- June 2022 87
- July 2022 141
- August 2022 38
- September 2022 73
- October 2022 152
- November 2022 39
- December 2022 50
- January 2023 93
- February 2023 49
- March 2023 106
- April 2023 47
- May 2023 69
- June 2023 92
- July 2023 64
- August 2023 103
- September 2023 91
- October 2023 101
- November 2023 94
- December 2023 46
- January 2024 75
- February 2024 79
- March 2024 104
- April 2024 63
- May 2024 40
- June 2024 160
- July 2024 80
- August 2024 70
- September 2024 62
- October 2024 121
- November 2024 117
- December 2024 89
- January 2025 59
- February 2025 104
- March 2025 96
- April 2025 107
- May 2025 52
- June 2025 72
- July 2025 60
- August 2025 81
- September 2025 124
- October 2025 63
- November 2025 22
Contributors
-
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,AlexeyOn 4 Mar 2024, at 16:37, Radovan Skolnik <notifications@odoo-community.org> wrote:Hi,what about this one: https://github.com/OCA/sale-workflow/tree/14.0/sale_restricted_qty ? There is PR for 16.0: https://github.com/OCA/sale-workflow/pull/2757In cobination with UoM of 10 I think it could work.Best regards   RadovanOn 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: 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 -
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 -
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: 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: 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,FlorianLe 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 updatebad 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 updatebad 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 -
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 BalleriniIl 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: ERROR: could not serialize access due to concurrent update (case using Job Queue)
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 updatebad 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
by "Adam Heinz" <adam.heinz@metricwise.com> - 02:35 - 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 updatebad 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 -
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,AlexeyOn 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 -
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: Product qty constraints for services
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
by Radovan Skolnik - 11:06 - 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 -
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Â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
by Francesco Ballerini - 03:01 - 3 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
by Francesco Ballerini - 02:31 - 3 Mar 2024