Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    Post a test case with OnModuleLoad and embedded classes.

    Comment


      #17
      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


        #18
        Isomorphic,
        are you able to reproduce this?
        Do you consider it as a bug?

        Thank in advance for your reaction

        Comment


          #19
          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 have a filterBuilder that shows all of the columns that are not hidden="true".
          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


            #20
            A quick test shows the FilterBuilder correctly ignoring hidden fields.

            Comment


              #21
              Hi,

              Actually, the problem is with the "canFilter" attribute which seems to be ignored :
              Even if set to "false" in the datasource, the field is shown in the AdvancedFilter listbox.


              Regards,

              --
              Mat'
              Last edited by mraber; 10 Sep 2009, 00:13.

              Comment


                #22
                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


                  #23
                  These issues are now fixed internally, along with a related one whereby canSave="false" was showing the same (incorrect) behavior as canEdit="false". The change should be available in SVN soon.

                  Comment


                    #24
                    Thanks Isomorphic, you are the best.

                    Comment


                      #25
                      Thanks for the quick fix !

                      --
                      Mat'

                      Comment


                        #26
                        Fix is in SVN.

                        Comment


                          #27
                          I have tested the last nightly build (rev. 742), it works.
                          Thank you.

                          --
                          Mat'

                          Comment


                            #28
                            I downloaded the new SmartGWT 1.3 and I still have these problems.

                            Is smartgwt.jar the only file that is affected by this fix or do I need to update other files in my SmartGWT EE 1.2.1+SmartGWT 1.3 environment?

                            Thanks a lot,

                            David

                            Comment


                              #29
                              A new release of SmartGWT EE is slated for early next week that will incorporate this fix. We'll post an update when its available.

                              Comment


                                #30
                                Any news on the release of a new version of SmartGWT EE?

                                Is it still scheduled in the near future?

                                Comment

                                Working...
                                X