Query Entity taking lot of time in fetching the data.

RE: Query Entity taking lot of time in fetching the data.

chandu — Thu, 08 Feb 2018 16:21:28 GMT

Hi Sahilb,
I suggest the approach given Shyamb. We are also using this type of approach and resulted in good feed back from the business.

RE: Query Entity taking lot of time in fetching the data.

Ravi Roshan — Thu, 08 Feb 2018 13:53:08 GMT

Hello Sahil,

You can do it by making the database call on the Grid's saveInto so whenever user will click on the next link it will call the query entity to
fetch the data and as you already saving the paginginfo, so it will automatically take the start index as per your requirement.

Case:
if your batchsize is 10 - > Your query entity rule will return only 10 records
click on next link - > startindex will become 11, and again your db call get execute and you will get another 10 set of results.

RE: Query Entity taking lot of time in fetching the data.

Shyam Bommakanti — Thu, 08 Feb 2018 13:00:43 GMT

Assuming you are trying to display this data on a grid, I suggest default to 25 batchsize. If needed, provide option to toggle between different batchsizes with a dropdown of radio button so that the end user can decide the batchsize but you can still control the max.

Refer to this recipe on how the next page works. Basically saving the paginginfo on gridField makes the grid paginate and batchsize can also be dynamically adjusted: docs.appian.com/.../recipe_display_data_with_cdt_fields_in_a_grid.html

RE: Query Entity taking lot of time in fetching the data.

sahilb346 — Thu, 08 Feb 2018 12:43:18 GMT

Colton Beck
Thanks for your reply. It is very helpful. But what you think then what batch size we should provide. There are 900 minimum rows for a particular user.

Can we give batch size 50 or 100 then when user clicks on the next button then again hit the query and fetch next 100.
Is this is good approach.

Thanks in Advance

RE: Query Entity taking lot of time in fetching the data.

Colton Beck — Thu, 01 Feb 2018 13:22:16 GMT

This is fairly complex logic to handle on the Appian-side. Could you try offboarding some of it to the database in the form of a view that you could query with less complex inputs?

If it's not possible to decrease complexity, it may be worthwhile to break this functionality into separate queries. This would not decrease the overall time, but would be less likely to result in a query timeout.

Also, you're querying with a -1 batch size, meaning this query will return every row that fits the filter criteria; if there are many rows, I suggest adding more optimal paging logic.