# Separate item URL for Visual Builder Table visualization **URL:** \ **Category:** Kibana\ **Created:** [June 11, 2018, 6:08am UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292 "2018-06-11T06:08:30Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Nikhil\_Utane](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikhil_utane/32/27547_2.png) [@Nikhil\_Utane](https://discuss.elastic.co/u/Nikhil_Utane)\ **Post date:** [June 11, 2018, 6:08am UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292/1 "2018-06-11T06:08:30Z")
Hi, I am using Visual Builder - Table visualization to display the available values AND make them as a hyperlink so that a user can click on them and opening a new dashboard with the filter set to the selected value. ![image](https://us1.discourse-cdn.com/elastic/original/3X/5/1/51b5cbe526ed9e63ced15b7293592ee03a3a3a49.png). So far so good. Now for a different field I have a different requirement. In this case, each field has a 'separate' dashboard as against the above case where dashboard is same only a different filter needs to be applied. So how can I achieve this? I got to a point where I can specify if-else condition using Handlebar syntax, but that does not allow me to check against some value. Rather it can only checks whether a field exists or not. -Thanks Nikhil ---
**Author:** ![Nikhil\_Utane](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikhil_utane/32/27547_2.png) [@Nikhil\_Utane](https://discuss.elastic.co/u/Nikhil_Utane)\ **Post date:** [June 11, 2018, 10:18am UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292/2 "2018-06-11T10:18:09Z")
For now I am achieving this using HTTP URL redirection. But I would really like to have something within Kibana to solve this. Thanks. ---
**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\ **Post date:** [June 12, 2018, 3:11pm UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292/3 "2018-06-12T15:11:06Z")
Can you give an example of how the dashboard name is determined? Dashboards support a query parameter to load by its name instead of id `/dashboards?title=foo`. If not it sounds like we need another layer on top. One option is a scripted field, giving you more control. ---
**Author:** ![Nikhil\_Utane](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nikhil_utane/32/27547_2.png) [@Nikhil\_Utane](https://discuss.elastic.co/u/Nikhil_Utane)\ **Post date:** [June 13, 2018, 4:13am UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292/4 "2018-06-13T04:13:07Z")
Currently dashboards have IDs (which is what gets created by default). > #/dashboard/80e4c410-5f18-11e8-b778-c980f5dee594" > #/dashboard/170fe630-5f15-11e8-b778-c980f5dee594" One solution could be to use the same name as that of the field, so that when user clicks on it, I can use the {{key}} parameter to load the corresponding dashboard. But that would mean, exporting these dashboards, changing the ID to my string and import them back. Surely this is a hacky way and I was wondering if there is a 'well-designed' way. Better approach than this is the URL redirection IMO since I don't want to mess with the design philosophy of using IDs for dashboards instead of user-defined strings. Thanks. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 11, 2018, 4:27am UTC](https://discuss.elastic.co/t/separate-item-url-for-visual-builder-table-visualization/135292/5 "2018-07-11T04:27:21Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.