We confirm that 13.0-p20230315 has fixed our problem.
Thanks for your efforts.
You can now archive this case.
Announcement
Collapse
No announcement yet.
User Profile
Collapse
-
13.0-p20230315 seems to be wroking.
We are investigating deeper and we will soon provide an update.
Leave a comment:
-
13.0-p20230312 seems to be working.
The operators list is now populated as expected.
However, the top level operators group is still...
Leave a comment:
-
Hello.
Overall our effort is driven by the need to explicitly reflect the server side semantics for each operator and field type so that...Last edited by eliasbalasis; 11 Mar 2023, 08:31.
Leave a comment:
-
As promised, you can find attached the transformed test case without server-side interactions.
This should make the source of the problem...
Leave a comment:
-
Under special conditions when a problem is not reproducible otherwise, a Maven-based test case is the last option, as it has happened for us in case 268066....
Leave a comment:
-
There is no database, all the fields are produced by FieldTypeOperatorsDataSource server side class.
The set of valid operators is defined...Last edited by eliasbalasis; 9 Mar 2023, 14:43.
Leave a comment:
-
You can use the attached files to reproduce the problem.
The top level operators group is wrong
The assigned operators are not...
Leave a comment:
-
FilterBuilder assignment of operators for each FieldType is not working properly / 13.0-p20230304
For "FieldDataSource" of "FilterBuilder",
we are calling com.smartgwt.client.data.DataSource#setTypeOperators(com.smartgwt.client.types.FieldType,...
No activity results to display
Show More
Leave a comment: