DataSourceDateTimeField showing unwanted options in filter builder

[vnathank]

Hi Isomorphic,

Issue 1: “equals” option is displayed for the DataSourceDateTimeField filterbuilder, after smartgwt upgrade to 6.1
Please find the below code snippet
DataSourceTextField countryNameField = new DataSourceTextField("countryName", "Country");
countryNameField.setRequired(true);
countryNameField.setValidOperators(OperatorId.CONTAINS,
OperatorId.STARTS_WITH, OperatorId.ENDS_WITH,
OperatorId.EQUALS, OperatorId.NOT_EQUAL);


DateTimeItem dateItem = new DateTimeItem();
dateItem.setUseTextField(true);
TextItem textItem = new TextItem();

textItem.setReadOnlyDisplay(ReadOnlyDisplayAppearance.READONLY);
textItem.setCanEdit(false);
textItem.setTextAlign(Alignment.LEFT);

dateItem.setTextFieldProperties(textItem);
DataSourceDateTimeField independenceField = new DataSourceDateTimeField("independence", "Nationhood");
independenceField.setValidOperators(OperatorId.GREATER_OR_EQUAL,
OperatorId.LESS_OR_EQUAL, OperatorId.BETWEEN);
independenceField.setEditorProperties(dateItem);
setFields(countryNameField,independenceField);

Observe Extra_equals_Option.png “equals” Option is displayed along with the “From”,”To”,”between” Options

Issue 2: "Equals" is displayed by default in filter even when it is added at last.
ObserveEquals_DisplayingOnTop.png “Equals” Option is displayed by default.

Is there any reason for the above inconsistent behaviour?
Any suggestions to overcome this ?

Kindly refer the attached screen shot s& source code.


Smart GWT Version: 6.1
Google chrome version: Version 65.0.3325.162 (Official Build) (64-bit).

[Isomorphic]

Which build of 6.1 are you using? We always need that information - you can find it in the bottom-left/top-right of the docs, or you can evaluate isc.version in your browser.

There was, in the past, an issue like this - so, if you're not using the latest patched build, dated within the last few days, please retest with the latest from smartclient.com/builds. Let us know if you still see an issue.

[vnathank]

Hi Isomorphic,

We checked this issue using the patched 6.1 build, This issue was fixed. Thank you.