I have been designing a table in PowerApps with a Canvas app. The table is not responsive currently and only fits about 10 rows by default.
The data in the table come from the DB. My engineers are suggesting to fetch list and have the user scroll through the 10 rows and have the BE fetch the next set of results. My UI design called for a pagination. They seem concerned about data retrieval that way and wanted to get people's opinion of this?
The reason I am going for the pagination route is that currently the table is "not" responsive and so with large data sets of 100+ records, when you scroll inside the table it is very clunky currently in our dev environment as it takes awhile to get the records and then you see white space until the table loads the new data set.
Solved! Go to Solution.
Hi @Anonymous ,
Do you want to display your table records using Pagination functionality?
Based on the needs that you mentioned, I think the Gallery could achieve your needs. The user @hpkeong has provided a detailed solution for this scenario, please check the solution within the following blog:
Please consider take a try with above solution, check if it could help in your scenario.
Best regards,
There are basically two approaches to paging: Pull large data sets and manage the paging with the locally cached data or use the query to do the paging on each request.
As a general rule, option 1 is better. The amount of data does not significantly cause performance issues, the heavy lift is generally the query not the amount of data over the wire. Assuming your dataset isn't over 2000 thousands of rows, option 1 is the way to go. If it is taking a few seconds, look for a point to load the data perhaps on app initialization.
Option 2 works well for extremely large data that needs to be sliced and/or HTTP API's. If you data is dynamic (i.e. could be anything from a big data set), you want to query specifically so the user doesn't need to page or scroll.
Summary, it depends. Basically map of the data-set and requirement and pick the best options. For instance, on a data-set of 4 million rows, I don't allow paging, if the user can't narrow it down, I doubt they are going to page around to find the data.
Hi @Anonymous ,
Do you want to display your table records using Pagination functionality?
Based on the needs that you mentioned, I think the Gallery could achieve your needs. The user @hpkeong has provided a detailed solution for this scenario, please check the solution within the following blog:
Please consider take a try with above solution, check if it could help in your scenario.
Best regards,
User | Count |
---|---|
260 | |
109 | |
92 | |
56 | |
41 |