Post a test case with OnModuleLoad and embedded classes.
Announcement
Collapse
No announcement yet.
X
-
I have exactly the same problem.
Filterbuilder seems to have a problem to filter on datasource fields that are read-only. (canEdit="false")
If you select a read-only field in the field combobox of the filterbuilder, it does not show the input field where you can fill in the filter criterium.
This is easily reproducable.
Comment
-
I am using SmartClient 7.0 and the following datasource :
Code:<DataSource ID="assureDMI" serverType="generic"> <fields> <field name="AAAACAPPLI" type="text" title="A_AAA_CAPPLI" length="10" canFilter="false" hidden="true"/> <field name="AAAABANINT" type="string" title="A_AAA_BANINT" length="7" canFilter="false"/> <field name="AAAABALMDE" type="text" title="A_AAA_BALMDE" length="8" canFilter="true"/> <field name="AAAABANSOC" type="text" title="A_AAA_BANSOC" length="3" canFilter="true"/> </fields> <serverObject lookupStyle="spring" bean="assureDao" /> </DataSource>
I would like the FilterBuilder to present only the last 2 columns which have the canFilter="true".
Have I made a mistake or is this a bug in SmartClient ?
Chris
Comment
-
This thread is now about two problems with FilterBuilder:
1) datasource fields with canFilter="false" are shown in the list of selectable search fields in the filterbuilder
2) datasource fields with canEdit="false" are not shown correctly in the filterbuilder. you would think 'canEdit' has nothing to do with filtering but apparently it has an influence on how the filterbuilder shows these fields.
(I don't know the inside of smarclient but maybe canEdit='false' makes the engine think it may not create an inputfield for this, but an inputfield is just what we need in the filterbuilder to fill in a value as search criterium.)
Comment
Comment