Announcement

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

    DataBound

    SmartGWT Version: v8.2p_2012-08-06/LGPL Development Only (built 2012-08-06)

    If I have a SelectItem in a databound DynamicForm with the DataSourceField that the SelectItem is bound to set to FieldType.INTEGER, setEmptyDisplayValue does not show anything in the empty SelectItem.

    When switching the DataSourceField type to TEXT it starts working again.

    Please advise, thanks!
    Brian

    #2
    Look at your data in the RPC tab of the Developer Console. To be considered "empty" you should be delivering null and not, for example, 0.

    Comment


      #3
      First of all, I apologize for the title of this post. I'm amazed it wasn't deleted/ignored. Not sure what happened there...

      I'll look into it and report back, thanks for the suggestion.

      Comment


        #4
        Hi Isomorphic,

        The form is set up to create new records, not edit existing ones. I have tried adding editNewRecord() to the end of my form initialization, and have also tried setting the default values of the SelectItems to null (by creating a null Integer object and using setDefaultValue).

        Nothing has worked. It seems that this only occurs if the DataSourceField is setMultiple:true. This doesn't occur when it is setMultiple:false as far as I can tell.

        Comment


          #5
          Can you put together minimal code to reproduce the problem? Then we can take a look.

          Comment


            #6
            Here's a minimal test case. I was wrong about the INTEGER fields working with setMultiple:false. As you can see, INTEGER fields will not show the setEmptyDisplayValue regardless of setMultiple.

            Thanks,
            Brian
            Attached Files

            Comment


              #7
              This has been fixed in the SC 8.3d and 8.2p branches. It should be in the nightly ZIPs shortly.

              Comment


                #8
                Great, thanks!

                Comment


                  #9
                  Confirmed that this bug has been fixed. Thanks for the quick response!

                  Brian

                  Comment

                  Working...
                  X