Is there any way to pass additional filters with search text from search UI to app search?
We have advance filter screen, there user can select the several filters and hit the submit button for search result.
---
Hi @ranjeet.tiwari. If you take a look at the Sandbox example, you can see how filters are applied via Facet components: [https://github.com/elastic/search-ui/blob/master/examples/sandbox/src/App.js](https://github.com/elastic/search-ui/blob/master/examples/sandbox/src/App.js).
The live demo can be found here: [https://codesandbox.io/s/national-parks-example-kdyms?fontsize=14](https://codesandbox.io/s/national-parks-example-kdyms?fontsize=14)
If you would like to apply a static filter to _every_ query, that is non-editable by a user, you could use [Advanced Configuration](https://github.com/elastic/search-ui/blob/master/ADVANCED.md#advanced-configuration). For example, we could apply a "world\_heritage\_site" filter to every query like follows:
```auto
{
searchQuery: {
filters: [
{
field: "world_heritage_site",
values: ["true"]
}
]
}
}
```
---
Hi @JasonStoltz, Once I select all filters and hit submit button from advance panel. result should be refreshed .. is there any way to refresh the result explicitly with updated config (added new filters in config) ?
---
Hey @ranjeet.tiwari. I'm confused about what you are trying to do.
Are you using facets and a "Facet" component?
If not, are you trying to build your own component that applies a filter without facets?
If so, I don't think you want to use config, you'll want to use "actions".
The general concept is documented here: [https://github.com/elastic/search-ui/blob/master/ADVANCED.md#working-with-the-headless-core](https://github.com/elastic/search-ui/blob/master/ADVANCED.md#working-with-the-headless-core).
A list of actions that you have available to you are listed here: [https://github.com/elastic/search-ui/blob/master/ADVANCED.md#actions](https://github.com/elastic/search-ui/blob/master/ADVANCED.md#actions).
It sounds like what you may want is the `addFilter` action. That will update the filters selected and trigger a new query.
---
I am not using facet and I have developed my own component called advance search where I have option to select multiple filters and there is submit button.
On the click of submit button, I want to show results...
On the click on submit button from filter panel, I am unable to generate/refresh the result
 .
I have attached the screenshot of filter panel.
---
Hey @ranjeet. I see. Then yes, on a user clicks that "Search" button, what you'll want to do is call the "addFilter" action to apply those filters. That will trigger a new query.
Make sense?
---
"addFilter" only accepts a single filter, to my knowledge, so you'll probably need to make a call to "addFilter" for each field. This currently will not work because of this issue: [https://github.com/elastic/search-ui/issues/65](https://github.com/elastic/search-ui/issues/65). I plan to patch this in the next day or two.
---
Thanks for the update ….
Through below code, I am able to update config
searchQuery: {
filters: [
{
field: "world\_heritage\_site",
values: ["true"]
}
]
Is there any explicit way to call refresh result/perform search with new config?
I just want to trigger the function from my button in filter panel that is being trigger on search button associated with SearchBox component of search ui.
How do I use addfilter function? I went through documentation but unable to find the way to addfilter..in which object I will get this method?
---
@ranjeet
# Using actions - You should probably do this
The way Search UI is designed to work, is by calling "actions" to apply filters or change the search term.
You can access "actions" in the following ways: [https://github.com/elastic/search-ui/blob/master/ADVANCED.md#working-with-the-headless-core](https://github.com/elastic/search-ui/blob/master/ADVANCED.md#working-with-the-headless-core).
For example:
```auto
({ isLoading })}>
{({ addFilter, setSearchTerm }) => (
{
setSearchTerm(e.target.value);
setFilter("quarter", 2);
setFilter("documentType", "PDF");
}}>Search
)}
```
This is how you _should_ be using Search UI to do what you are trying to do.
As stated before, calling actions quickly after one another as shown is _NOT_ working right now. I am planning to put in a fix today or tomorrow that would allow that example to work.
# An alternative to using actions - overriding onSearch
This could also work for you, but it is less ideal. It takes the approach that you are mentioning, applying query configuration dynamically. This [overrides the onSearch method](https://github.com/elastic/search-ui/blob/master/ADVANCED.md#overriding-connector-handlers)
```auto
onSearch: (state, queryConfig, next) => {
return next(
{
...state,
filters: [
{
field: "world_heritage_site",
values: ["true"]
},
{
field: "states",
values: ["California"]
}
]
},
queryConfig
);
},
```
When a user clicks on the "Search" button, you would then call the "setSearchTerm" action as seen above, which would trigger the "onSearch" method.
---
Follow this issue to track progress of the mentioned change: [https://github.com/elastic/search-ui/issues/65](https://github.com/elastic/search-ui/issues/65)
---
@JasonStoltz Please help me here [Is there any way to implement document level security in app search?](https://discuss.elastic.co/t/is-there-any-way-to-implement-document-level-security-in-app-search/201154)
---