Announcement

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

    #16
    Sorry for the confusion....I had switched back to testing with our actual code as opposed to the runnable code sample that I had been sending. I have attached the DataSource that was used when the error was received...as you can see...I had switched to using $advancedCriteria (as opposed to $criteria) in the SQL template. Also, as you can see in the Request, all the referenced fields were sent (see post 14 for the request, Response, error log).

    Any other thoughts on what could be producing the error? I don't see the actual SQL that is produced in the Log so I assume it's erroring before that.

    Attached Files

    Comment


      #17
      We've made the mentioned change to address this issue. Please try the next nightly build, dated January 19.

      Regards
      Isomorphic Software

      Comment


        #18
        To clarify that last post - we've modified things so that you can now set defaultTextMatchStyle to "exactCase" and you should get the type of query you want.

        We think we see what's causing the stack trace as well. It's an Oracle-specific problem that comes up when you are using a Date value in the where clause and there is no DataSourceField for the date. Should be easy to fix, and we'll let you know when that's corrected.

        Comment


          #19
          The problem that is causing the stack trace has been fixed. Please test your code again using the next nightly build, dated January 19.

          Regards
          Isomorphic Software

          Comment


            #20
            I have updated to the January 19th nightly build and set the CubeGrid's AutoFetchTextMatchStyle to 'ExactCase'. I am happy to report that both issues are now fixed and functioning as expected.

            Thank you for your support and assistance.

            Comment

            Working...
            X