• Replies 6 replies
  • Subscribers 13 subscribers
  • Views 10105 views
  • Users 0 members are here
Related Discussions
Home » Discussions » Best Practices

Paginginfo

pauls0003
A Score Level 1

Is there any more info available on how Paginginfo works within Appian ?

I've an upcoming use case where we will have a source of truth table which over time will become quite large. We will be doing all the user tricks to keep it responsive but at some point we will be querying it and no matter how many filters etc we get returned the data subset will be for a large amount of records. (let pretend 10,000).

i'll use pagingInfo to control the grid, but whilst I'm displaying records 1 to 100, what is happening to the rest of the data set ? I'm assuming it's floating around in Appian memory somewhere. 

I'm interested in people's thoughts here ?

  Discussion posts and replies are publicly visible

Parents
  • Hi Paul,
    I have similar use case as you mentioned. If we define start index and batch size correctly as guys already responded, Appian will fetch only that much of data. E.g. if start index is 1 and batch size is 100, Appian will holds memory of datasubset with 100 records. Along with this, it will have some metadata information e.g. totalCount but nothing much. With properly defined paging, it doesn't matter how many records are in database. its just your batch size will define how much Appian memory will be utilized. Also we need to make sure to use CDT with precise number of fields which are required for that screen. Extra unused fields will increases payloads and memory unnecessarily.
    Thanks.
Reply
  • Hi Paul,
    I have similar use case as you mentioned. If we define start index and batch size correctly as guys already responded, Appian will fetch only that much of data. E.g. if start index is 1 and batch size is 100, Appian will holds memory of datasubset with 100 records. Along with this, it will have some metadata information e.g. totalCount but nothing much. With properly defined paging, it doesn't matter how many records are in database. its just your batch size will define how much Appian memory will be utilized. Also we need to make sure to use CDT with precise number of fields which are required for that screen. Extra unused fields will increases payloads and memory unnecessarily.
    Thanks.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.