PURPOSE Be able to remove some measures from graph / pivot views. Currently fields are automatically added but some of them make no sense. SPECIFICATIONS Add the possibility to not display some fields in the measures dropdown for the graph and pivot views. When a field is not displayed in the measures of a pivot views we remove them also from the list of groupable fields. LINKS Task ID-2288381 Community PR #54774 Enterprise PR odoo/enterprise#11970 Upgrade PR odoo/upgrade#1519
In pivot view, a cell data is determined by his row/column key which are the value chain of field values to get to that row/column. If you had a grouping with value in a cell and then close the grouping, you could somehow get the old value back wrongly on next grouping operations. This happened because: - the key was computed based on the value (eg. for relational field the record ID) but without the field name. - succeeding read_group only fill existing values. eg. If on pivot view we had a salesperson with same ID as product category, if we closed salesperson grouping then opened product category grouping, we could possibly get the cell value to the product category that has the same ID as the salesperson. With this changeset, we clear the cell data corresponding to a grouping that has been closed. Added test without the fix would fail by displaying data of a previous read_group that should have been cleared inbetween. opw-2262306 closes #55129 closes odoo/odoo#55936 X-original-commit: f1df73adca4955561814d4b8e90a62d7d50c1c33 Signed-off-by: Nicolas Lempereur (nle) <nle@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>
Before this commit, click on the divider in the menu 'Measures' of the pivot control panel would cause a crash. The present commit fixes that situation. We also bring another small correction: the menu won't close if one clicks on the measure list but not exactly on a menu item or the divider. closes odoo/odoo#55902 X-original-commit: aad9f3fd7499ef8b660cc25fea840a34d70f75a6 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com> Signed-off-by: Mathieu Duckerts-Antoine <Polymorphe57@users.noreply.github.com> Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>
Improve mock server: - add support for mocked `fetch` - add support for `active_test` - add support for x2m `in` in domains - add support for default values computed from a function - implement a more natural "next id" compute - allow initial data without ids - ensure write and x2m commands integrity - improve bad data/bad commands error messages - always warn for failing RPC, not only in debug mode - fix all existing tests that had inconsistency data Other changes done in mail (or dependents) that are not just related to tests: - remove `direct_partner` from formatter result ->`correspondent` can be computed from other keys, especially `members` - fix `livechat_visitor` convertData -> only process if there is value - add `current_partner` and `current_user_id` as `init_messaging` result -> easier to mock than session - remove usage of `need_moderation` -> that was just a search indirection to `moderation_status` - adapt `partner_id` -> `res_partner_id` key in `_notification_format` -> to be consistent with field name - add name in result of `mail_partner_format` -> sometimes display_name is not the same - remove usage of `is_moderator` -> that was just an indirection to `moderation_channel_ids` Enterprise counterpart: https://github.com/odoo/enterprise/pull/11523 task-2287171 closes odoo/odoo#55854 X-original-commit: 7ba3fecb3377a720d1eb70e7515a0c45da73836d Related: odoo/enterprise#12391 Signed-off-by: Sébastien Theys (seb) <seb@odoo.com>
A previous commit has paved the way for displaying sample data in the reporting views. The present commit brings the required changes to have sample data in pivot views. Task ID: 2282196 Co-authored-by: Aaron Bohy <aab@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>
Adaptation of the tests to the changes regarding the refactored search panel and model. Part of task 2228968 Co-authored-by: Julien Mougenot <jum@odoo.com> Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com>
When comparing time ranges in pivot, it makes more sense to display the previous period before the one being compared. This commit allows that. Task ID: 2269770 closes odoo/odoo#52746 Signed-off-by: Mathieu Duckerts-Antoine <Polymorphe57@users.noreply.github.com> Co-authored-by: Priyanka Kakadiya <pka@odoo.com> Co-authored-by: Mohammed Shekha <msh@odoo.com>
This is useful for the integration of pivot views with spreadsheet Task-ID: 2168016
Tests have been adapted accross all affected modules to support the new "comparison" menu component. Task ID: 2245719 Co-authored-by: Mathieu Duckerts-Antoine <dam@odoo.com> Co-authored-by: Julien Mougenot <jum@odoo.com>
In the pivot view, groups comming from many read_group are assemble to create the header hierarchies and the table. Groups returned by the read_group may be already sorted by the server using the order set on the model for instance and that order should be reflected in the header hierarchies (and in the table). It is important to keep that order since it might not be possible to recreate it in the interface. Even if possible it might not be a good idea for performance reasons. Before this commit: The groups are added in a JS object, whose keys are the group ids (when grouping on a many2one at least). Then, to generate the table, we iterate over the keys of that object, but those keys are sorted according to the numerical order (not the insertion order), because keys are kind of numeric. See https://stackoverflow.com/questions/5525795/does-javascript-guarantee-object-property-order. After this commit: Instead of a JS object, we use a Map for which the insertion order is used (official spec). Task ID: 2243416 closes odoo/odoo#50551 X-original-commit: 1a9a85c8b8d0f47c3c6f3878cd6d9401ddc3ad75 Signed-off-by: Aaron Bohy (aab) <aab@odoo.com>