An OData feed that supports 'OData Extension for Data Aggregation Version 4.0'
can be queried for all of the information required to populate a PivotGrid
with rows and columns that are paged, sortable (including by different aggregates
of the measures), and filterable, and have all calculations performed on the server.

The pivot grid can be popualted using data obtained from a couple of requests
to a suitable feed -- or feeds.

Suppose we have an OData feed that we'd like to display in a pivot grid. Some of the 
columns in the feed will become dimensions, and some will become measures.
(We may display the same measure more than once, with different aggregates applied.)

In order to display the row/column headings for the pivotGrid we need to select the 
distinct values from the 'dimension' columns. The filtering provided by OData 
allows the row/column headings to be filtered, and even
paged (in both directions). Sorting is more difficult because we want to sort not only 
by the row/column heading values themselves, but also by (aggregates of) the measures.
However, that's a problem for the server side!

In order to populate the body of the table we need to calculate a load of aggregates
from the measure columns in the base dataset for the rows that correspond to visible
row/column headers. We can write a rather long OData $filter expression to obtain 
the required rows from the original OData feed, and then aggregate them.

All of this functionality is available in 'OData Extension for Data Aggregation Version 4.0'.
However, as an interim solution we may establish two 'helper' OData feeds associated
with the original feed: one for the dimensions for populating the row and column headers,
and one for the measures to populate the body of the table. The grid has already
established a convention for asking for aggregates computed on the server,
although this can be overridden using parameterMap anyway.

In some applications one may not want  aggregation on some or all dimenions on the pivot grid and jut show the raw data.

In the .NET for Ajax PivotGrid, you can set a caption for all fields, row and column. This does not seem possible in the kendo based version (MVC). The only property I see on a column or row is if we want it expanded by default or not.

Here is how it is done on the Webforms version of the control

 <Fields>
                <telerik:PivotGridRowField DataField="Rep" ZoneIndex="1" Caption="Rep" 
                </telerik:PivotGridRowField>

Add the option to connect to Microsoft SSAS Tabular mode using Kendo UI PivotGrid

It would be nice to have a chart chooser for the PivotGrid build in (a dropdown that i can place anywhere). At the moment it is really difficult to display a PivotGrid in a chart or even change the chart type on the fly. This and the convertion to a chart could be build in so every developer don't need to worry about this.

What i visualize is a dropdown menu which shows all posible chart types. If i choose one, the pivot grid disapears and on it's position the choosen chart apears (optional with the PivotConfigurator in the side). From a chart i can switch back to the pivot grid or choose another chart type.

Add format configuration for Pivot schema rows and columns. Like aggregates config.

Make the COUNT measure count only distinct itens on PivotGrid. For instance, let's say we have a dataSource like this:

var dados = [{ PersonID: 2958, Address: "5h St"},{ PersonID: 2958, Address: "​Lexington Ave"},{ PersonID: 2958, ​Address: "76th Street"}]

Note that it is only 1 person, which has 3 address.. if I wanted to use the COUNT measure on the Address, it is correct (it counts 3 itens). But when I use the COUNT measure on the PersonID, it also counts 3 itens, but there is only one personID. I think it should count distinct values for the data in the measure.

On a screen, showing the totals to the left and bottom of the data it summarizes makes no sense.

When a user drills through a data set, the totals are the deciding factors for which nodes to expand.

Advanced functionality in xml/a binding should be available to local binding. Also ability to define new binding protocols.

Hi Team,

I would like to request Selection/multi-cell drag selection for the Kendo UI PivotGrid. 

Thank you!

Setting dimensions in pivot grid with fields of data type "number" or "date" the filter menu opens with conditions and input component as if the fields are of "string" type,  how do I configure the filter menu to act according it's data type. 

In case of date/number data type, in the Include fields filter the selected  items are not persistent - when a user selects some of the values and reenters the include fields the selected values are not saved.

Regards

Miron Konrad

I've bound the PivotGrid to a XMLA-WebService (with Mondrian as Backend).

In the Datasource I've defined the error-Function.

When PivotGrid requests Data and Mondrian runs an Exception, following XMLA is transferred:

<?xml version="1.0" encoding="ISO-8859-1"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" >
<SOAP-ENV:Header>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<SOAP-ENV:Fault>
  <faultcode>SOAP-ENV:Server.00HSBE02</faultcode>
  <faultstring>XMLA Discover unparse results error</faultstring>
  <faultactor>Mondrian</faultactor>
  <detail>
    <XA:error xmlns:XA="http://mondrian.sourceforge.net">
      <code>00HSBE02</code>
      <desc>The Mondrian XML: Error in executeQuery. Stackdump follows. See SQL logfile for more info.&#13;&#10;Error Stack Dump, time : 22.11.2018 13:19:16&#13;&#10;   com.microsoft.sqlserver.jdbc.SQLServerException: Die Sachbearbeiter-Spalte wurde für &#39;Beschluss&#39; mehrmals angegeben.&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)&#13;&#10;&#9;at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)&#13;&#10;&#9;at net.abit.base.support.StatementImpl.executeQuery(StatementImpl.java:504)&#13;&#10;&#9;at mondrian.rolap.SqlStatement.execute(SqlStatement.java:201)&#13;&#10;&#9;at mondrian.rolap.RolapUtil.executeQuery(RolapUtil.java:350)&#13;&#10;&#9;at mondrian.rolap.RolapUtil.executeQuery(RolapUtil.java:303)&#13;&#10;&#9;at mondrian.rolap.SqlMemberSource.getMemberCount(SqlMemberSource.java:149)&#13;&#10;&#9;at mondrian.rolap.SqlMemberSource.getLevelMemberCount(SqlMemberSource.java:142)&#13;&#10;&#9;at mondrian.rolap.SmartMemberReader.getLevelMemberCount(SmartMemberReader.java:158)&#13;&#10;&#9;at mondrian.rolap.RolapSchemaReader.getLevelCardinality(RolapSchemaReader.java:320)&#13;&#10;&#9;at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)&#13;&#10;&#9;at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)&#13;&#10;&#9;at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)&#13;&#10;&#9;at java.lang.reflect.Method.invoke(Method.java:498)&#13;&#10;&#9;at mondrian.rolap.RolapUtil$2.invoke(RolapUtil.java:111)&#13;&#10;&#9;at com.sun.proxy.$Proxy33.getLevelCardinality(Unknown Source)&#13;&#10;&#9;at mondrian.olap4j.MondrianOlap4jExtra.getLevelCardinality(MondrianOlap4jExtra.java:74)&#13;&#10;&#9;at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateDimension(RowsetDefinition.java:3970)&#13;&#10;&#9;at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateCube(RowsetDefinition.java:3915)&#13;&#10;&#9;at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateCatalog(RowsetDefinition.java:3897)&#13;&#10;&#9;at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateImpl(RowsetDefinition.java:3885)&#13;&#10;&#9;at mondrian.xmla.Rowset.populate(Rowset.java:201)&#13;&#10;&#9;at mondrian.xmla.Rowset.unparse(Rowset.java:173)&#13;&#10;&#9;at mondrian.xmla.XmlaHandler.discover(XmlaHandler.java:2903)&#13;&#10;&#9;at mondrian.xmla.XmlaHandler.process(XmlaHandler.java:676)&#13;&#10;&#9;at mondrian.xmla.impl.DefaultXmlaServlet.handleSoapBody(DefaultXmlaServlet.java:517)&#13;&#10;&#9;at mondrian.xmla.XmlaServlet.doPost(XmlaServlet.java:318)&#13;&#10;&#9;at javax.servlet.http.HttpServlet.service(HttpServlet.java:660)&#13;&#10;&#9;at javax.servlet.http.HttpServlet.service(HttpServlet.java:741)&#13;&#10;&#9;at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231)&#13;&#10;&#9;at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)&#13;&#10;&#9;at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)&#13;&#10;&#9;at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193)&#13;&#10;&#9;at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166)&#13;&#10;&#9;at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199)&#13;&#10;&#9;at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96)&#13;&#10;&#9;at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140)&#13;&#10;&#9;at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80)&#13;&#10;&#9;at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:651)&#13;&#10;&#9;at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87)&#13;&#10;&#9;at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342)&#13;&#10;&#9;at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:498)&#13;&#10;&#9;at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)&#13;&#10;&#9;at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:796)&#13;&#10;&#9;at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1374)&#13;&#10;&#9;at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)&#13;&#10;&#9;at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)&#13;&#10;&#9;at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)&#13;&#10;&#9;at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)&#13;&#10;&#9;at java.lang.Thread.run(Thread.java:748)&#13;&#10;&#13;&#10;</desc>
    </XA:error>
  </detail>
</SOAP-ENV:Fault>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

in Result the error-Parameter contains:

As you can see, the Details are missing. This wouldn't be worse - but additional xhr is away (null) - so manually parsing the result is impossible.

It should be possible to use message details - or having access to the complete Response (but xhr is not present).

As of August 2018, the PivotConfigurator can show a list of dimensions and measures.  However, the control could be improved by optionally adding the members of dimension attributes to the control.   By allowing users to drag-and-drop members, they can add a dimension and instantly filter by the selected member.   This would speed up the process of designing sophisticated queries.  Thanks!

Connection with Azure Analysis Services not work.

Hi Team,

I am working on one of client application and we are using pivot grid control jQuery version to connect and pull data from cube but one things which we are missing is getting the cellset properties(back_color) from cube data. 

There are certain business rules applied on the cube to show data with different color schemes. Now based on the cube data color properties , We want to get that as a part of kendo UI pivot grid for the cells.

 

We saw excel supports that feature, where it can understand the cell set (back color) properties and render the back color. I am also attaching snapshots from excel.

Below is the sample mdx query and highlighted underlined holds cell properties

 

 

SELECT NON EMPTY { [Measures].[QCV to Deploy], [Measures].[Initial Calculated Quota], [Measures].[Quota Deployed], [Measures].[Remaining QCV] }

ON COLUMNS, NON EMPTY { ([SalesMetric].[Sales Metric Key].[Sales Metric Key].ALLMEMBERS * [SalesMetric].[Sales Metric Name].[Sales Metric Name].ALLMEMBERS ) }

DIMENSION PROPERTIES MEMBER_CAPTION ON ROWS FROM (

SELECT ( { [SalesOrganization].[SalesOrganization].[All], [SalesOrganization].[SalesOrganization].&[108]} )

ON COLUMNS FROM [QuotaAllocation]) WHERE ( [SalesOrganization].[SalesOrganization].CurrentMember )

CELLPROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS 

Currently the Pivot Grid have both Column and Row that will be used to be on display for Jquery type.

Please add in additional Filter like others software givers on pivotgrid. 
This additional Filter is not used for display, as it is used for filter only.

If i have a hierarchy location, for example country, city and postal code, i can only use location as field and can't use country, city or postal code. If i want to use them indiviually i would have to configure them as extra attributes in the olap schema.

It would be nice, if these hierarchies could be used as fields.

Kendo pivotgrid should show non-empty members in filters - currently when we open the row or column filter to see the members in the dimension all the members in the dimension seem to be shown. At least we need a field to let us indicate that the filter entries should be filtered out using 'non empty' clause.

Kendo pivotgrid - clicking on a data cell should produce correct row/column/filter items info so that the info can be used for custom drilldowns and drillthroughs.  Currently the info produce by cells defined by All row/column is incorrect in the interior of the pivotgrid