Announcement

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

    DataSource not sending start/endrow in 13.1

    Hey just upgraded to 13.1 13.1-p20250110.

    Summary:
    We have a Timeline calendar that has problems problems loading data after we've upgraded.

    It seems that in 13.0, the request contains start row and end row, but not in 13.1.
    This results in the DSRequest included with the DMI call has a startrow of 0, and an endrow of -1.

    The DSRequests in the network debug looks basically the same except for that in 13.0 it has the
    <startRow xsi:type="xsd:long">0</startRow><endRow xsi:type="xsd:long">4000</endRow>
    and it's missing after we upgraded to 13.1

    The 4000 comes from setting
    Code:
    setDataPageSize(4000);
    on the TimeLine.


    Is this a known thing? Am i doing something wrong? Happy to provide more details if you need it.

    Would be great with some feedback asap, it's keeping us from upgrading.

    Cheers


    #2
    In 13.1, we added fetching based on visible date-ranges and, as part of that, changed the default value of Calendar.dataFetchMode to "basic", so that all events in the accessible range are client-side.

    We'll revisit whether this is necessary in Timelines but, in the meantime, setting dataFetchMode to "paged" on your Timeline should revert to the behavior you expect.

    Comment


      #3
      OK, thanks for quick response.

      Comment


        #4
        Hi, i'll reply in this thread because we have a similar issue if not a regression?

        we have updated from/to these versions:

        Code:
        <smartgwt.version>13.1-p20250323</smartgwt.version>
        <!--smartgwt.version>13.1-p20250522</smartgwt.version-->
        And now nothing happens when you press the left and right arrows in the timeline header to load a different time period.

        EDIT: to clarify, it does switch period in the timeline, but no new records are fetched from the server.
        Last edited by mathias; 5 Jul 2025, 07:02.

        Comment


          #5
          We'll need to see sample code, or a modified showcase sample that shows the issue - we don't see issues like this in regular cases.

          Comment


            #6
            ok. I just switched out the smartgwt jar files in our production build and it started fetching from the server again. Won't have to do research to find the exact circumstances where this happens if you can't replicate.

            Comment

            Working...
            X