Messages

1

Help for ParamQuery Pro / Re: Report generating "xml parse" error at 32768 records

« on: March 30, 2022, 01:10:31 am »

Ack. I figured it out (feel free to delete this thread if you like).

The page is a dynamic one ... and there were a couple of stray invisible characters on it, right before the call to pqgrid to assemble the table. Removing those solved the problem. Why they didn't affect smaller datasets is unclear, but I'm declaring victory.

Sorry for the trouble!

Ron

2

Help for ParamQuery Pro / Report generating "xml parse" error at 32768 records

« on: March 29, 2022, 07:18:14 pm »

Hi Paramvir,

Wrestling with another weird issue. I have two reports on our system, one of which is humming along fine generating reports containing over 100,000 records ... while the other one generates a parsing error at precisely 32,768 records (the limit of an integer).

Here's the error message:
error on line 25 at column 262: xmlParseEntityRef: no name
error on line 25 at column 262: Encoding error

Line 25 is the line that contains our data, which is in a JSON array: [["value","value"...],["value",value"...]] and so on. We're not using objects/labels for this data, just arrays. That's true of both tables ... the one that works, and the one that doesn't.

I'm using the exact same Object definition in the two models. The Column definition is a bit different, but only because the report that's giving me problems has much less data per record ... 9 columns, versus 20.  Moreover, if there were a problem with the column definition I don't think it would be giving me 32767 records without problems.

We're not trying to do any column totals, rendered cells using calculations, or anything like that. Just a table of data, mostly strings, a few dates and a couple of integer values.  This is true of both tables.

I've tried several sets of data, thinking it might be a corrupted record; it always stops at the magic 32,768 integer limit. If I give it 32767 records, the table displays without problems. The problem is also not on the server side; all of the records are being assembled and appearing in the data array in the browser's source code, the browser just isn't parsing it beyond 32,767 records ... except in the "working" model which has no problem with more than 100,000 records.

Any thoughts on what I should be looking for on this? It has to have something to do with that 32,768 integer limit.

Below is the column model, followed by a sample of a couple of records of data.  Thank you!

var colModel = [{
  title: "Trainee ID",
  dataType: "string",
  maxWidth: 100,
  minWidth: 100,
  filter: {
    crules: [{
      condition: 'begin'
    }]
  }
}, {
  title: "Trainee Name",
  dataType: "string",
  maxWidth: 200,
  minWidth: 100,
  filter: {
    crules: [{
      condition: 'begin'
    }]
  }
}, {
  title: "Course ID",
  dataType: "string",
  maxWidth: 100,
  minWidth: 100,
  filter: {
    crules: [{
      condition: 'range'
    }]
  }
}, {
  title: "Course Title",
  dataType: "string",
  filter: {
    crules: [{
      condition: 'range'
    }]
  }
}, {
  title: "Status",
  dataType: "string",
  minWidth: 100,
  maxWidth: 100,
  filter: {
    crules: [{
      condition: 'range'
    }]
  }
}, {
  title: "Score",
  dataType: "integer",
  maxWidth: 70,
  minWidth: 70,
  filter: {
    crules: [{
      condition: 'between'
    }]
  }
}, {
  title: "First Date",
  dataType: "date",
  maxWidth: 100,
  minWidth: 100,
  exportRender: true,
  format: "M dd, yy",
  filter: {
    crules: [{
      condition: 'between'
    }]
  }
}, {
  title: "View Count",
  dataType: "integer",
  maxWidth: 70,
  minWidth: 70,
  filter: {
    crules: [{
      condition: 'between'
    }]
  }
}, {
  title: "Viewing Dates",
  minWidth: 300,
  menuIcon: false,
  dataType: "string"
}];

Here's a snippet of the data.  Note that the string of dates in the last field of each record (spelled out as March 26, 2022 and so on) is not meant to be parsed; those dates all appear as text in one table cell.

var reportdata = [
  ["ba2ead76-cbae-4bd1-ab24-cfb03b9e82ff", "Trainee One", "E_3389", "Lockout/Tagout Affected Employees", "COMPLETED", "90", "03/26/2022", "1", "March 26, 2022"],
  ["47063f83-ca57-4d30-95e6-dbfc95468d25", "Trainee Two", "E_3443", "Dealing With Drug & Alcohol Abuse for Managers", "COMPLETED", "90", "03/25/2022", "3", "March 25, 2022/March 25, 2022/March 25, 2022"]
]

3

Help for ParamQuery Pro / Re: RefreshCell in a filtered grid updating the wrong cell

« on: March 22, 2022, 04:08:37 pm »

Thank you Paramvir!

filterModel {hideRows:true} seems to be what I was looking for!  I can back out my workaround with the next server update.

I'll also try to get a jsfiddle up so you can check on the issue I ran into using the updateRow approach (once the dust settles here in a day or two ... I'm working around the clock at the moment.)

Is there any performance downside to using the filterModel approach?  Does that slow down grid filtering or anything like that? (It doesn't appear to, but I thought I'd check with you.)

Thanks again!

4

Help for ParamQuery Pro / Re: RefreshCell in a filtered grid updating the wrong cell

« on: March 22, 2022, 02:33:31 pm »

I've got a workable workaround for the issue. If there's a better way to identify the original 0-based position of a row in the source data array, please let me know!

1) The first item in each element in the array is a sequence number identifying a record in the database
2) As the data set is built, I'm now prepending that with a zero-based index number.  So, if the first sequence number is 23432343, it becomes 0-23432343
3) In the browser, I'm parsing that into an original row reference (ie the position of element in the data array) and the original sequence number.
4) I'm referencing that original row reference when updating the traineelist source data, but the displayed rowIndx when updating the cell.

Here's the code:

 cellDblClick: function( event, ui ) {
            var sequence = ui.rowData[0].split("-") //gets the original sequence number and the row index number in the source data
            if(ui.colIndx==2){
            getreg(sequence[1])} //calls a function to display a registration form
        else{
            if(ui.dataIndx==3){  //this is the "active/suspended" status column;
            var usr = document.getElementById("user").value;
            var com = document.getElementById("co").value;
            var row = ui.rowIndx;         
            var grid = this;
           $.ajax({
            type: "POST",
            dataType: "json",
            url: "/suspenduser",
            data: {seq:sequence[1],val:ui.rowData[3],user:usr,co:com},
            success: function(data){
            traineelist[sequence[0]][3]=data.val; // uses the prepended original element number from the source data
            grid.refreshCell( { rowIndx: row, dataIndx: 3 } );
           $("#message").html(data.message);
           $('#message').show();
           $('#message').fadeOut(3000);
            },
});
        }
        }},

5

Help for ParamQuery Pro / Re: RefreshCell in a filtered grid updating the wrong cell

« on: March 22, 2022, 01:23:37 pm »

Hi Paramvir,

Unfortunately, that didn't do the trick. In fact, it made it worse ... now the cell doesn't update even when the table is unfiltered.  Before, it would update when it was unfiltered (ie every row was the original, unfiltered row) but not when it was filtered down to a few rows. 

What appears to be throwing it off is that the row reference (rowIndx) retrieved when the user double-clicks the cell is the row number relative to the filtered data being displayed, while when updating the cell after the ajax transaction completes the rowIndx always goes to the corresponding row in the unfiltered (total) list, not the filtered list.

Example: if I have 100 rows, and I filter out the first 20 and the last 77, leaving three rows, the rowIndx value at the start of the transaction will be 0,1 or 2(one of the three visible rows) but when the response returns the cell in row 0, 1, or 2 of the original table gets updated. If I reset the filter, I can see the changed cell in that row near the top.

traineelist is a reference to the source array of data (dataModel: {data: traineelist},)

The 4th zero-based element in each sub-array within traineelist holds the Status value. Updating that, and then calling grid.RefreshCell, works well except when the row references don't correspond to the original data array (ie the table was filtered at the start of the transaction.)

Sorting doesn't cause any problem, only filtering.

Using updateRow as you suggested doesn't appear to correct that.  I think what I'm looking for is a way to reference the row by its original position in the source data, not its current position in the filtered row.

Here's the code I have, with your change and my original part commented out, along with some additional comments.

if(ui.dataIndx==3){
            var usr = document.getElementById("user").value;
            var com = document.getElementById("co").value;
            var row = ui.rowIndx;   //this is row 0 of the filtered table, row 21 of the unfiltered table in my example
            var grid = this;
           $.ajax({
            type: "POST",
            dataType: "json",
            url: "/suspenduser",
            data: {seq:ui.rowData[0],val:ui.rowData[3],user:usr,co:com},
            success: function(data){
            console.log(row);  //shows row relative to the current display
            console.log(data.val);   //shows returned value, correctly
            console.log(ui.rowData[0]);   //shows col 0 value (a hidden identifier for the record on the server) correctly.

            //old code; cell would update if grid was unfiltered
            //traineelist[row][3]=data.val;
            //grid.refreshCell( { rowIndx: row, dataIndx: 3 } );  //this is updating row 0 of the total, unfiltered table

              //new code; cell never updates   
               grid.updateRow( { 
               rowIndx: row,
          newRow: { 3: data.val }
            });

           $("#message").html(data.message);
           $('#message').show();
           $('#message').fadeOut(3000);
            },
});
        }

The server receives the call and responds with the correct status change (Active or Suspended) but the cell doesn't update. Previously, it did with the column unfiltered.

Thanks for your help Paramvir. Please let me know if anything stands out.

  UPDATE: I tried a test where, using my old code, I used:

traineelist[4][3]=data.val;
grid.refreshCell( { rowIndx: row, dataIndx: 3 } );

This locks the ajax return to updating the 5th array in the original data. 

Then I tried filtering the data so that the original zero-based row 4 was always visible. That worked. If I double-clicked the cell that was originally in row 4, it would update even if, after filtering, it was in row 3 or something.

So this is telling me that the problem is finding the correct array element to update in traineelist, yes?

6

Help for ParamQuery Pro / RefreshCell in a filtered grid updating the wrong cell

« on: March 22, 2022, 10:04:42 am »

Hi Paramvir,

This may be because I've been coding for too long  but I've got a bug that I can't figure out.

Below is the snippet of troublesome code. What I'm doing is letting the user double-click a cell. That sends an Ajax message to the server to toggle the cell's value (active/suspended). The server responds with the new cell contents, and a message displayed elsewhere on the screen.

It all works fine EXCEPT when the table is filtered. Let's say I filter it down to one row. It appears that the row that's being captured on the 4th line (var row = ui.rowIndx) is returning the row number in the filtered array (ie. 0) rather than the overall row number. Later on, in line 14, the cell in the 0 row of the entire table is changed (that is, in the hidden row at the very top of the table). So, while everything gets to the server alright, the wrong cell in the table gets updated by the response.

What I want to do is reference the row that the "clicked" cell is in on the entire, unfiltered table, and update the fourth cell (dataIndx 3) in that row.

I'm guessing I need something different in line 4 or 14, but I'm not sure what.

          if(ui.dataIndx==3){
            var usr = document.getElementById("user").value;
            var com = document.getElementById("co").value;
            var row = ui.rowIndx;
            console.log(row);
            var grid = this;
           $.ajax({
            type: "POST",
            dataType: "json",
            url: "/suspenduser",
            data: {seq:ui.rowData[0],val:ui.rowData[3],user:usr,co:com},
            success: function(data){
            traineelist[row][3]=data.val;
           grid.refreshCell( { rowIndx: row, dataIndx: 3 } );
           $("#message").html(data.message);
           $('#message').show();
           $('#message').fadeOut(3000);
            },
});
        }

7

ParamQuery Pro Evaluation Support / Re: 'wdCenter' of undefined

« on: March 17, 2022, 05:08:35 am »

Makes sense, and it's easy enough to work within that constraint. Thank you Paramvir!  You've got a great product here.

8

ParamQuery Pro Evaluation Support / Re: 'wdCenter' of undefined

« on: March 14, 2022, 12:18:13 pm »

Thanks for the suggestion Paramvir,

Just to be sure that I understand the mechanism at work here, does this mean that the table doesn't render if it's loaded into a DIV (or, in our case, an iframe within a DIV) that's not visible (css display:none), hence the need to call refresh?

Ron

9

ParamQuery Pro Evaluation Support / Re: 'wdCenter' of undefined

« on: March 11, 2022, 12:16:32 am »

A number of people have reported this error, and I ran into it myself.

After a series of tests, looking at issues like the presence of tables in iframes and so on, I finally tracked down the culprit (at least in my case): 

I was putting multiple tables into jQuery tabs on the page, using the jQuery UI function described here: https://jqueryui.com/tabs/

Having multiple tables on a page in these jQuery tabs in some way triggers the "wdCenter" error.  Simply removing those tabs makes the error go away.  Most likely, Paramquery is using this jQuery UI function for its tabbed tables. (That approach might work for some ... letting Paramquery handle the tabs ... but in our case some of the tabs on the page don't contain tables.)

The solution is using a different approach to setting up page tabs without using that jQuery UI function (there are a number of other ways to accomplish the same UI effect.)

10

ParamQuery Pro Evaluation Support / Re: JSZip is not a constructor

« on: February 09, 2022, 05:46:25 am »

I ran into the same issue, and finally figured it out.

There's an error in the Tutorial; it instructs you to add jszip.js toward the end of the header. It needs to be added before pqgrid.min.js so that the latter can recognize that jszip is installed when it loads.

Simply reordering those two lines in the header, putting jszip.js (or the minimized version) first, resolved the problem for me.