Announcement

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

    Error when sorting formulaField

    Hi, I'm using SmartClient 8.2. When I create a Formula Field and then try to sort by the Formula Field, I get an error that says "component.getStandaloneFieldValue is not a function". Firebug suggests is it coming from the parseLocatorFallbackPath method.

    I wasn't able to re-create in your Feature Explorer. Any ideas why that might be happening before I try to debug it?

    #2
    We don't know why you're hitting this, but from your description we see where the error is very likely occurring.
    We've added a null-check which should avoid this error (just checked into our source control - will be present in the next nightly build).
    This is likely to resolve the issue, though we're shooting a little blind since we haven't seen exactly what your setup is that led to this error.
    If it persists or if there are other odd behaviors around your formula field, please let us know (along with as much detail as possible - if possible including a way to reproduce).

    Thanks
    Isomorphic Software

    Comment


      #3
      Thanks. Since it sounds like one simple null check is a potential solution, can you show me a patch that I can apply to our version of 8.2 to try it out as opposed to downloading a new version?

      Comment


        #4
        It is a null check but it's in the middle of a somewhat complex method (actually it occurs twice, so 2 methods).
        It'd be easier to verify with a fresh build than implement patched versions of these methods, so we'd recommend this unless there's some reason you actually can't test with the latest.

        Comment


          #5
          Ok, fair enough. Can you confirm you patched 8.2 and then I'll pull down the latest nightly and try it?

          Comment


            #6
            Sorry patch was the wrong term. Can you confirm you applied this fix to the latest 8.2 nightly?

            Comment


              #7
              We already checked this change into the 8.2p branch source (yesterday). It should be present in today's nightly build (Aug 1).

              Comment


                #8
                Looks like your null check did the trick. If you want any more details from me on this issue, let me know. Otherwise, we're good.

                Comment

                Working...
                X