[Blama]

Hi mgoertz,

sorry, no further input from my side besides the usual:

• Are the shown ListGrid settings really all settings applied (also with respect to subclassing and setDefaultProperties()?
• Is the application freshly built (clean, build, deploy))
• Is the client side cache emptied?

Best regards,
Blama

[mgoertz]

Hi Blama, thanks again. No other settings have been applied to the ListGrids. I can run with a very simple case of just instantiating a grid and fetching data, and it won't work. I've done a clean build and I've emptied my caches and these actions also don't help. Any filtering that requires a trip to the server to fetch data creates AdvancedCriteria, regardless of the field being filtered.

Isomorphic, can you weigh in at all here??? If I need to, I'll just build a filter from scratch, but it kind of seems a shame to have to do so.

[Isomorphic]

We're looking into it and will update here when we have more information

[Isomorphic]

The issue here is that one of your fields is of type "time" - this results in a filterEditor item of type "TimeItem", which assumes a default of allowing expressions (FormItem.allowExpressions).

This should not be the case in a filterEditor and we've fixed it in the framework - you could then fix your issue by setting ListGrid.allowFilterExpressions(false).

Alternatively, you can switch allowExpressions off for a specific field via its filterEditorProperties, or for TimeItem's globally like this:

TimeItem ti = new TimeItem();
ti.setAllowExpressions(false);
TimeItem.setDefaultProperties(ti);

[mgoertz]

Wonderful, that seems to have fixed it! Thanks for all your help!