Announcement

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

    A blank field (with non default characterCasing) isn`t included in the DSRequest

    We have a text item with characterCasing = UPPER
    Code:
            setCharacterCasing(CharacterCasing.UPPER);
    When the field is set to blank, it no longer gets passed in the DSRequest on update.
    When we change the characterCasing to default everything works fine (the field is set to null in DSRequest)

    Using : SmartClient Version: SNAPSHOT_v10.1d_2015-09-09/Pro Deployment (built 2015-09-09)

    Thanks

    ps. This worked fine in SmartClient Version: v9.1p_2014-08-31/Pro Deployment (built 2014-08-31)

    #2
    Can you show us a simple test case to reproduce the problem? Probably easiest to to use one of the shipped dataSources (from the built-in ds sample, for example) and put together a simple EntryPoint class which just builds the minimal UI needed to reproduce the problem so we can run it on our end and see the problem.
    Thanks

    Isomorphic Software

    Comment


      #3
      Attached you can find a simple test case.
      You`ll see there are two text items in the form . One has casing set to upper and the other one is using the default value for characterCasing.

      To reproduce the problem change the text in the input fields from "test" to blank and click save.
      In the popup you`ll see new values from the DSRequest. You`ll notice that only defaultCaseItem and its value is included (upperCaseItem is missing).


      Please let us know if you need more info.


      Click image for larger version

Name:	screenshot.png
Views:	174
Size:	67.4 KB
ID:	231721
      Attached Files

      Comment


        #4
        Hello,

        Wondering if you were able to recreate the issue we are having using the test case we provided.

        Thank you.
        Stonebranch
        Last edited by sb; 5 Oct 2015, 11:09.

        Comment


          #5
          Yes, we've managed to reproduce the issue using the test case. Bear with us while we look into what could be causing this.
          Last edited by Isomorphic; 9 Oct 2015, 12:34.

          Comment


            #6
            Hi Isomorphic,
            Just following up on this one to see if any progress has been made to resolve the regression issue here.
            Thanks

            Comment


              #7
              Yes we have been working on this one. We believe we have a fix and will be checking it into our codebase shortly.
              Try the next nightly build and let us know if the problem persists.

              Thanks
              Isomorphic Software

              Comment


                #8
                Thank you for the update, we will verify in the next nightly build.

                Comment


                  #9
                  We tried the latest build SmartClient Version: SNAPSHOT_v10.1d_2015-10-13/Pro Deployment (built 2015-10-13) and the issue with upper case items is still there.

                  Comment


                    #10
                    Hello Isomorphic,
                    Any updates on this issue ?

                    Thanks

                    Comment


                      #11
                      Sorry for the silence. We have isolated the problem but the "right" fix is proving tricky.
                      We will follow up when we have a resolution for you.

                      Comment


                        #12
                        Hello Stonebranch,

                        Thank you for your patience, we've now resolved this issue and it will be available in the next nightly build.

                        Thanks,
                        Isomorphic Software

                        Comment


                          #13
                          Thank you, can you confirm if the build for the 20th includes the fix?
                          Regards

                          Comment


                            #14
                            It looks like the commit may have missed the cut off point for the Oct 20th build - so you'll want to test with the build dated Oct 21st

                            Regards
                            Isomorphic Software

                            Comment

                            Working...
                            X