Author Topic: Issue with Date Filters in ParamQuery Grid with Custom Date Formats  (Read 223 times)

TenarisDev

  • Pro Enterprise
  • Newbie
  • *
  • Posts: 7
    • View Profile
Hello Support Team,

We are encountering an issue with date filters in ParamQuery Grid when the date column is formatted using a custom format function. Here are the steps to reproduce the problem:

1. Go to the ParamQuery demo: https://paramquery.com/pro/demos/filter_date#
2. Modify the singleFilter option to false in the configuration and rerun the demo:
menuUI: {
    singleFilter: false
}
3. Try to filter the "Order Date" column using both "Greater Than" and "Less Than" options (see attachment):
Select the first date from the date picker.
Select the second date from the date picker.

4. Observed Behavior:

The filter does not apply correctly.
The second date textbox is left empty.
An error appears in the console:
jquery-ui.min.js:9 Uncaught TypeError: t.charAt is not a function
    at s.formatDate (jquery-ui.min.js:9:8028)
    at s._formatDate (jquery-ui.min.js:9:20968)
    at s._selectDay (jquery-ui.min.js:9:4109)
    at HTMLTableCellElement.selectDay (jquery-ui.min.js:9:11648)
    at HTMLTableCellElement.dispatch (jquery-2.2.4.min.js:3:7537)
    at r.handle (jquery-2.2.4.min.js:3:5620)
We would appreciate your assistance in resolving this issue.

Thank you in advance for your support.
Best regards.

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 6310
    • View Profile
Re: Issue with Date Filters in ParamQuery Grid with Custom Date Formats
« Reply #1 on: August 23, 2024, 08:56:01 am »
Thank you for reporting issue, it's found that filter.init callback is not called for the 2nd filter condition in the filter menu.

This has been fixed in the upcoming version.
« Last Edit: August 23, 2024, 08:57:59 am by paramvir »

paramvir

  • Administrator
  • Hero Member
  • *****
  • Posts: 6310
    • View Profile
Re: Issue with Date Filters in ParamQuery Grid with Custom Date Formats
« Reply #2 on: November 20, 2024, 12:16:43 pm »
This has been fixed since v10.0.0