handling query entity errors

@erickp Would you please be able to give some background about the implementation(i.e., are you trying to export the report to Excel or are you trying to show the data in Paging Grid etc) as I opine that it really depends on what you are trying to do.

Would it make sense to make a Materialized View? This would greatly improve the query time.

We see this often as well, would be interested to hear about other practitioners experiences. In the past, I've restructured reports to fetch data in batches to get around slow views from other systems that we cannot control. I'm hoping one day we can get the old Query DB "Pause on Error = False" logic back in the Write to DS node and maybe even something similar for query functions. Error handling capability has been greatly reduced for us when switching from Query DB to Write to Datastore nodes.

@erickp Have you already looked into improving the performance on the view and/or query entity? Have you stripped out all data that is not immediately relevant to the end user and leveraged paging appropriately?

Can you explain how to retrieve query data in batches ?

@saicharanb, you can leverage a!pagingInfo() when making a query. Here is the link explaining more about a!pagingInfo(): forum.appian.com/.../System_Functions.html

@scottf281: We have a query as below
rule!WFT_getRequestDetailsBySearchParams(ri!process,ri!subprocess,ri!action,ri!requestor,ri!company,ri!reference,ri!sapRefNo,if(isnull(ri!fromDate),todatetime(date(2010,10,10)),ri!fromDate),if(isnull(ri!toDate),todatetime((today())),ri!toDate+intervalds(23,59,59)),ri!monetaryValue,ri!priority,ri!wftRequestID,ri!salesOffice,ri!requestStatus,ri!pageInfo)))

In the above query how is "ri!pageInfo" working? I could not find any parameters like batch size set for pageInfo. Please help how does it work for the above query.

@conorc, Can you please elaborate more on Materialized View?

We are facing Performance Issues for one of our views, Query entity is taking longer time to retrieve the data from the view.

Any help would be appreciated.
Thanks
Prakhar

@erickp: I am also facing the similar issue with the view. Please let me know if there is any concrete solution for the same.

We are using SQL Server

Thanks in Advance