Question on using a!query with grids

RE: Question on using a!query with grids

marky — Tue, 29 Mar 2016 20:35:04 GMT

Creating the dictionary will have to be done in the load (or else the paging won't work correctly). I think the better approach is to build and optimize a view with the additional calculated column, that way the data can be retrieved in a with as well. There are some ways to handle sorting paging for a calculated column where the data must be in a with, but those options are more advanced and can be messy.

RE: Question on using a!query with grids

vishnuv — Tue, 29 Mar 2016 06:31:57 GMT

Below link will help you as well
forum.appian.com/.../SAIL_Recipes.html

RE: Question on using a!query with grids

monikar — Tue, 29 Mar 2016 05:48:17 GMT

I second the solution given by Benjamin.
Hi hussams214,

You can always create a dictionary of final data you want to display.

And you can also try the following approach:

1. Create a Dummy CDT for the display purpose which will not have any entity associated with it. Basic structure columns can be textColumn1, textColumn2, textColumn3 and so on.
2. Create a rule to construct the cdt data with given inputs. Sample code of the rule can be like:

load(
apply(
type!displayCDT(
textColumn1: _,
textColumn2: _,
textColumn3: _
),
merge(
{
ri!textColumn1
},
{
ri!textColumn2
},
{
ri!textColumn3
}
)
)
)

3. And you can construct the display data where textColumn1, textColumn2 can be actual queried column from DB and textColumn3 values can be the calculated data.

4. Once the data is in hand you can construct the data subset and display on grid.

RE: Question on using a!query with grids

benjamins — Tue, 29 Mar 2016 03:33:45 GMT

Easiest way to fix this issue is to create a dictionary based on the data you are using to create your data subset. Include the calculated field in this dictionary. Once you have done this, then create the data subset for your grid.