Announcement

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

    After upgrading to SmartGWT 13.1, the ListGrid is not fetching data for some data sources

    Please find the data source:

    <DataSource ID="DailyOrderActivity" dataFormat="iscServer"

    title="Daily Order Activity" pluralTitle="Daily Order Activities"

    serverType="sql" dbName="as400" strictSQLFiltering="true"

    serverConstructor="ScDataSource">

    <field name="channelCode" nativeName="DCDDIV" tableName="DORDHDR"

    title="Channel" type="text" hidden="true"

    customSQL="true"/>



    <operationBindings>

    <operationBinding operationType="fetch" customCriteriaFields=" channelCode ">

    <tableClause>

    dordlin

    join dordhdr on dordlin.dconum=dordhdr.dconum

    </tableClause>

    <whereClause>

    $defaultWhereClause AND dordhdr.dcosts>'0'

    </whereClause>

    <groupClause>

    dcordt

    </groupClause>

    </operationBinding>

    </operationBindings>

    </DataSource>

    When the above field is used as customCriteriaFields (e.g., customCriteriaFields="channelCode") in the operation binding, the query generated includes the field with a prefix of the data source ID instead of the table name. This issue occurs only in version 13.1, whereas the same code works correctly in version 13.0.

    Sample query generated in 13.1

    SELECT * FROM dordlin join dordhdr on dordlin.dconum=dordhdr.dconum where (DailyOrderActivity.dcddiv=10)

    Sample query generated in 13.0

    SELECT * FROM dordlin join dordhdr on dordlin.dconum=dordhdr.dconum where (dordhdr.dcddiv=10)


    Note: when customSQL=” true” is removed it's working fine in 13.1.

    Could you please let me know your suggestions?


    #2
    Hi All,

    Could you please review my above comments and let me know your suggestion?

    Thanks

    Comment


      #3
      This issue has been assigned to an engineer, we will post back on this thread in the next few days

      Comment


        #4
        We have been unable to reproduce this issue locally. Can you confirm that you still see the issue with the most recent build of 13.1? If you do, we will need a small standalone test case that demonstrates the problem

        Comment

        Working...
        X