Pagination

RE: Pagination

GautamShenoy — Tue, 13 Dec 2022 15:42:20 GMT

Thank you worked

RE: Pagination

Stefan Helzle — Tue, 13 Dec 2022 15:32:40 GMT

The grid uses the totalcount value from the datasubset to manage paging. You need to enable this.

There is so much going wrong here ....

Remove your manual startIndex calculation. The grid uses the paginginfo to tell the query how much data to fetch. Pass this into the expression and use it accordingly.

This is a full example of a working paging grid fetching only 5 rows at a time.

a!gridField(
  label: "Read-only Grid",
  labelPosition: "ABOVE",
  data: a!queryEntity(
    entity: cons!ADM_ENTITY_APPLICATIONS,
    fetchTotalCount: true,
    query: a!query(
      pagingInfo: fv!pagingInfo
    )
  ),
  pageSize: 5,
  columns: {
    a!gridColumn(
      label: "Name",
      sortField: "name",
      value: fv!row.name
    )
  },
)

RE: Pagination

GautamShenoy — Tue, 13 Dec 2022 15:27:01 GMT

It is a training.

The task given was, I need to fetch data from the database in batch format. i.e. 10 rows at a time. Now initially I did the page size thing and it worked fine.

But then 1 complexity added was to pass only 10 records at a time to the grid and not the entire data from the table. So the page size will not do my job here

Onto the didn't work part, I tried passing 10 records, but then It did not show me the '>' key to move to next batch of records. I tried adjusting the records such that I get the '>' key, but then problem was, the '<' key was disabled. Now I can get the next 10 records, but I can't access the previous 10 records

RE: Pagination

Mike Schmitt — Tue, 13 Dec 2022 15:11:58 GMT

FWIW while you're using an external query and an external PagingInfo that you've pre-defined, you never need the read-only grid's internal "page size" parameter. That's only needed when you're having it handle the query internally.

RE: Pagination

Stefan Helzle — Tue, 13 Dec 2022 15:04:23 GMT

Is this a test or a training?

I do not understand your question about the datasubset. The gridfield will manage paging based on the additional values in the datasubset. When you only pass the data part of it, this will not work.

I missed one important thing? In the initial post you write "it didn't work". What exactly did not work?

RE: Pagination

GautamShenoy — Tue, 13 Dec 2022 14:59:28 GMT

The requirement was given I guess so that we find alternatives of page size,a

Now about the datasubset, I might sound amateur, but wouldn't it put us in the same problem of putting load on the query ? Like I wanted only 10 records at a time

RE: Pagination

Stefan Helzle — Tue, 13 Dec 2022 14:50:53 GMT

You have a requirement to not use pageSize !?!?! What kind of requirement is that???

I think the problem is that you only pass the list of items to the grid. To make paging work, it needs a full datasubset. Did you try this?