Hierarchical Value Presentation
- 2 minutes to read
Field values in reports are displayed hierarchically, if two or more fields are located in the drop areas. The hierarchical view of the data allows end-users to analyze a report at different levels. The deeper the hierarchy, the more hierarchical choices for end-users to make data analysis from different perspectives.
The hierarchical view is best fitted for the complex data analysis, if the data in the underlying data source is hierarchical (the tables in that store are in a master-detail relationship) and the data source contains lookup fields. For example, the Orders table may contain a lookup Company Name (a dealer) field and a lookup Car Name. Then dropping these two fields in the row header area will result in the following hierarchy:
In the view you can see the way the data is summarized by the dealer, and each model at a time. The parent grouping values display expand buttons that can be used to switch from the “by dealer” to the “by model” view.
Another way is to apply different levels of details with the same field. You can create two or more view fields and bind them to the same persistent field. For instance, two fields can be bound to the PurchaseDate persistent field (see the OrderReportsDemo that ships with the product). The first field (Year) will group data by years, while the second one (Month) – by months (see the TcxPivotGridField.GroupInterval property):
Note that you can provide custom intervals in addition to the default ones (to do that, set the TcxPivotGridField.GroupInterval property to giCustom and handle the TcxPivotGridField.OnGetGroupValue and TcxPivotGridField.OnGetGroupValueDisplayText events).