Skip to Content
  2. Mailing Lists
  3. Contributors

Archives

  • Sale Workflow v14
    Hi all,

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

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

    Best wishes for 2022!


    --

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


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel. - 03:46 - 10 Jan 2022

    3 replies 3 replies

  • Odoo v14 - Bank reconciliation flow
    Hello All

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

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

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

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

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

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

    Have a great day. 


    Julien Jézéquel-Bréard - Chargé de projets
    NUMIGI SOLUTIONS INC.


    Longueuil, Québec, Canada

    linkedinyoutubecustom-icontwitter

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

    2 replies 2 replies

    • Re: Odoo v14 - Bank reconciliation flow 
      Hi Julien,

what Graeme is saying is what Odoo put here

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

at 1:30 ff 

Best Frederik

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

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

> 

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

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

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

> account the same.

> 

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

> julien.jezequel@numigi.com> wrote:

> > Hello All

> > 

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

> > your projects.

> > 

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

> > V14. 

> > 

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

> > the systematic use of transit accounts on payments. 

> > 

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

> > direct and simple way of managing payments and bank

> > reconciliation. 

> > 

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

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

> > share on this matter. 

> > 

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

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

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

> > analysis in progress. 

> > 

> > Have a great day. 

> > 

> > 

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

> > NUMIGI SOLUTIONS INC.

> > julien.jezequel@numigi.com

> > 

> > 

> > Longueuil, Québec, Canada

> > http://www.numigi.com/

> > 

> > 			

> > 

> > _______________________________________________

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

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

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

> 

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer. - 12:11 - 8 Jan 2022
    • Re: Odoo v14 - Bank reconciliation flow
      Just watch the official Odoo video on how to do this.

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

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

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

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

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

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

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

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

      Have a great day. 


      Julien Jézéquel-Bréard - Chargé de projets
      NUMIGI SOLUTIONS INC.


      Longueuil, Québec, Canada

      linkedinyoutubecustom-icontwitter

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

      by Graeme Gellatly - 11:51 - 7 Jan 2022
  • stock: Retroactively removing lots from incompatible products in stock move history 
    Hi all,

I'm a little bit new to Odoo, so please bear with me if I don't get
everything right, but I've been told that I have struck a difficult
bug.

TL:DR: Having removed the lot_id from certain rows (products that are
incompatible with that lot) in stock_move_line and stock_quant, how do
I know I haven't broken something?


I have a database that was migrated from Odoo 9 to Odoo 12. Before the
migration, there was a bug that assigned lots to by-products of a
dismantling operation (in this case, empty bottles were assigned the
lots of full bottles of wine).

As a result, during inventory on Odoo 12, the error message from
StockMoveLine._check_lot_product() shows up, correctly identifying that
these various lots are incompatible with empty bottles, then aborting
the validation.

Because these lots were added in error, I want to remove them from all
past stock moves. This cannot be done through the UI, so I've made
these SQL statements to get it done:

```
update stock_move_line 
set lot_id = null, lot_name = null
where product_id in (67, 38, 29) and lot_id is not null;

update stock_quant
set lot_id = null
where product_id in (67, 38, 29) and lot_id is not null;
```

(the product_ids here are empty bottles)

Having run the above on a test/staging database, I can now do the
inventory without troubles. I have also verified that the quantities in
the inventory have correctly added up (the quantities of bottles that
previously had lots are added to the lot-less bottles). The quantities
on the `product.product` view have remained the same, which makes sense
to me. I have also triggered `_compute_quantities()` for
'product.product', and nothing has changed.

Although everything works and my problems seem to have disappeared, the
problem is that I do not know whether I have inadvertently corrupted
the (test!) database. I've been reading the source code of the stock
module to find interactions with lot_id and lot_name, but I've not
really found anything troubling.

Does my approach make sense? Is there anything I can do to verify the
integrity of what I've done?

Many thanks and best regards,

Carmen Bianca Bakker
Coop IT Easy
    by Carmen Bianca Bakker - 10:46 - 7 Jan 2022

    4 replies 4 replies

    • Re: stock: Retroactively removing lots from incompatible products in stock move history
      Oh FYI,

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

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

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

      move_line_ids = []
      move_line_to_recompute_ids = []

      logging = ''

      for quant in quants:

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

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

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

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

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

      move_lines_to_unreserve = []

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

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

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

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

      Or if database is large/many users I create a Server Action on Product secured to inventory manager with an action
      if records:
          quants = env['stock.quant'].sudo().search([('product_id', 'in', records.ids)])
         
          move_line_ids = []
          move_line_to_recompute_ids = []
         
          logging = ''
         
          for quant in quants:
         
              move_lines = env['stock.move.line'].search([
                  ('product_id', '=', quant.product_id.id),
                  ('location_id', '=', quant.location_id.id),
                  ('lot_id', '=', quant.lot_id.id),
                  ('package_id', '=', quant.package_id.id),
                  ('owner_id', '=', quant.owner_id.id),
                  ('product_qty', '!=', 0),
                  ])
         
              move_line_ids += move_lines.ids
              reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
              move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])
         
              if quant.location_id.should_bypass_reservation():
                  # If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
                  # should be 0.
                  if quant.reserved_quantity != 0:
                      logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                      logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
                      if move_lines:
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                      else:
                          logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
                      logging += '******************\n'
                      quant.write({'reserved_quantity': 0})
              else:
                  # If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
                  # of the `product_qty` of all the partially_available / assigned move lines with the same
                  # characteristics.
         
                  if quant.reserved_quantity == 0:
                      if move_lines:
                          logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                          logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          logging += '******************\n'
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                  elif quant.reserved_quantity < 0:
                      logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                      logging += "its `reserved_quantity` field is negative while it should not happen\n"
                      quant.write({'reserved_quantity': 0})
                      if move_lines:
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                      logging += '******************\n'
                  else:
                      if reserved_on_move_lines != quant.reserved_quantity:
                          logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                          logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          logging += '******************\n'
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                          quant.write({'reserved_quantity': 0})
                      else:
                          if any(move_line.product_qty < 0 for move_line in
                                 move_lines):
                              logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                              logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
                              logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                              logging += '******************\n'
                              move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                              move_line_to_recompute_ids += move_lines.ids
                              quant.write({'reserved_quantity': 0})
         
          move_lines = env['stock.move.line'].search([('product_id.type', '=',
                  'product'), ('product_qty', '!=', 0), ('id', 'not in',
                  move_line_ids), ('product_id', 'in', records.ids)])
         
          move_lines_to_unreserve = []
         
          for move_line in move_lines:
              if not move_line.location_id.should_bypass_reservation():
                  logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
                  logging += "There is no exiting quants despite its `reserved_quantity`\n"
                  logging += '******************\n'
                  move_lines_to_unreserve.append(move_line.id)
                  move_line_to_recompute_ids.append(move_line.id)
         
          if len(move_lines_to_unreserve) > 0:
              env.cr.execute("""
                      UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
                  """
                             % (tuple(move_lines_to_unreserve), ))
         
          if logging:
              env['ir.logging'].sudo().create({
                  'name': 'Unreserve stock.quant and stock.move.line',
                  'type': 'server',
                  'level': 'INFO',
                  'dbname': env.cr.dbname,
                  'message': logging,
                  'func': '_update_reserved_quantity',
                  'path': 'addons/stock/models/stock_quant.py',
                  'line': '0',
              })
         
          if move_line_to_recompute_ids:
              env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

      On Fri, 7 Jan 2022, 11:27 pm Carmen Bianca Bakker, <carmen@coopiteasy.be> wrote:
      Hello,

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

With kindness,
Carmen

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

      by Graeme Gellatly - 11:51 - 7 Jan 2022
    • Re: stock: Retroactively removing lots from incompatible products in stock move history
      Personally if they are meant to have lots I wouldn't null them. Just create them new ones and set.

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

      move_line_ids = []
      move_line_to_recompute_ids = []

      logging = ''

      for quant in quants:

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

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

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

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

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

      move_lines_to_unreserve = []

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

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

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

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

      Or if database is large/many users I create a Server Action on Product secured to inventory manager with an action
      if records:
          quants = env['stock.quant'].sudo().search([('product_id', 'in', records.ids)])
         
          move_line_ids = []
          move_line_to_recompute_ids = []
         
          logging = ''
         
          for quant in quants:
         
              move_lines = env['stock.move.line'].search([
                  ('product_id', '=', quant.product_id.id),
                  ('location_id', '=', quant.location_id.id),
                  ('lot_id', '=', quant.lot_id.id),
                  ('package_id', '=', quant.package_id.id),
                  ('owner_id', '=', quant.owner_id.id),
                  ('product_qty', '!=', 0),
                  ])
         
              move_line_ids += move_lines.ids
              reserved_on_move_lines = sum(move_lines.mapped('product_qty'))
              move_line_str = str.join(', ', [str(move_line_id) for move_line_id in move_lines.ids])
         
              if quant.location_id.should_bypass_reservation():
                  # If a quant is in a location that should bypass the reservation, its `reserved_quantity` field
                  # should be 0.
                  if quant.reserved_quantity != 0:
                      logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                      logging += "its `reserved_quantity` field is not 0 while its location should bypass the reservation\n"
                      if move_lines:
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                      else:
                          logging += "no move lines are reserved on it, you can safely reset its `reserved_quantity` to 0\n"
                      logging += '******************\n'
                      quant.write({'reserved_quantity': 0})
              else:
                  # If a quant is in a reservable location, its `reserved_quantity` should be exactly the sum
                  # of the `product_qty` of all the partially_available / assigned move lines with the same
                  # characteristics.
         
                  if quant.reserved_quantity == 0:
                      if move_lines:
                          logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                          logging += "its `reserved_quantity` field is 0 while these move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          logging += '******************\n'
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                  elif quant.reserved_quantity < 0:
                      logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                      logging += "its `reserved_quantity` field is negative while it should not happen\n"
                      quant.write({'reserved_quantity': 0})
                      if move_lines:
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                      logging += '******************\n'
                  else:
                      if reserved_on_move_lines != quant.reserved_quantity:
                          logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                          logging += "its `reserved_quantity` does not reflect the move lines reservation\n"
                          logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                          logging += '******************\n'
                          move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                          move_line_to_recompute_ids += move_lines.ids
                          quant.write({'reserved_quantity': 0})
                      else:
                          if any(move_line.product_qty < 0 for move_line in
                                 move_lines):
                              logging += "Problematic quant found: %s (quantity: %s, reserved_quantity: %s)\n" % (quant.id, quant.quantity, quant.reserved_quantity)
                              logging += "its `reserved_quantity` correctly reflects the move lines reservation but some are negatives\n"
                              logging += "These move lines are reserved on it: %s (sum of the reservation: %s)\n" % (move_line_str, reserved_on_move_lines)
                              logging += '******************\n'
                              move_lines.with_context(bypass_reservation_update=True).sudo().write({'product_uom_qty': 0})
                              move_line_to_recompute_ids += move_lines.ids
                              quant.write({'reserved_quantity': 0})
         
          move_lines = env['stock.move.line'].search([('product_id.type', '=',
                  'product'), ('product_qty', '!=', 0), ('id', 'not in',
                  move_line_ids), ('product_id', 'in', records.ids)])
         
          move_lines_to_unreserve = []
         
          for move_line in move_lines:
              if not move_line.location_id.should_bypass_reservation():
                  logging += "Problematic move line found: %s (reserved_quantity: %s)\n" % (move_line.id, move_line.product_qty)
                  logging += "There is no exiting quants despite its `reserved_quantity`\n"
                  logging += '******************\n'
                  move_lines_to_unreserve.append(move_line.id)
                  move_line_to_recompute_ids.append(move_line.id)
         
          if len(move_lines_to_unreserve) > 0:
              env.cr.execute("""
                      UPDATE stock_move_line SET product_uom_qty = 0, product_qty = 0 WHERE id in %s ;
                  """
                             % (tuple(move_lines_to_unreserve), ))
         
          if logging:
              env['ir.logging'].sudo().create({
                  'name': 'Unreserve stock.quant and stock.move.line',
                  'type': 'server',
                  'level': 'INFO',
                  'dbname': env.cr.dbname,
                  'message': logging,
                  'func': '_update_reserved_quantity',
                  'path': 'addons/stock/models/stock_quant.py',
                  'line': '0',
              })
         
          if move_line_to_recompute_ids:
              env['stock.move.line'].browse(move_line_to_recompute_ids).move_id._recompute_state()

      On Fri, 7 Jan 2022, 11:27 pm Carmen Bianca Bakker, <carmen@coopiteasy.be> wrote:
      Hello,

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

With kindness,
Carmen

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

      by Graeme Gellatly - 11:46 - 7 Jan 2022
    • Re: stock: Retroactively removing lots from incompatible products in stock move history 
      Hello,

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

With kindness,
Carmen
      by Carmen Bianca Bakker - 11:26 - 7 Jan 2022
    • Re: stock: Retroactively removing lots from incompatible products in stock move history


      On 1/7/22 10:47 AM, Carmen Bianca Bakker wrote:
      I have also verified that the quantities in
the inventory have correctly added up (the quantities of bottles that
previously had lots are added to the lot-less bottles).

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

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

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

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

    Hi,

     

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

     

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

     

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

     

    I look forward to your response!

     

    Regards,

    Caitlyn Drake

    Demand Generation

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

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

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

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

    Are there module in OCA helping out?

    Many thanks!
    by Kitti Upariphutthiphong - 11:26 - 30 Dec 2021

    6 replies 6 replies

  • Apply to community PSC
    Hi all,

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

    Thanks.

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

    8 replies 8 replies

    • Re: Apply to community PSC
      Thank you! :)

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

      Happy Christmas to all!

      El mié., 29 dic. 2021 15:57, Frederik Kramer <frederik.kramer@initos.com> escribió:
      Of course +1 and thanks for helping on this one 

Best Frederik

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



> Hi all,



> 



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



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



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



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



> happened yesterday.



> 



> Thanks.



> 



> Regards.



> _______________________________________________



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



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



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



-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

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

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

      by João Marques - 11:05 - 30 Dec 2021
    • Re: Apply to community PSC
      Thanks for the quick reaction.

      Happy Christmas to all!

      El mié., 29 dic. 2021 15:57, Frederik Kramer <frederik.kramer@initos.com> escribió:
      Of course +1 and thanks for helping on this one 

Best Frederik

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


> Hi all,


> 


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


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


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


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


> happened yesterday.


> 


> Thanks.


> 


> Regards.


> _______________________________________________


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


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


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


-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155

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

      by Pedro M. Baeza - 04:46 - 29 Dec 2021
    • Re: Apply to community PSC 
      Of course +1 and thanks for helping on this one 

Best Frederik

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

> Hi all,

> 

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

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

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

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

> happened yesterday.

> 

> Thanks.

> 

> Regards.

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer. - 03:56 - 29 Dec 2021
    • Re: Apply to community PSC
      Dear Pedro and Joäo,

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

      Bests,

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

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

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

      Thanks.

      Regards.

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



      --
      Simone Orsi

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


      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi. - 02:06 - 29 Dec 2021
    • Re: Apply to community PSC
      Hola, +1 :)

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

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

      Thanks.

      Regards.

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



      --
      Simone Orsi

      Full stack Python web developer, Odoo specialist, Odoo Community Board Member, in love with open source.
      by Simone Orsi. - 02:01 - 29 Dec 2021

  • Boolean grouped line label
    Hi there,

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

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

    image.png

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

    Your comments are appreciated !

    Regards,

    --
    Pierre Verkest
    06 81 12 25 20
    Github: petrus-v - Twitter: petrusv84 - Linkedin: pierre-verkest
    by Pierre Verkest - 02:36 - 24 Dec 2021

    1 attachments 1 attachments

    image.png

    2 replies 2 replies

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


-- 
Librement,
Xavier Brochard (zeroheure) xavier@alternatif.org
La liberté est à l'homme ce que les ailes sont à l'oiseau (Jean-Pierre 
Rosnay)
    by xavier - 10:20 - 15 Dec 2021
  • stock_inventory repository
    Hi all,

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


    Thanks

    --

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


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel. - 11:11 - 14 Dec 2021

    8 replies 8 replies

  • Move purchase_request* and purchase_work_acceptance*
    Hi all,

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

    Thanks
    --

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


    Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
    Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
    Zone industrielle 22 | L-8287 Kehlen | Luxembourg
    by Denis Roussel. - 09:35 - 14 Dec 2021

    11 replies 11 replies

    • Re: Move purchase_request* and purchase_work_acceptance*
      We can use readme to store this information. One file, all the info.

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

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


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

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

      On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

      Regards.

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

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



      --

      Francesco Apruzzese

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

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

      Non stampare questa email se non strettamente necessario. Aiuta te ed aiuta l'ambiente.
      by Francesco Apruzzese - 02:01 - 21 Dec 2021
    • Re: Move purchase_request* and purchase_work_acceptance*
      El mar, 21 dic 2021 a las 13:32, Yann Papouin (<ypa@decgroupe.com>) escribió:
      As I was in that case, why not creating a file with the same name for each moved module with a text content:
      Module moved to repository xxxxx


      In my experience, that's more maintenance burden on our part with no reward because people still don't look.

      Regards.
      by Pedro M. Baeza - 01:41 - 21 Dec 2021
    • Re: Move purchase_request* and purchase_work_acceptance*
      As I was in that case, why not creating a file with the same name for each moved module with a text content:
      Module moved to repository xxxxx

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


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

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

      On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

      Regards.

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

      by Yann Papouin - 01:31 - 21 Dec 2021
    • Re: Move purchase_request* and purchase_work_acceptance*
      I agree with Pedro.

      The amount of modules is not the only factor to take into account.

      The aim of a repository is also to group functionally modules that do 'quite' the same things and has a specific meaning (I don't like *-workflow stuff as it is too generic - @kitti don't create  purchase-extra-workflow as it adds abstraction and has no meaning).

      To find modules, we have our shop that leads to the good repository (we maybe need to do marketing on this)

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

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

      On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

      Regards.

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



      --

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


      Val Benoit, Quai Banning 6 | B-4000 Liège | Belgium
      Atrium Building, Drève Richelle 167 | B-1410 Waterloo | Belgium
      Zone industrielle 22 | L-8287 Kehlen | Luxembourg
      by Denis Roussel. - 11:50 - 21 Dec 2021
    • Re: Move purchase_request* and purchase_work_acceptance*
      Hi,

      I don't have a strong opinion on this one, if you want to split purchase-workflow, I'm fine with that.

      For me the real problem, and to bring another consideration to the table, are the repos with "rebel" addons that forces you to have multiple pipelines with some addons excluded and other with them included, it happens often that a contributor ends having to fix other modules tests when you opening a new PR of a new module. This happens in purchase-workflow but also in sale-workflow.

      Regards,

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

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

      On the contrary, it makes the ecosystem a bit more complicated, and gets people used to look to other places. When we unfolded OCA/hr into several repos, including OCA/hr-holidays and OCA/hr-expense, some people still created PRs to migrate one module that is already migrated, but on the other repo. But the problem here is that people don't look, and it happens constantly, not only with this, so no big deal.

      Regards.

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



      --
      Lois Rilo Antelo
      Odoo consultant at ForgeFlow S.L.
      by Lois Rilo Antelo - 11:46 - 21 Dec 2021

  • Decision tree to solve issues

    Hi all,

    I think anyone knows about decision trees, if even as jokes:

    A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

    I can imagine modeling something like this, but doesnt it already exist?

    I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

    Any ideas?

    Tom

    by Tom Blauwendraat - 03:16 - 10 Dec 2021

    1 attachments 1 attachments

    digbcncppollllom.png

    5 replies 5 replies

    • Re: Decision tree to solve issues
      Check out the mermaid widget in web repo.

      Also In odoo a decision tree is a multi step wizard. I could see how to do that with some very fancy context passing to a generic wizard.

      On Sat, 11 Dec 2021, 7:17 am Xavier Brochard, <xavier@alternatif.org> wrote:
      This sound very much like reverting a task with dependencies :

To work the printer need
->to be turned on
-->green light
--->paper
--->toner
-> to be online
-->network cable plugged in
-->no paper jam
etc.

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

Le 10.12.2021 17:57, Tom a écrit :


> Hi Pierre


> 


> Thanks!


> 


> What I'm looking for is more something on the lines of:


> 


> - There is a decision.tree model eg "How to fix your printer"


> - It can have decision.tree.node children such as "Is it turned on?"


> - Each question node has a set of conditions as to which next node it


> jumps to like: condition1,node1,condition2,node2...


> - If there are no conditions on a node anymore then this is an end


> node saying like "Your printer is irrefutably broken. Please send it


> back."


> 


> Kind of like a "Choose your own adventure" book.


> 


> -Tom


> 


> 


> Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:


> 


> 


> Hi,


> 


> 


> At anybox the project management was(/is ?) based on top of such idea


> where we could import mindmap as project starting point. Module is


> called anytracker and available on github here:


> https://github.com/anybox/anytracker [1] .


> 


> 


> A project is an anytracker.ticket without parent


> A task is an anytracker.ticket without child


> A node becomes a node when a child appears !


> 


> After a while we add the concept of anytracker.bouquet which is a


> couple of anytracker.ticket which could be a milestone, a release or


> whatever that has some sense to group together without changing the


> ticket tree !


> 


> hope that helps


> 


> 


> 


> 


> 


> Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl


> [2] > a écrit :


> 


> 


> Hi all,


> I think anyone knows about decision trees, if even as jokes:


> 


> A customer wants something like this, not the visualisation per-se,


> but to be able to have users click through it whenever they have an


> issue.


> I can imagine modeling something like this, but doesnt it already 


> exist?


> I guess the Odoo "Survey" modules can do part of it, but i don't know


> if they support structuring the survey as a tree.


> Any ideas?


> Tom


> 


> _______________________________________________ Mailing-List:


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


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


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


> 


> 


> --


> 


> Pierre


> 


> 


> _______________________________________________ Mailing-List:


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


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


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


> 


> 


> 


> _______________________________________________


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


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


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


> 


> 


> 


> [1] https://github.com/anybox/anytracker


> [2] mailto:tom@sunflowerweb.nl


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


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


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


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


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


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


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

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

      by Graeme Gellatly - 08:25 - 10 Dec 2021
    • Re: Decision tree to solve issues 
      This sound very much like reverting a task with dependencies :

To work the printer need
->to be turned on
-->green light
--->paper
--->toner
-> to be online
-->network cable plugged in
-->no paper jam
etc.

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

Le 10.12.2021 17:57, Tom a écrit :

> Hi Pierre

> 

> Thanks!

> 

> What I'm looking for is more something on the lines of:

> 

> - There is a decision.tree model eg "How to fix your printer"

> - It can have decision.tree.node children such as "Is it turned on?"

> - Each question node has a set of conditions as to which next node it

> jumps to like: condition1,node1,condition2,node2...

> - If there are no conditions on a node anymore then this is an end

> node saying like "Your printer is irrefutably broken. Please send it

> back."

> 

> Kind of like a "Choose your own adventure" book.

> 

> -Tom

> 

> 

> Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

> 

> 

> Hi,

> 

> 

> At anybox the project management was(/is ?) based on top of such idea

> where we could import mindmap as project starting point. Module is

> called anytracker and available on github here:

> https://github.com/anybox/anytracker [1] .

> 

> 

> A project is an anytracker.ticket without parent

> A task is an anytracker.ticket without child

> A node becomes a node when a child appears !

> 

> After a while we add the concept of anytracker.bouquet which is a

> couple of anytracker.ticket which could be a milestone, a release or

> whatever that has some sense to group together without changing the

> ticket tree !

> 

> hope that helps

> 

> 

> 

> 

> 

> Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat < tom@sunflowerweb.nl

> [2] > a écrit :

> 

> 

> Hi all,

> I think anyone knows about decision trees, if even as jokes:

> 

> A customer wants something like this, not the visualisation per-se,

> but to be able to have users click through it whenever they have an

> issue.

> I can imagine modeling something like this, but doesnt it already 

> exist?

> I guess the Odoo "Survey" modules can do part of it, but i don't know

> if they support structuring the survey as a tree.

> Any ideas?

> Tom

> 

> _______________________________________________ Mailing-List:

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

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

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

> 

> 

> --

> 

> Pierre

> 

> 

> _______________________________________________ Mailing-List:

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

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

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

> 

> 

> 

> _______________________________________________

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

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

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

> 

> 

> 

> [1] https://github.com/anybox/anytracker

> [2] mailto:tom@sunflowerweb.nl

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

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

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

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

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

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

> [9] https://odoo-community.org/groups?unsubscribe
      by xavier - 07:16 - 10 Dec 2021
    • Re: Decision tree to solve issues
      hum... ok so not sure that's helps that much then even you could reproduce the tree using title as answer node description as question that would probably not suit as usage...

      Le ven. 10 déc. 2021 à 17:57, Tom <tom@sunflowerweb.nl> a écrit :
      Hi Pierre

      Thanks!

      What I'm looking for is more something on the lines of:

      - There is a decision.tree model eg "How to fix your printer"
      - It can have decision.tree.node children such as "Is it turned on?"
      - Each question node has a set of conditions as to which next node it jumps to like: condition1,node1,condition2,node2...
      - If there are no conditions on a node anymore then this is an end node saying like "Your printer is irrefutably broken. Please send it back."

      Kind of like a "Choose your own adventure" book.

      -Tom

      Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

      Hi,

      At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

      A project is an anytracker.ticket without parent
      A task is an anytracker.ticket without child
      A node becomes a node when a child appears !

      After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

      hope that helps



      Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

      Hi all,

      I think anyone knows about decision trees, if even as jokes:

      A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

      I can imagine modeling something like this, but doesnt it already exist?

      I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

      Any ideas?

      Tom

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



      --
      Pierre

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

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



      --
      Pierre
      by Pierre Verkest - 06:31 - 10 Dec 2021
    • Re: Decision tree to solve issues
      Hi Pierre

      Thanks!

      What I'm looking for is more something on the lines of:

      - There is a decision.tree model eg "How to fix your printer"
      - It can have decision.tree.node children such as "Is it turned on?"
      - Each question node has a set of conditions as to which next node it jumps to like: condition1,node1,condition2,node2...
      - If there are no conditions on a node anymore then this is an end node saying like "Your printer is irrefutably broken. Please send it back."

      Kind of like a "Choose your own adventure" book.

      -Tom

      Dec 10, 2021 17:32:12 Pierre Verkest <pierreverkest84@gmail.com>:

      Hi,

      At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

      A project is an anytracker.ticket without parent
      A task is an anytracker.ticket without child
      A node becomes a node when a child appears !

      After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

      hope that helps



      Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

      Hi all,

      I think anyone knows about decision trees, if even as jokes:

      A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

      I can imagine modeling something like this, but doesnt it already exist?

      I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

      Any ideas?

      Tom

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



      --
      Pierre

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

      by Tom Blauwendraat - 05:55 - 10 Dec 2021
    • Re: Decision tree to solve issues
      Hi,

      At anybox the project management was(/is ?) based on top of such idea where we could import mindmap as project starting point. Module is called anytracker and available on github here: https://github.com/anybox/anytracker.

      A project is an anytracker.ticket without parent
      A task is an anytracker.ticket without child
      A node becomes a node when a child appears !

      After a while we add the concept of anytracker.bouquet which is a couple of anytracker.ticket which could be a milestone, a release or whatever that has some sense to group together without changing the ticket tree !

      hope that helps



      Le ven. 10 déc. 2021 à 15:17, Tom Blauwendraat <tom@sunflowerweb.nl> a écrit :

      Hi all,

      I think anyone knows about decision trees, if even as jokes:

      A customer wants something like this, not the visualisation per-se, but to be able to have users click through it whenever they have an issue.

      I can imagine modeling something like this, but doesnt it already exist?

      I guess the Odoo "Survey" modules can do part of it, but i don't know if they support structuring the survey as a tree.

      Any ideas?

      Tom

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



      --
      Pierre
      by Pierre Verkest - 05:30 - 10 Dec 2021
  • How to use oca-ci 
    Hi,


I just read the README.md of the https://github.com/OCA/oca-ci project,


Does anyone have experience using this to develop and test locally?


I am probably not that smart, but I miss in the README.md information to
get started or how tu use this.


Kind regards,


Ronald
    by Ronald Portier - 08:50 - 9 Dec 2021

    2 replies 2 replies

  • Tracing and in general how can we execute an handler on every request

    Hello all,

    I have a technical question and I wonder if anyone here already faced this issue.

    I am trying to integrate Odoo into our monitoring stack, with the three pillars of observability metrics/logging/tracing, starting with the tracing. My issue is, it doesn't look like we have an easy way to insert the handler which will start the trace. Also no documentation anywhere about how we can easily integrate tracing into Odoo. This is a v12 version but I believe the issue is still here on more recent versions.

    We are planning to use Azure Monitor, but the issue will be the same with any other tracing platform : I can't figure a way to override a core function to start the trace and insert the python library I need https://docs.microsoft.com/fr-fr/azure/azure-monitor/app/opencensus-python#tracing

    I can of course override some of the most important controllers like https://github.com/odoo/odoo/blob/12.0/addons/web/controllers/main.py#L961:

    -----------

    from odoo.addons.web.controllers.main import DataSet
    class ExtendDataSet(DataSet):
    @route()
    def call_kw(self, model, method, args, kwargs, path=None):
    print("Insert tracer here")
    return super(
    ExtendDataSet, self).call_kw(
    model, method, args, kwargs, path=path)

    -----------

    But this will force me to override all controllers I can find, and some custom controllers will obviously go under the radar.

    I identified some entry point used by all requests like https://github.com/odoo/odoo/blob/12.0/addons/web/controllers/main.py#L961 or https://github.com/odoo/odoo/blob/12.0/odoo/http.py#L316 but I don't think I have a way to override theses functions without having to rely on the terrible idea to patch the core code.

    Anything I missed on how we could execute some code on every request ? On Django you would just use a middleware for such purpose https://docs.djangoproject.com/fr/2.2/topics/http/middleware/ and it does the job perfectly, I feel like this is something which is really missing in Odoo when we have such requirements.

    Thanks,
    Yannick




    by Yannick Buron - 12:20 - 8 Dec 2021
  • Consignation for shipping material
    Dear community,

    I'm searching for a solution to handle "consignation" of products ("consigne" in French). There are 2 aspects we want to handle here:

    1. Invoicing
    2. Stock t the customer (how many boxes left at each customers facility)

    The use case is: To deliver the customer we use X shipping boxes like those https://embalogik.com/produit/fruits-legumes-50-x-30-b/. For every customer, we want to keep the count of how many boxes he received and invoice/refund him when I deliver and take them back...
    The behavior is similar to the one with consignation on bottles. We discussed it internally at Camptocamp and have 3 ideas:

    1. Cheap solution: an integer field on res.partner to contain the quantity -> 100% manual, not very handy
    2. delivery_package_fee that we developed and adds a fee on the SO using a service product -> we cover the invoicing, stock and refunds have to be handled manually
    3, A new module that would handle, stock, invoicing and refunds -> seems to be really complicated for the benefit

    What are your thoughts? Thank you very much!

    Didier

    --
    camptocamp
    INNOVATIVE SOLUTIONS
    BY OPEN SOURCE EXPERTS

    Didier Donzé
    Chef de projet

    +41 21 619 10 10 (central)
    +41 21 619 10 45 (direct)

    Camptocamp SA
    Quartier de l'Innovation EPFL, PSE-A
    1015 Lausanne
    Suisse

    by Didier Donzé - 09:00 - 7 Dec 2021

    2 replies 2 replies

    • Re: Consignation for shipping material

      Dear Didier,

      As far as I understand, keeping the same behavior as delivery_package_fee but allowing to select a storable product instead of service might do the trick no ?

      • Validating your sale order would then generate a delivery order with the shipping box
      • When you get the shipping box back, you could make a return of these products from delivery order and refund the returned quantity

      Best Regards,

      Le Filament
      		 Rémi CAZENAVE
      ------
      SCOP LE FILAMENT
      06.87.23.26.04
      remi@le-filament.com
      Le 07/12/2021 à 09:02, Didier Donzé a écrit :
      Dear community,

      I'm searching for a solution to handle "consignation" of products ("consigne" in French). There are 2 aspects we want to handle here:

      1. Invoicing
      2. Stock t the customer (how many boxes left at each customers facility)

      The use case is: To deliver the customer we use X shipping boxes like those https://embalogik.com/produit/fruits-legumes-50-x-30-b/. For every customer, we want to keep the count of how many boxes he received and invoice/refund him when I deliver and take them back...
      The behavior is similar to the one with consignation on bottles. We discussed it internally at Camptocamp and have 3 ideas:

      1. Cheap solution: an integer field on res.partner to contain the quantity -> 100% manual, not very handy
      2. delivery_package_fee that we developed and adds a fee on the SO using a service product -> we cover the invoicing, stock and refunds have to be handled manually
      3, A new module that would handle, stock, invoicing and refunds -> seems to be really complicated for the benefit

      What are your thoughts? Thank you very much!

      Didier

      --
      camptocamp
      INNOVATIVE SOLUTIONS
      BY OPEN SOURCE EXPERTS

      Didier Donzé
      Chef de projet

      +41 21 619 10 10 (central)
      +41 21 619 10 45 (direct)

      Camptocamp SA
      Quartier de l'Innovation EPFL, PSE-A
      1015 Lausanne
      Suisse

      _______________________________________________
      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 - 10:31 - 7 Dec 2021
    • Re: Consignation for shipping material
      A suggestion:
      - We've done for a project a module that allows to create invoice from a delivery order, while maintaining the compatibility with odoo sales-invoices control.

      So:
      I would suggest to do the above + mimicking the sale deposit process:
      - When creating an invoice from delivery order
            - manually add the number of boxes (e.g. with a wizard)
            - add a sale order line for the number of boxes - order qty =0, delivered qty = as in the stock.picking
           - create the sales invoice

      When the boxes are returned:
      - return the boxes from the DO
      - create a new sales invoice, which will automatically create a credit note
           
      Cheers,
      Dominique


      On Tue, 7 Dec 2021 at 16:02, Didier Donzé <didier.donze@camptocamp.com> wrote:
      Dear community,

      I'm searching for a solution to handle "consignation" of products ("consigne" in French). There are 2 aspects we want to handle here:

      1. Invoicing
      2. Stock t the customer (how many boxes left at each customers facility)

      The use case is: To deliver the customer we use X shipping boxes like those https://embalogik.com/produit/fruits-legumes-50-x-30-b/. For every customer, we want to keep the count of how many boxes he received and invoice/refund him when I deliver and take them back...
      The behavior is similar to the one with consignation on bottles. We discussed it internally at Camptocamp and have 3 ideas:

      1. Cheap solution: an integer field on res.partner to contain the quantity -> 100% manual, not very handy
      2. delivery_package_fee that we developed and adds a fee on the SO using a service product -> we cover the invoicing, stock and refunds have to be handled manually
      3, A new module that would handle, stock, invoicing and refunds -> seems to be really complicated for the benefit

      What are your thoughts? Thank you very much!

      Didier

      --
      camptocamp
      INNOVATIVE SOLUTIONS
      BY OPEN SOURCE EXPERTS

      Didier Donzé
      Chef de projet

      +41 21 619 10 10 (central)
      +41 21 619 10 45 (direct)

      Camptocamp SA
      Quartier de l'Innovation EPFL, PSE-A
      1015 Lausanne
      Suisse

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

      by dominique.k - 10:15 - 7 Dec 2021
  • Target Criteria

    Hi,

     

    Hope you are doing well.

     

    Since we are heading towards end of 2021 I would like to know if you are looking for a fresh list of B2B customers for your target criteria.

     

    We offer customized list based on job titles, employee size, revenue size, industry and users of specify software’s.

     

    Let me know your target criteria so that I can help you reach your target audience.

     

    Regards,

    Meghan Hudson

    Marketing Executive

    If you do not wish to receive these emails. Please respond Exit.

     

    by "Meghan. Hudson" <meghan.hudson@mytechdb.com> - 10:41 - 3 Dec 2021
  • Target Criteria

    Hi,

     

    Hope you are doing well.

     

    Since we are heading towards end of 2021 I would like to know if you are looking for a fresh list of B2B customers for your target criteria.

     

    We offer customized list based on job titles, employee size, revenue size, industry and users of specify software’s.

     

    Let me know your target criteria so that I can help you reach your target audience.

     

    Regards,

    Rachael Kelly

    Marketing Executive

    If you do not wish to receive these emails. Please respond Exit.

     

    by "Rachael Kelly" <rachael.kelly@globaltradeshowz.com> - 10:21 - 3 Dec 2021
  • [29806] Porting account_reset_chart to v14+ 
    Hi Stefan, hi others, 

a small OCA realated question. Does anyone of the originators or
contribtors of

https://github.com/OCA/account-financial-tools/tree/10.0/account_reset_chart

know if the core functionality (empty and change the whole CoC) 
of this module has ever been superseeded by anything other (i guess
account_chart_update won't do that trick) or if it simply hasn't been
ported so far. 

If there are now massive technical traps either of you is aware of 
i would let it migrate to v14 the days to come. I would really
appreciate all your comment on that.

Cheers and stay healthy

Frederik

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
    by Frederik Kramer. - 01:45 - 2 Dec 2021

    2 replies 2 replies

    • Re: [29806] Porting account_reset_chart to v14+ 
      Hi Stefan,

thank you for the feedback on this. We already started this migration
(for the time being without too much refactoring, but i haven't tested
the result myself yet). Anyway the important issue for me here was if
that module is really technically obsolete (for whatever reason) but
reading between the lines i would say this is probably not the case, so
let me check if we can get it work soon on v14

Best and thanks for your feedback

Frederik

Am Freitag, dem 10.12.2021 um 10:47 +0000 schrieb Stefan Rijnhart:

> On 02-12-2021 13:46, Frederik Kramer wrote:

> > Hi Stefan, hi others, 

> > 

> > a small OCA realated question. Does anyone of the originators or

> > contribtors of

> > 

> > https://github.com/OCA/account-financial-tools/tree/10.0/account_reset_chart

> > 

> > know if the core functionality (empty and change the whole CoC) 

> > of this module has ever been superseeded by anything other (i guess

> > account_chart_update won't do that trick) or if it simply hasn't

> > been

> > ported so far. 

> > 

> > If there are now massive technical traps either of you is aware of 

> > i would let it migrate to v14 the days to come. I would really

> > appreciate all your comment on that.

>  

> Dear Frederik,

> 

> note that the module is in the 10.0 repo but uninstallable, so that's

> actually the 8.0 version you're looking at.

> 

> That is a long 6,5 years of financial refactoring on the Odoo side,

> so you can be looking forward to a complete redevelopment of the

> functionality I'm afraid.

> 

> Good luck!

> Stefan

> 

> 

> -- 

> Opener B.V. - Business solutions driven by open source collaboration

> 

> Stefan Rijnhart - Consultant/developer

> 

> mail: stefan@opener.am

> tel: +31 (0) 6 1447 8606

> web: https://opener.am

> _______________________________________________

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

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

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

-- 
Dr.-Ing. Frederik Kramer
Geschäftsführer
        
initOS GmbH
An der Eisenbahn 1
21224 Rosengarten
        
Phone:  +49 4105 56156-12
Fax:    +49 4105 56156-10
Mobil:  +49 179 3901819
        
Email: frederik.kramer@initos.com
Web:   www.initos.com
        
Geschäftsführung:
Dr.-Ing. Frederik Kramer & Dipl.-Ing. (FH) Torsten Francke

Sitz der Gesellschaft: Rosengarten – Klecken
Amtsgericht Tostedt, HRB 205226
Steuer-Nr: 15/200/53247
USt-IdNr.: DE815580155
      by Frederik Kramer. - 12:26 - 10 Dec 2021
    • Re: [29806] Porting account_reset_chart to v14+
      On 02-12-2021 13:46, Frederik Kramer wrote:
      Hi Stefan, hi others, 

a small OCA realated question. Does anyone of the originators or
contribtors of

https://github.com/OCA/account-financial-tools/tree/10.0/account_reset_chart

know if the core functionality (empty and change the whole CoC) 
of this module has ever been superseeded by anything other (i guess
account_chart_update won't do that trick) or if it simply hasn't been
ported so far. 

If there are now massive technical traps either of you is aware of 
i would let it migrate to v14 the days to come. I would really
appreciate all your comment on that.

      Dear Frederik,

      note that the module is in the 10.0 repo but uninstallable, so that's actually the 8.0 version you're looking at.

      That is a long 6,5 years of financial refactoring on the Odoo side, so you can be looking forward to a complete redevelopment of the functionality I'm afraid.

      Good luck!
      Stefan


      -- 
Opener B.V. - Business solutions driven by open source collaboration

Stefan Rijnhart - Consultant/developer

mail: stefan@opener.am
tel: +31 (0) 6 1447 8606
web: https://opener.am
      by "Stefan Rijnhart" <stefan@opener.amsterdam> - 11:45 - 10 Dec 2021
  • Call for OCA Financial Auditors - closing Friday 3rd December
    Hello OCA Contributors

    I hope this finds you well.

    Just a quick reminder that the applications for Board Members (only current Delegates can apply for this, the links have been sent on the Delegates mailing list) and Financial Auditors closes tomorrow - Friday 3rd Dec.

    For the Financial Auditors the applicant does not need to be a current member of the OCA. So, if there is perhaps someone in your company that may be able to help in this regard please share the link below.

    Any questions, please let me know.

    Warm regards,
    Rebecca
    --
    Rebecca Gellatly
    General Secretary
    Odoo Community Association
    by Rebecca Gellatly - 05:16 - 2 Dec 2021
  • Install postgres unaccent lib at travis yml
    Hello Everyone!

    I'm developing a  Pull Request at Brazilian location (l10n-brazil) and I'm getting error at some Travis jobs because we need that our Postgres database has the unaccent lib installed.

    My Travis build is:


    Could anyone help me on how to set this unaccent lib in my Travis yml configuration?

    Thanks for your help!

    Regards,
    Luiz Felipe

    --
    Luiz Felipe do Divino
    Bacharel em Ciências da Computação
    UNIFEI - Itajubá
    by Luiz Felipe Divino - 09:06 - 30 Nov 2021

    3 replies 3 replies

  • FAQ on OCB github's wiki 
    Hi everyone

I am working on the OCB wiki.
I've already renamed with "OLD-" prefix all the pages related to 
migration from Launchpad to Github, and I started an OCB purpose page 
and a draft FAQ. Could you help to answer these simple questions (short 
answers, please)? 

- Can I fix bugs directly in OCB ?

   OCB only accept changes if you submit your fix against the official 
version to prevent to be a fork in the end. All updates must be 
submitted to the official odoo branch for adoption in the official odoo 
release before they can be considered for the OCB version.

- Do I need the Odoo CLA signed to submit a patch to OCB branches ?

   No. But as you need to submit your patch upstream, Odoo SA will 
probably ask you to sign it. The OCA encourages you to carefully read 
this document, as it allows Odoo s.a. to relicense your contribution. 
Some important contributors from the OCA have signed that document 
because this eases the work of the core maintainers and the OCB 
maintainers.

- Does it contains backports ?
- Does it contains fixes that are not on same Odoo version, but on 
higher versions ?
- Does it maintains versions that are no more maintained by Odoo ?
- Does OCA's runbot use OCB ?
- Why is it sometimes behind Odoo ? does it concern minor updates ?
- Why should we use OCB instead of Odoo nightly ?

   Because it contains more bug fixes and because it is maintained for a 
longer time.

- How to use OCB ?

  See Odoo documentation about installing from source. Use git clone and 
update frequently.



Best regards


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