summaryrefslogtreecommitdiff
path: root/addons/pos_cache/data/pos_cache_data.xml
diff options
context:
space:
mode:
authorNicolas Lempereur <nle@odoo.com>2016-06-16 15:29:05 +0200
committerNicolas Lempereur <nle@odoo.com>2016-06-16 15:38:27 +0200
commitf7ec48b6dff7ae89104a369494f5825083a44bd2 (patch)
tree9d801006da03229c22a4718eb7966511ff6a8b86 /addons/pos_cache/data/pos_cache_data.xml
parenta59703e6527678a62ba9b8344645448f0ac61c21 (diff)
[FIX] crm: needed _order for group by crm.stage
When grouping result the BaseModel method _read_group_fill_results add the possible groups which had no result. But, if the order of the group is not consistent, we can get really wrong results. The code logic is expecting that the grouped result gotten and the list of groups (returned by _read_group_stage_ids of crm.lead) is in the same order. If the _order attribute of the model is not enough specific (as was the case in crm.stage) the inconsistent order would kill aggregation values (displaying 0 instead of what should have been present). opw-680952
Diffstat (limited to 'addons/pos_cache/data/pos_cache_data.xml')
0 files changed, 0 insertions, 0 deletions