I am using a record type to back some read-only grids via a!recordData. The grids both use the same record type, but with different queryFilters passed into a!recordData. Both instances need to show the OOTB search box, but I need to disable the "My Filters" view and the "Save Filters As..." feature to avoid users getting confused. Furthermore, the application of a saved filter as default will be applied to both instances of the gridField, which is something we must avoid.
Is there a way to disable My Filters / "Save Filters As" while retaining the OOTB search box? Else I would need to build a custom search.
Discussion posts and replies are publicly visible
AFAIK you cannot disable just the filter button.
To clarify, your reasoning for not wanting 'My filters' is because you want to have custom filters which affect both read only grids?
Danny Verb do you know whether the manage filter / refresh icons will be configurable in an upcoming release? We are deciding whether to build a custom search to hide the icons, or to just query the dse and use a datasubset to back the grid.
What you're describing almost seems like a bug. Are you saying that on an interface with two grids using the same record type, when you 'save filters' you are seeing a saved filter set on both grids?
That's correct. These grids are not intended to be a record list, but rather to display 2 different subsets of the record data. Of course we could use a query to back the grid, but want the performance benefits & OOTB search feature that comes with using a!recordData.We do not want to display manage filters.
Danny Verb Any conclusion on this? Is this a bug or is expected behavior. Does Engineering have a backlog item to allow "Save Filter As" to be disabled?
This is expected behavior because because saved filters are determined based on (1) the record type and (2) the combination of user filters / search used, and in this case both grids have the same values for both of those.
We don't have this on the immediate backlog, but I'll create a case to track this. One question: is it more important that they shouldn't be able to save their filters when the search is displayed, or is it more important that the same saved search shouldn't display on both grids?
Thanks, Peter. We're excited about the benefits of using record types over queries but just need a little more flexibility.
For my use case, it's more important that the same saved search isn't displayed in both grids.
© 2021 Appian. All rights reserved.