# URL templating for Drilldowns using required field from the dashboard filters **URL:** \ **Category:** Kibana\ **Tags:** dashboard\ **Created:** [December 16, 2024, 12:21pm UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019 "2024-12-16T12:21:28Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [December 16, 2024, 12:21pm UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/1 "2024-12-16T12:21:28Z")
Hi Team, We are trying to create a drilldown using URL templating to link two dashboards. But while moving from one dashboard to other we need to carry one particular field(recon\_key) which is added in the filters to be carried as a filter to the other dashboard but not all the filters which are added. Could you please suggest us how to select a particular field from the filters to be carried ignoring other filters. Note: The users might select the filters randomly so that we cannot use filters offset to carry the recon\_key from the filter. For example: From the below URL there are 3 filters added 1. Primary\_sourceSystemId:OMS\_SAPMENA 2. Secondary\_sourceSystemId:SHP\_ASEAN 3. recon\_key: 24121619XXXXX(Sample value but the url should take the value what ever it has) Out of these filters we need to take only recon\_key to go to the other dashbord. Please suggest. [https://xxxxxxxxxxxxxxxxxxxxxxxxxx/app/dashboards#/view/cf954448-5885-4424-b24a-0d43656c3e3c?\_g=(time:(from:'now-7d/d',to:'now'),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:Primary\_sourceSystemId,negate:!f,params:(query:OMS\_SAPMENA),type:phrase](https://xxxxxxxxxxxxxxxxxxxxxxxxxx/app/dashboards#/view/cf954448-5885-4424-b24a-0d43656c3e3c?_g=(time:(from:'now-7d/d',to:'now'),filters:!(('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:Primary_sourceSystemId,negate:!f,params:(query:OMS_SAPMENA),type:phrase)),query:(match\_phrase:(Primary\_sourceSystemId:OMS\_SAPMENA))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:Secondary\_sourceSystemId,negate:!f,params:(query:SHP\_ASEAN),type:phrase),query:(match\_phrase:(Secondary\_sourceSystemId:SHP\_ASEAN))),('$state':(store:appState),meta:(alias:!n,disabled:!f,index:d1b4ec03-6510-4e47-b418-cd24774f19a7,key:recon\_key,negate:!f,params:(query: **VN/P2/24121619XXXXX** ),type:phrase),query:(match\_phrase:(recon\_key: **24121619XXXXX** ))))) ---
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [December 17, 2024, 4:03am UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/2 "2024-12-17T04:03:12Z")
Can someone please help me with this request. ---
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [December 30, 2024, 10:28am UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/3 "2024-12-30T10:28:32Z")
Can someone please help me with this request. ---
**Author:** ![Hannah\_Mudge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hannah_mudge/32/107993_2.png) [@Hannah\_Mudge](https://discuss.elastic.co/u/Hannah_Mudge)\ **Post date:** [December 30, 2024, 4:12pm UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/4 "2024-12-30T16:12:20Z")
@venkatkumar229 Unfortunately, your specific request is not currently possible. Drilldowns are designed to either take **all** filters or **no** filters, and we don't have an option to configure a specific subset. As a workaround, you could **pin** your `recon_key` filter (i.e. make it a global filter) and then it would follow you across all of Kibana? If that workaround doesn't work for you, please feel free to make a [feature request](https://github.com/elastic/kibana/issues/new?template=Feature_request.md) so that we can better prioritize this 🙂 ---
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [January 2, 2025, 4:06am UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/5 "2025-01-02T04:06:42Z")
Thank you @Hannah_Mudge , if i try to pin recon\_key after selecting a particular value from the dashboard. All the other filters which i have selected will be flowing to the other dashboards and if i remove filters nothing will be flowing to other dashboard even if i pin them. I will try to raise a feature request as suggested. ---
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [January 2, 2025, 5:43am UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/6 "2025-01-02T05:43:52Z")
Hi @Hannah_Mudge , I have raised a feature request for this use case in Git. > > > Description: > Currently, when using "context.panel.filters" in Kibana's URL temp…lating for drilldowns, all filters applied in the source dashboard are passed to the destination dashboard. However, there are cases where only a specific filter, rather than all the filters, needs to be passed to the destination. > > Use Case: > We have two dashboards with drilldowns that link one to another. In the source dashboard, multiple filters might be applied (e.g., source1, source2, key). However, the destination dashboard only has one relevant field (key) available. When using drilldown with panel filters, if the source dashboard has multiple filters (such as source1, source2, and key), the destination dashboard may encounter errors because some of these filters (e.g., source1, source2) are not present in the destination index. > > Feature Request: > We need the ability to select a specific filter (and its value) to pass through to the destination dashboard during drilldowns, regardless of the order or number of filters applied in the source dashboard. This will ensure that only the relevant filters, such as key, are transferred to the destination dashboard, avoiding errors when certain fields are not available in the destination index. > > Public Elastic Case: > \[URL Templating for Drilldowns Using Required Field from Dashboard Filters\](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019) ---
**Author:** ![venkatkumar229](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/venkatkumar229/32/104663_2.png) [@venkatkumar229](https://discuss.elastic.co/u/venkatkumar229)\ **Post date:** [February 18, 2025, 7:14am UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/7 "2025-02-18T07:14:50Z")
Hi @Hannah_Mudge , We have upgraded our elasticsearch to 8.17.2 from 8.15.4 recently. We could see that now we are not able to create drilldowns on saved searches. Could you please let us know whether the feature is removed now. ---
**Author:** ![Davis\_McPhee](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davis_mcphee/32/112461_2.png) [@Davis\_McPhee](https://discuss.elastic.co/u/Davis_McPhee)\ **Post date:** [February 19, 2025, 11:37pm UTC](https://discuss.elastic.co/t/url-templating-for-drilldowns-using-required-field-from-the-dashboard-filters/372019/8 "2025-02-19T23:37:23Z")
Hi @venkatkumar229, sorry for the inconvenience this caused. Drilldown support was not intentionally removed from saved search panels, but a bug introduced in 8.16 has caused them to stop working. We're working on a fix now and are aiming to have it included in the next 8.17 patch release. The issue to track is here: [[Discover] [Embeddable] Discover session embeddable is missing drilldown support · Issue #211677 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/211677).