Hi Team,
I would like to request Selection/multi-cell drag selection for the Kendo UI PivotGrid.
Thank you!
Hello,
I have a problem with KendoPivotGrid auto height while using jQuery 3.5.5.
See Dojo
The same issue was previously in KendoGrid, but now it's solved.
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. Error Stack Dump, time : 22.11.2018 13:19:16 com.microsoft.sqlserver.jdbc.SQLServerException: Die Sachbearbeiter-Spalte wurde für 'Beschluss' mehrmals angegeben. 	at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689) 	at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696) 	at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155) 	at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616) 	at net.abit.base.support.StatementImpl.executeQuery(StatementImpl.java:504) 	at mondrian.rolap.SqlStatement.execute(SqlStatement.java:201) 	at mondrian.rolap.RolapUtil.executeQuery(RolapUtil.java:350) 	at mondrian.rolap.RolapUtil.executeQuery(RolapUtil.java:303) 	at mondrian.rolap.SqlMemberSource.getMemberCount(SqlMemberSource.java:149) 	at mondrian.rolap.SqlMemberSource.getLevelMemberCount(SqlMemberSource.java:142) 	at mondrian.rolap.SmartMemberReader.getLevelMemberCount(SmartMemberReader.java:158) 	at mondrian.rolap.RolapSchemaReader.getLevelCardinality(RolapSchemaReader.java:320) 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 	at java.lang.reflect.Method.invoke(Method.java:498) 	at mondrian.rolap.RolapUtil$2.invoke(RolapUtil.java:111) 	at com.sun.proxy.$Proxy33.getLevelCardinality(Unknown Source) 	at mondrian.olap4j.MondrianOlap4jExtra.getLevelCardinality(MondrianOlap4jExtra.java:74) 	at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateDimension(RowsetDefinition.java:3970) 	at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateCube(RowsetDefinition.java:3915) 	at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateCatalog(RowsetDefinition.java:3897) 	at mondrian.xmla.RowsetDefinition$MdschemaDimensionsRowset.populateImpl(RowsetDefinition.java:3885) 	at mondrian.xmla.Rowset.populate(Rowset.java:201) 	at mondrian.xmla.Rowset.unparse(Rowset.java:173) 	at mondrian.xmla.XmlaHandler.discover(XmlaHandler.java:2903) 	at mondrian.xmla.XmlaHandler.process(XmlaHandler.java:676) 	at mondrian.xmla.impl.DefaultXmlaServlet.handleSoapBody(DefaultXmlaServlet.java:517) 	at mondrian.xmla.XmlaServlet.doPost(XmlaServlet.java:318) 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:660) 	at javax.servlet.http.HttpServlet.service(HttpServlet.java:741) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:231) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) 	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53) 	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:193) 	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:166) 	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:199) 	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:96) 	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:140) 	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:80) 	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:651) 	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:87) 	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:342) 	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:498) 	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66) 	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:796) 	at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1374) 	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) 	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) 	at java.lang.Thread.run(Thread.java:748) </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!
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.
Now if you set filterable true for KendoPivotGrid you get two options - Include Fields and Fields Filter. In some cases you need only one of this options and it is not good to be with one option - filterable.
I would like to see a persist state feature like in the grid control applied to the pivot grid. A complex cube state is difficult for our users to set up each time the page is loaded. It would be great to save the current state of the pivotgrid and restore it on future visit.
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.
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>
Expanding programmatically all paths in a level in a pivot grid is coumbersome. One should be able to expand all itlems in a level. Also when one row.expand and column.expand configuration should work for all levels.
In some applications one may not want aggregation on some or all dimenions on the pivot grid and jut show the raw data.
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 does not allow us to hide 'All' row/column.'All' row/column is not always needed in a OLAP report. Excel would allow us to hide/eliminate subtotall rows/columns. pivotgrid needs similar functionality. In general emulate Excel pivotgrid functionality in kendo pivotgrid
Kendo pivotgrid currently has only row and column filters. Filters and Filter area are also important. See other pivotgrid implementations - especially DevExpress ASPxPivotgrid and Excel pivot table
What we would need is te possibility to show the percentage of the gand total summary. For example: row / column value 1 / 2 2 / 3 3 / 5 summary / 10 => change calculation to percent of grand total 1 / 20% 2 / 30% 3 / 50%
The PivotConfigurator is very static. It would be nice to change the layout. For example some options: - Hide / visibility of all four elements (Row, Column, Measure, Fieldlist) - Position of all four elements (Row, Column, Measure, Fieldlist)
Problem: The values and fieldnames can be very long or very short. Based on that, values and fieldnames are often truncated or lost in a way to wide column. That behavior has many downsides: - The PivotGrid need much more space then it should - Long values and fieldnames can't be read - It's totally not responsive and looks bad Competitors solution: - http://www.igniteui.com/pivot-grid/all-grid-features - http://webix.com/pivot/ Problem-solving approach: - Show resize icon when hovering over a the bar between two columns - Resize this column to it's min. width (value or fieldname) after a double click on this bar - Manual resizing of the column by drag and drop of this bar - Automatically size columns to there min. width on initialisation
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.