Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - nzxgq0

Pages: [1] 2
Thanks for responding. Unfortunately, there is no error, no log entry. User can drag the columns from the source but cannot drop them to the destination. Very strange.


I has been confused for a while. Sometimes Chrome doesn't allow user to modify the columns in ToolPanel.

ParamQuery Pro v8.1.0
Google Chrome Version 95.0.4638.69 (Official Build) (64-bit)

I haven't experienced such problem with Firefox or Microsoft Edge yet.


Help for ParamQuery Pro / Re: Apply filter to Grid at Pivot mode (Pro 8.1.0)
« on: September 17, 2021, 12:10:31 pm »
Good news. The workaround is still working if using this to turn off the pivot mode (and to turn on by change the "false" to "true").
Code: [Select]
    if (pivot) {
            pivot: false

I still like to see the loadState working with pivot mode and filters.

Help for ParamQuery Pro / Apply filter to Grid at Pivot mode (Pro 8.1.0)
« on: September 17, 2021, 11:41:00 am »

Before 8.0.1, I have a workaround for this.
1. turn off the pivot mode for the grid
2. apply the filter to the grid
Code: [Select]
            oper: 'replace',
            mode: 'AND',
            rules: [
                { dataIndx: 'FacilityName', condition: 'begin', value: filterFacilityName },
3. turn on the pivot mode for the grid
However, with 8.0.1 and 8.1.0, it seems the workaround is not working any more. At the 2 step, it complains an error of "Uncaught !primary.getDMData".

By the way, the loadState for Pivot mode with filter values is still not working.  The details are at

Bug Report / Re: loadState failed when loading a grid (8.0.1)
« on: September 03, 2021, 03:50:58 pm »
Hi paramvir, this is a great news.

I tried Pro 8.1.0 and the issue mentioned above is fixed. However, it doesn't seem to support to restore the pivot state and the filters if any.
Meaning that if a Web user switched the grid from the normal mode to the pivot mode and left, it still displays the grid at the normal mode (the checkbox of pivot mode not checked and the columns are for normal mode) when coming back to that page.

I noticed that the pivot flag of the groupModel actually was not saved in the localStorage.  Any luck to enable it?


Please use groupChange event instead of groupOption event.

Code: [Select]
groupChange: function(){

Try this if the above doesn't work
Code: [Select]
groupChange: function(){
  var grid = this;
Hi paramvir, it looks the groupChange event is not fired when dragging and dropping a column on the toolPanel but the groupOption is.
I tried your setTimeout method in groupOption and it worked. Thanks.

Thanks. I am using Pro 8.0.1.

Your approach by sorting the data inside the complete event is working at the first page load.

When updating the group by adding/removing columns into/from the row group, the sorting is gone.
Any idea to ensure the sort of the group?

Note the screenshots are not well ordered. See the FirstLoad, 2.AddStageToGroup then 3.SecondLevelNotSorted.
By the way, I tried "this.sort()" inside the groupOption event, but it didn't help.

Please check the image attached

Hello there,

we want to sort the grp column by default.
Code: [Select]
groupModel: {
            checkbox: true,
            checkboxHead: true,
            on: true,
            pivot: false, //pivotMode
            summaryInTitleRow: 'all', //to display summary in the title row.
            header: false, //hide grouping toolbar.
            grandSummary: true,
            titleInFirstCol: true,
            titleIndx: 'grp',
            fixCols: false,
            dataIndx: ['Item'],
            groupCols: [], //grouping along column axis.
            collapsed: [true, true],
            agg: {
                Count: "sum"
            showSummary: [false], //to display summary at end of every group.
            title: [
                "{0} ({1})",
                "{0} - {1}"
            summaryTitle: {
                sum: ""
            }        },
sortModel: {

            sorter: [{ dataIndx: 'grp', dir: 'up' }],
            space: true,
            ignoreCase: true,
            multiKey: null,
            single: false

However it is not working. It shows the small triangle but actually it is not sorting.

we also want to keep the group sorted at the pivot mode. Still no luck.
If we choose another column other than the "grp" column - such as the Item column in the example, it works.

Any idea? thanks.

Bug Report / Re: loadState failed when loading a grid (8.0.1)
« on: July 13, 2021, 04:16:47 pm »
another issue related to the pivot grid is that  some of the grid themes (JQuery themes such as Dark Hive, Dot Luv, Egg Plant, etc.) don't work well on the tool panel.

Bug Report / Re: loadState failed when loading a grid (8.0.1)
« on: July 08, 2021, 09:49:07 am »

I'm able to reproduce the issue while loadState with pivot, moving it to bug log for further analysis.

Thanks. With the following option, loadState always fails. I hope we can have a quick solution.
        toolPanel: {
            show: true  //show toolPanel initially.

Bug Report / loadState failed when loading a grid (8.0.1)
« on: July 07, 2021, 03:25:03 pm »
I have a pqgrid with the pivot feature.
However it fails when loading the grid with the state maintenance (
It looks "this.panes" is not initialized when calling the method.
Any idea?
Code: [Select]
22794      setAttrPanes: function() {
22795        this.$ele.attr("panes", this.panes.filter(function($ele) {
22796                return $":visible")
22797            }).length)
22798        }

Uncaught TypeError: Cannot read property 'filter' of undefined
    at _pq.cToolPanel.setAttrPanes (
    at _pq.cToolPanel.showHideColPane (
    at _pq.cToolPanel.setHtml (
    at _pq.cToolPanel.refresh (
    at _pq.cToolPanel.onGroupOption (
    at handleListeners (
    at $.<computed>.<computed>._pq._trigger (
    at _pq.cGroup.option (
    at _pq.cGroup.option (
    at $.<computed>.<computed>.fn.loadState (

It should go to ParamQuery Pro 7.4 ~ 7.6.1 however my subscription is need of renew and I cannot post it there.
We have several web pages created using pqgrid and when jumping between them. It often complains this JavaScript error.

Uncaught TypeError: Cannot redefine property: nodeClose
    at Function.defineProperty (<anonymous>)
    at new e.cTree (eval at <anonymous> (jquery-1.10.2.min.js:21), <anonymous>:16:16031)
    at HTMLDocument.eval (eval at <anonymous> (jquery-1.10.2.min.js:21), <anonymous>:16:15883)
    at HTMLDocument.dispatch (jquery-1.10.2.min.js:22)
    at HTMLDocument.v.handle (jquery-1.10.2.min.js:22)
    at Object.trigger (jquery-1.10.2.min.js:22)
    at init.triggerHandler (jquery-1.10.2.min.js:22)
    at $.<computed>.<computed>.o._create (eval at <anonymous> (jquery-1.10.2.min.js:21), <anonymous>:10:1248)
    at $.<computed>.<computed>._create (jquery-ui.js:144)
    at $.<computed>.<computed>._super (jquery-ui.js:129)

Refreshing fixes it but it is too annoying.
ParamQuery Pro 7.1.0 is OK.

Any thoughts?

Help for ParamQuery Pro / How to auto adjust column width
« on: October 29, 2020, 01:25:24 pm »

I have a grid which allows user to select the columns to display. Two issues:

1. Is there a way to automatically adjust the grid's column width based on user's selection?

2. How to set the font size or the row height on the selection dialog?


For large datasets, it's possible to divide one ajax call into multiple calls and keep updating the as more data arrives from server.

Server side script receives current page and records per page from grid and sends the requested data back.

Code: [Select]
postData: function () {
                return {
                    pq_curpage: pqIS.requestPage,
                    pq_rpp: pqIS.rpp

These 2 examples use this methodology:

Thanks. It solves my problem.
By the way, I found that the local export functionality has its limits. For example, it's OK to export 200K records as Excel but it fails when the count of the records reaches 300K. But the upper limit is larger if exporting as HTML.

Pages: [1] 2