Hello All,
I have added readable grid into an interface and linked the record to this interface which will provide me all the fields of the record.
In the record user filter option available part of the a!gridfield. In the record I have enabled set showSearchBox to true which provides us with a global search option.
But I have a requirement to add filter for text field for example, Iike
CustomerName
The version I'm using is 21.2, any alternative way to achieve this?
Thanks & Regards
Girish
Discussion posts and replies are publicly visible
Hi ,
I'm sharing a workaround here, but please analyze whether it'll fit your use case.
Instead of an entity-backed record, we can create an expression-backed record, where we can customize the search filter to apply to the desired columns. A simple query entity can be the source of the expression.
docs.appian.com/.../Service-Backed_Record_Tutorial.html
If you're using a grid that uses record data, can you create a user filter where users can select a customer? https://docs.appian.com/suite/help/latest/filter-the-record-list.html
Hi Selvakumar,
Thankyou for the reply. One question i mind will expression-backed record not be slower when performing the search?
Hello Peter,
Using the user filter I will get a drop down list which is not required. I need the field as a free text to perform the search.
Sure but you can search in the dropdown to find the customers you need. Do you explicitly need to search by keyword instead of searching to find / select the customers?
If you do explicitly need to search by a key word, I'd suggest just adding a text box above your grid and save the results of the search into a local variable. Then, use that local variable as a filter in your record grid by applying a filter with a!recordData(). The one downside to this is that the user experience won't be as nice, but it should allow you to search what you want.
Yes I have already tried the method you have recommended, but need to confirm this approach with the customer. I do agree the downside with having a separate explicit search which would have an affect on the user experience. I was also going through "Expression Backed Record:, but in the newer version I see no documentation for this. I need to try this approach and check the performance.
There will not be much difference unless your entity-backed record was a synced record. Synced records perform faster than normal ones.
Thanks for the insight, let me try the work around.