When a date dimension is used in a pivot view, the granularity must be specified. Before this commit, it automatically defaulted to 'month_number'. With the experience of the odoo pivot, it's not a good idea to have a default granularity, as it's not easily migrable. In addition, supported a date dimension without granularity leads to lots of "if-else" in the code to handle this.
So, we prefer to avoid this situation and raise an error when a date dimension is used without a granularity.
Description:
description of this task, what is implemented and why it is implemented that way.
When a date dimension is used in a pivot view, the granularity must be specified. Before this commit, it automatically defaulted to 'month_number'. With the experience of the odoo pivot, it's not a good idea to have a default granularity, as it's not easily migrable. In addition, supported a date dimension without granularity leads to lots of "if-else" in the code to handle this.
So, we prefer to avoid this situation and raise an error when a date dimension is used without a granularity.
Description:
description of this task, what is implemented and why it is implemented that way.
Task: : TASK_ID
review checklist