In-Memory Mode Limitations
- 2 minutes to read
The following article describes Pivot Grid’s In-Memory mode limitations that depend on the data processing engine.
Note
If you connect the Pivot Grid to the server mode data sources and OLAP cubes, the PivotGridOptionsData.DataProcessingEngine property is ignored because Pivot data processing engines calculate data on the client.
Optimized Mode
The following API are not supported in Optimized mode. The NotSupportedException occurs in Optimized mode for unavailable values, properties, and handled events.
Events
Properties
The following properties of the Pivot Grid’s field are not supported:
The following properties of the Pivot Grid’s field are not supported when its value is set to Custom:
Property | Value |
---|---|
PivotGridField.SummaryType | PivotSummaryType.Custom |
PivotGridField.GroupInterval | PivotGroupInterval.Custom |
PivotGridField.SortMode | PivotSortMode.Custom |
The following properties of the Pivot Grid’s field are ignored when you use the Data Binding API:
You can set the PivotGridFieldBase.DataBinding property to null to use them.
You cannot use the CalculationBindingBase descendants to apply summary filter or sorting by summary when Pivot Grid operates with Optimized calculation engine.
Legacy and LegacyOptimized
Legacy and LegacyOptimized modes do not support the Data Binding API.
The PivotGridFieldBase.DataBinding property is ignored.
You cannot use the control’s CreateDrillDownDataSource methods to request underlying data in the following events: