date type and preDefined searchBuilder

arnodedecker

Link to test case:
Debugger code (debug.datatables.net):
Error messages shown:
Description of problem:
No Case No Messages No Error,

Scenario:
I got this from getDetails() on my searchBuilder, and it does work fine =>

    {
            "criteria": [
                {
                    "condition": "between",
                    "data": "Last Used",
                    "value": [
                        "2021-03-12",
                        "2021-07-12"
                    ]
                }
            ],
            "logic": "AND"
        }

The problem here:
- on the input fields, the datepicker does not appear
- when u change the input from 2021-03-12 to another start value, it does not change the data. (it looks the same as a normal text input field)

When I then manually add exactly the same filter. Everything works.

Has it something to do with the moment when I load the table in $(document).ready(function() {}) or ?

Anybody a clue what's going on here?

colin

We're happy to take a look, but as per the forum rules, please link to a test case - a test case that replicates the issue will ensure you'll get a quick and accurate response. Information on how to create a test case (if you aren't able to link to the page you are working on) is available here.

Cheers,

Colin

arnodedecker

https://jsfiddle.net/ysena1zj/9/

arnodedecker

You can see how the dates filter correctly.
Then u want to change the predefined date and there is no datepicker.
When u change it manually, it does not work either.

When u add a not predefined clause, everything does work.
It must be something with events or triggers being loaded on new elements (but not on the predefined ones)

colin

Thanks for that test case, that helped demonstrate the issue, and yep, I'm seeing it there too. I've raised it internally (DD-2038 for my reference) and we'll report back here when there's an update.

Cheers,

Colin

sandy

Hi @arnodedecker ,

Thanks for pointing this out! That should be the issue fixed now. This will be available in the next SearchPanes release which we hope will be in the next few weeks. Until then you can access the fix from the nightly builds.

Thanks,
Sandy