51
ParamQuery Grid
Recent Posts
52
Bug Report / Re: ESC does not restore value after Delete in editor mode (v11)
« Last post by paramvir on April 12, 2026, 09:47:09 pm »Thanks for reporting the issue, it's a bug and its fix is in progress.
53
Bug Report / ESC does not restore value after Delete in editor mode (v11)
« Last post by luckduck on April 10, 2026, 11:20:05 am »Hello,
I noticed a difference in behavior between pqGrid v9 and v11.
1. In pqGrid v9:
When a cell is in editor mode, if I press the Delete key to clear the content and then press ESC, the original value is restored.
2. In pqGrid v11:
After pressing the Delete key, the cell value is already removed, and pressing ESC does not restore the original value.
Could you please confirm if this is an intended change or a bug?
This behavior can also be reproduced on the demo site.
pqGrid9 (https://paramquery.com/pro/demos91/editing_instant)
pqGrid11 (https://paramquery.com/pro/demos/editing_instant)
Thank you.
I noticed a difference in behavior between pqGrid v9 and v11.
1. In pqGrid v9:
When a cell is in editor mode, if I press the Delete key to clear the content and then press ESC, the original value is restored.
2. In pqGrid v11:
After pressing the Delete key, the cell value is already removed, and pressing ESC does not restore the original value.
Could you please confirm if this is an intended change or a bug?
This behavior can also be reproduced on the demo site.
pqGrid9 (https://paramquery.com/pro/demos91/editing_instant)
pqGrid11 (https://paramquery.com/pro/demos/editing_instant)
Thank you.
54
Help for ParamQuery Pro / Re: Another 11.1.0 bug
« Last post by paramvir on April 06, 2026, 08:54:03 pm »Setting focusModel: { focusable: false } specifically restricts focus via pointer devices (mouse/touch). It does not prevent focus via the Tab key or programmatic API calls.
When the filter dropdown opens, the host grid programmatically sets focus to the first option to ensure keyboard accessibility. With focusable: false enabled in the filter's gridOptions, users are prevented from focusing options via mouse clicks, but the automated programmatic focus still functions as intended.
If you are experiencing a different behavior, please provide a JSFiddle or a list of steps to reproduce the issue.
When the filter dropdown opens, the host grid programmatically sets focus to the first option to ensure keyboard accessibility. With focusable: false enabled in the filter's gridOptions, users are prevented from focusing options via mouse clicks, but the automated programmatic focus still functions as intended.
If you are experiencing a different behavior, please provide a JSFiddle or a list of steps to reproduce the issue.
55
Help for ParamQuery Pro / Re: Another 11.1.0 bug
« Last post by jplevene on April 05, 2026, 04:09:03 am »Do you have a temporary fix to this until the next version is released, or is the next version with the bug fixes going to be released soon.
56
Help for ParamQuery Pro / Re: pqGrid Paste Issue with Indian Number Format (#VALUE! Error) - Reactjs
« Last post by paramvir on April 02, 2026, 11:06:56 pm »Yes it's possible to paste the numbers in a string column or any type of column in pqgrid / spreadsheet with a small workaround.
Following is the solution for "Standard" number format used in your Excel file
Step 1. First monkey patch the pq.isDateFormat function, this ensures that the correct number formatting is called.
Step 2.
Please let me know if you need furtehr assistance.
Following is the solution for "Standard" number format used in your Excel file
Step 1. First monkey patch the pq.isDateFormat function, this ensures that the correct number formatting is called.
Code: [Select]
const _isDateFormat = pq.isDateFormat;
pq.isDateFormat = function(fmt){
return (fmt == 'Standard')? false: _isDateFormat.call(this, fmt);
}
Step 2.
Code: [Select]
beforePaste(evt, ui){
debugger
ui.rows.forEach(row =>{
row.forEach(cell=>{
if(cell.prop?.format == "Standard"){
//either
cell.prop.format = "#,##0.00";
//or
cell.prop.format = "";
}
})
})
},
Please let me know if you need furtehr assistance.
57
Help for ParamQuery Pro / Re: pqGrid Paste Issue with Indian Number Format (#VALUE! Error) - Reactjs
« Last post by Punit on April 01, 2026, 10:49:04 am »From our side, the pqGrid column data type is set to string.
Could you please confirm if it is possible to convert (copied from Excel in Indian number format) the pasted values into string during the paste process??
Could you please confirm if it is possible to convert (copied from Excel in Indian number format) the pasted values into string during the paste process??
58
Help for ParamQuery Pro / Re: pqGrid Paste Issue with Indian Number Format (#VALUE! Error) - Reactjs
« Last post by paramvir on March 27, 2026, 07:24:55 pm »Thanks for sharing the details.
The format you’re using is currently not supported in pqGrid. However, support for this format is planned and will be included in the upcoming release.
In the meantime, if you’re able to modify the Excel file, please use the equivalent custom format: "#,##0.00". This format is fully supported and should work as expected.
The solution is provided in my next post.
In the meantime, if you’re able to modify the Excel file, please use the equivalent custom format: "#,##0.00". This format is fully supported and should work as expected.
The solution is provided in my next post.
59
Help for ParamQuery Pro / pqGrid Paste Issue with Indian Number Format (#VALUE! Error) - Reactjs
« Last post by Punit on March 26, 2026, 06:28:02 pm »I am facing an issue while copying values from Excel and pasting them into pqGrid.
Issue Description:
When I copy a number in Indian format from Excel (e.g., 3,69,92,674.00) and paste it into pqGrid, the value is getting converted to #VALUE! instead of the correct numeric value.
Current Implementation:
I have implemented the following pqGrid events to track the pasted data:
paste: function (evt, ui) {
},
beforePaste: function (evt, ui) {
console.log("Before Paste (raw data): ", ui.clipboardData);
console.log("Parsed rows: ", ui.rows);
},
change: function (evt, ui) {
if (ui.source === 'paste') {
console.log("After Paste (final data): ", ui.updateList);
ui.updateList.forEach(row => {
console.log("Row Data:", row.newRow);
});
}
}
In all console logs (paste, beforePaste, and change events), the value is already coming as #VALUE!.
The actual Excel value (3,69,92,674.00) is not being received at any stage.
Kindly suggest the resolution for this issue.
Issue Description:
When I copy a number in Indian format from Excel (e.g., 3,69,92,674.00) and paste it into pqGrid, the value is getting converted to #VALUE! instead of the correct numeric value.
Current Implementation:
I have implemented the following pqGrid events to track the pasted data:
paste: function (evt, ui) {
},
beforePaste: function (evt, ui) {
console.log("Before Paste (raw data): ", ui.clipboardData);
console.log("Parsed rows: ", ui.rows);
},
change: function (evt, ui) {
if (ui.source === 'paste') {
console.log("After Paste (final data): ", ui.updateList);
ui.updateList.forEach(row => {
console.log("Row Data:", row.newRow);
});
}
}
In all console logs (paste, beforePaste, and change events), the value is already coming as #VALUE!.
The actual Excel value (3,69,92,674.00) is not being received at any stage.
Kindly suggest the resolution for this issue.
60
Help for ParamQuery Pro / Re: Invalid Data Display (#VALUE!) on Excel Paste In React
« Last post by Punit on March 26, 2026, 04:03:25 pm »When I copy data from Excel in Indian number format and paste it into pqGrid, it doesn’t work. The Indian number format is not supported