ASP.NET Pivot Table Control

ADOMD.NET and XMLA Support for OLAP Binding

With this release, we have introduced full support for ADOMD.NET and XMLA data providers.

• ADOMD.NET offers all the features supported by OLE DB and additionally allows you to retrieve format strings and properties of OLAP members from the server.

• XMLA is an open XML-based standard that does not require any data access libraries or data providers to be installed on the system. Nevertheless, it supports all OLAP features available in ADOMD.NET.

Browsing OLAP Cubes in Field List

If a Pivot Grid is bound to an OLAP cube, the Field List shows pivot grid fields as they appear in a cube browser - dimension fields are arranged in folders and grouped by dimensions, while named and KPI measures are shown within two separate categories, arranged in measure groups and/or display folders.

User Folders in Field List

For standard data source mode, this release introduces the ability to arrange fields into user-defined folders in the Field List. To implement this new feature, specify a folder for each field. Whenever the field is displayed in the Field List, it will be shown in the specified folder. As you would expect, you can create folder hierarchies, by placing folders one into another.

Charting Automation Features

When displaying the PivotGrid Control’s data in a chart, you rarely need to compare cell values to Totals or Grand Totals as these values differ significantly. At the same time, when selecting large cell blocks, Total values inevitably appear within the selection. To solve this with previous versions, you had to manually disable a few options that controlled Total value visibility within the bound chart control.

With this release, PivotGrid automatically defines which values should be passed to ChartControl. It analyzes the current selection, finds the lowest-level data and excludes all higher-level Totals. The following animation shows how selection changes are reflected within a bound Chart control.

Yet another new automation feature "rotates" the chart by changing series into arguments and vice versa depending on the current selection. In this mode the control makes sure that the number of series never exceeds the number of arguments.

Filtering by OLAP Member Unique Names

By default, a pivot grid identifies field values by the corresponding OLAP member values. With this release, you can configure the pivot grid to use OLAP member unique names instead. This option is useful if your cube contains several members with the same value, as it enables the pivot grid to distinguish between such members.

Optimized Performance and Memory Consumption for OLAP

The ASP.NET PivotGrid consumes much less memory when fetching summary values if the layout contains one to three data fields. The query generation engine has also been optimized, giving you up to two times faster performance against certain operations (such as expanding field values).

Simplified OLAP Binding

You no longer need to create data source objects nor reference additional assemblies to bind the pivot grid to OLAP cubes using ADOMD.NET or XMLA. Simply specify the connection string (as you would with OLE DB), and select the required data provider via the newly introduced OLAPDataProvider property.

Miscellaneous Enhancements

• Improved Top N Values Feature

  We have introduced a new way to define the number of top values to be displayed (an update for the Top N Values feature – available in OLAP mode). You can now specify the maximum allowed sum of the corresponding summary values and the pivot grid will display the maximum number of field values whose summaries do not exceed the specified number in total.

• New Event for Easy Customization of Data Passed to a Chart

  We have introduced a new CustomChartDataSourceRows event that allows you to add, modify and remove specific rows from the chart data source.