Hi mal81394, yes, you can by adding something like this: <drilldown> <condition field="foo"> </condition> <condition field="bar"> </condition> <condition field="baz"> <link> this_dashboard?form.Appname=$click.value2$ </link> </condition> </drilldown> This will disable drill down for cells named foo and bar , but enables drill down for a cell called baz . See the docs http://docs.splunk.com/Documentation/Splunk/latest/Viz/PanelreferenceforSimplifiedXML#condition_.28form_input.29 for more details on this topic. Hope this helps ... cheers, MuS ... View more

Hi JuGuSm, well using CLI is a broad statement, and therefore I can answer this question with Yes, of course you can use CLI to change it. Let me show you how to change the option search_assistant = none to search_assistant = full using CLI commands. first option, use sed sed -i 's/search_assistant = none/search_assistant = full/' /opt/splunk/etc/users/<username>/user-prefs/local/user-prefs.conf second option, use curl and edit it using the REST endpoint: curl -u admin:changeme -k https://localhost:8089//servicesNS/admin/user-prefs/properties/user-prefs/general/search_assistant -d value=full The result will be like this: <?xml version="1.0" encoding="UTF-8"?> <response> <messages> <msg type="INFO">Successfully modified 1 key(s)</msg> </messages> </response> Third option, use any CLI text editor and modify the file - yeah I know, lame but still a CLI option. So, as you can see there are ways to edit the setting using CLI commands 😉 Hope this helps ... cheers, MuS ... View more