Filters in Readonly grid

hi goddativ5526  Appian does not support placing dropdowns inside the grid header row or just below it,

Hi goddativ5526 ,

as Abhishek Karumuru  mentioned, Appian doesn’t natively support dropdowns directly under grid headers (like Excel-style filters), but you can create a very similar experience using filters above the grid.

We have a alternative way to implement very closely as shown below.



Use a cascading dropdown and add filters into the Read only grid. This will add custom filters.

Hope this helps you!!!

Hi Varun Teja Gurrapu Thank you for your reply.

The problem here is there are 50 fields so I want the position of that filter exactly above that column and if we scroll grid horizentally it should scroll dropdowns also.

The client is specifically asking for this requirement. While this is possible in an editable grid, I want search functionality just like in a read-only grid. Can we have a custom search bar?

Hi goddativ5526 
Yes, you can create that in editable grid and use custom search using text box component and button. But as you mentioned, you are having 50 fields and if search need to be applied for all the 50 fields, there can be performance issues as the custom search need to search for all the 50 fields and give you the results . If search is restricted to some fields then you can proceed with custom search but there might be performance issues in this scenario also.

Hi  Teja Kunchala ,If you dont mind can you give sample code for custom serach ,Iam new to appian

My advice is, to not try to implement an Excel in Appian. While the Appian capabilities can be stretched to some extend, more sooner than later you will bump into a problem.

And then, Appian has a separate component GridPlus which might help you with this.

 GridPlus Component Plug-In 

goddativ5526 
a!localVariables(
local!search,
{
a!sectionLayout(
label: "",
contents: {
a!sideBySideLayout(
items: {
a!sideBySideItem(
item: a!textField(
label: "",
labelPosition: "COLLAPSED",
value: local!search,
saveInto: local!search,
refreshAfter: "UNFOCUS",
validations: {}
)
),
a!sideBySideItem(
item: a!buttonArrayLayout(
buttons: {
a!buttonWidget(
label: "SEARCh",
style: "OUTLINE"
)
},
align: "START",
marginBelow: "NONE"
)
)
}
)
}
)
}
)

When clicked on search, refresh the query that is getting the data to in grid and the query need to contain query filters for the fields to search.
Just for your reference but its not recommended to use. For 50 fields, you have to use a!queryfilter and pass the local!search and return the data which is not good as per performance.

goddativ5526 
a!localVariables(
local!search,
{
a!sectionLayout(
label: "",
contents: {
a!sideBySideLayout(
items: {
a!sideBySideItem(
item: a!textField(
label: "",
labelPosition: "COLLAPSED",
value: local!search,
saveInto: local!search,
refreshAfter: "UNFOCUS",
validations: {}
)
),
a!sideBySideItem(
item: a!buttonArrayLayout(
buttons: {
a!buttonWidget(
label: "SEARCh",
style: "OUTLINE"
)
},
align: "START",
marginBelow: "NONE"
)
)
}
)
}
)
}
)

When clicked on search, refresh the query that is getting the data to in grid and the query need to contain query filters for the fields to search.
Just for your reference but its not recommended to use. For 50 fields, you have to use a!queryfilter and pass the local!search and return the data which is not good as per performance.