Just asking here to gauge whether or not I’m going to write up a ticket for this in the grid views… I can’t seem to determine why some columns filters work with the option “is null” and “is not null.” Seems to be mostly dates…
This has been going on since we started using Kinetic, so it’s not new - it just hasn’t been important enough for our efforts in finding a resolution…
So, on custom layers and non-custom layers, certain columns will return results when “is null” and “is not null” other columns will never do it. In particular, I see this on dates and number-type columns such as Unit Price, etc.
For instance, in Sales Order Status, ship by, doesn’t work when null sorting AND these type columns don’t have the “is empty” or not “is not empty” option available.
Any ideas or workarounds for this? Am I just missing something quick in Application Studio to make this work?
Here is the result of the ticket: It’s a known issue related to all of the filter problems that Kinetic has with grids and searching large amounts of records.
This was “fixed” in the upcoming 2025.2 docket to be released in the future this year. (I’m truly excited for these changes, if they come as promised and bug-free.)
The resolution is the same as with other filtered search issues: you have to select the download button on the grid to grab all of the records, then the “null” filter will work properly. I can confirm this workaround works, and can confirm it to be an ongoing PIA for us and, likely, for other users. But, maybe hope still lives with the idea of a fix on the horizon…
