Odoo Changelog — 2018-07-16

Monday, July 16, 2018

3 changes

Improvements(3)

Enhancements to existing features

[PERF] stock: compute of quantity done is so long

CoremasterstockMEDIUM

Improves the speed of validating stock pickings that contain many uniquely serialized items. This reduces long waiting times during warehouse operations, turning a process that could take many minutes into a much faster action.

Original PR description

When you validate a picking with unique serial number it is super long :
- with 323 `stock.move` and 1780 `stock.move.line` (because it is unique serial) the time is around 14 minutes.

During the compute the field `quantity_done` on `stock.move` is not stored, the time to compute is around 1.5 secondes.
With this fix it is 0.15 secondes., You win 484 secondes for this picking.

Regards

@odony @jco-odoo @alnslang @pedrobaeza @sylvain-garancher 




--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

#performance#inventory#warehouse#serial numbers

De-commit-ify installation and don't fail module install on demo failure

PR #25436

Coremasterbasegamificationwebsite_forumMEDIUM

Module installation is now more resilient when optional demo data cannot be loaded. Instead of blocking the whole installation, the system rolls back only the failed demo data, logs the issue, and notifies the user so business operations can continue.

Original PR description

Task 1856935

Currently, when installing modules with demo data enabled if the demo data installation fails (because they're borked or the module was uninstalled and they weren't fully cleaned up or some other reason) the module itself fails.

Since demo data are generally non-essential, change this so when the demo data fail to install their installation is just rollbacked and we go on our merry way, but do notify the end user of the issue (and log a warning).

#installation#demo data#user notification#reliability

Master cohort in dashboard rli

PR #2378

Enterprisemasterweb_cohortweb_dashboardMEDIUM

Dashboards can now include cohort views, making it easier to track how groups evolve over time from one central reporting page. This gives business users richer analysis options without switching between separate views.

Original PR description

Task : https://www.odoo.com/web#id=1864784&model=project.task&view_type=form&menu_id=

#dashboard#cohort#reporting#analytics

When you validate a picking with unique serial number it is super long : - with 323 `stock.move` and 1780 `stock.move.line` (because it is unique serial) the time is around 14 minutes. During the compute the field `quantity_done` on `stock.move` is not stored, the time to compute is around 1.5 secondes. With this fix it is 0.15 secondes., You win 484 secondes for this picking. Regards @odony @jco-odoo @alnslang @pedrobaeza @sylvain-garancher -- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

Task 1856935 Currently, when installing modules with demo data enabled if the demo data installation fails (because they're borked or the module was uninstalled and they weren't fully cleaned up or some other reason) the module itself fails. Since demo data are generally non-essential, change this so when the demo data fail to install their installation is just rollbacked and we go on our merry way, but do notify the end user of the issue (and log a warning).