For all graph types, Datetime fields are tricky for grouping, because you'll rarely encounter the same field value here. So, if you have a Datetime field of type row, also specify the interval attribute with one of the following values: day, week, month, quarter, or year. This will cause the grouping to take place in the given interval.
The pivot table also supports grouping in columns. Use type col for the fields you want to have there.
Grouping, like sorting, relies heavily on PostgreSQL. So, here also, the rule applies that a field must live in the database and in the current table in order to be usable.
It is common practice to define database views that collect all the data you need and define a model on top of this view in order to have all the necessary fields available.
Depending on the complexity of your view and the grouping, building the graph can be quite an expensive exercise. Consider setting the auto_search attribute to False in those cases, so that the user can first adjust all the parameters and only then trigger a search.
It is common practice to define database views that collect all the data you need and define a model on top of this view in order to have all the necessary fields available.
Depending on the complexity of your view and the grouping, building the graph can be quite an expensive exercise. Consider setting the auto_search attribute to False in those cases, so that the user can first adjust all the parameters and only then trigger a search.