Facing issue in expression while querying the data

RE: Facing issue in expression while querying the data

Harsh Kumar Agarwal — Wed, 24 Apr 2024 09:50:56 GMT

Use Appian record to create the grid and Appian will automatically solve the batch size issue for you.

Alternatively, if you are pulling data in a local variable first and use that to render the grid then make sure the query of local variable and paging grid shares the same paging info. This way you will only pull the rows needs to display in one page of grid and limits the batch size.

RE: Facing issue in expression while querying the data

ganesh_sasank18 — Wed, 24 Apr 2024 07:11:08 GMT

Can you try calling rule in data keyword in grid and pass fv!paginginfo to paginginfo rule input without using local variable

RE: Facing issue in expression while querying the data

Unnam Nageswara Rao — Wed, 24 Apr 2024 07:06:38 GMT

In grid I am passing local data

RE: Facing issue in expression while querying the data

Karumuru Abhishek — Wed, 24 Apr 2024 06:54:53 GMT

hi May I Know the requirement for querying the whole data. filter the columns you need from the data set and display, Calling whole data at once may lead to memory and timeout issues, Also may i know is it a table or view you are using to retrieve the data. Add indexes to the required columns and retrieve the columns you need.

RE: Facing issue in expression while querying the data

ganesh_sasank18 — Wed, 24 Apr 2024 06:41:00 GMT

Can you share the code where you are calling this rule in the grid

RE: Facing issue in expression while querying the data

Stefan Helzle — Wed, 24 Apr 2024 06:33:28 GMT

Sorry, but that will never work. That will result in a slow UI and a bad UX. Besides hitting the memory restrictions of Appian.

You will have to implement that in a way you only display a certain subset of the data.

RE: Facing issue in expression while querying the data

Konduru Chaitanya — Wed, 24 Apr 2024 06:33:07 GMT

I would say show few columns in the grid by minimizing the amount of data that you query and try to have a summary where you can display the whole data of that particular selection. That would be a better option. If you have too many columns your grid would look clumsy anyway. So I would consider few points from Rohit's suggestion.

RE: Facing issue in expression while querying the data

Unnam Nageswara Rao — Wed, 24 Apr 2024 06:27:54 GMT

I Need to show all the data into Grid in UI

RE: Facing issue in expression while querying the data

Stefan Helzle — Wed, 24 Apr 2024 06:25:18 GMT

For what purpose do you try to load the whole table into memory?

RE: Facing issue in expression while querying the data

Rohit Mehta — Wed, 24 Apr 2024 05:43:41 GMT

You are attempting to retrieve all data from a view in a single QE hit, which is not considered best practice and should generally be avoided. I am not fully aware of the specifics of your use case, but it is necessary to revise your approach, especially as the data in the view will continue to grow and you are using a batch size of -1.

Consider the following alternative approaches:

1. Retrieve only a specific number of rows.
2. Use aggregation to decrease the number of rows.
3. Limit the number of columns in the QE.
4. Execute a stored procedure (SP) and limit the data retrieved.
5. Alternatively, you can transfer the data from the view into a table and perform the QE on that table.

Please provide more details about your use case so that we can suggest a more tailored approach.

RE: Facing issue in expression while querying the data

venkatrea696188 — Wed, 24 Apr 2024 05:39:48 GMT

It seems you are pulling large data (More than 1 MB) ,there is a support case related to this error , go through it.

https://community.appian.com/support/w/kb/686/kb-1411-memory-threshold-reached-during-output-conversion