@AshimaE, you would need to add little bit of more details with your use case. What are the values for two dropdown? What kind of query is being formed? Does one dropdown provide query and other visualization? Or is it a combination of both?
In either case you need to code dropdown's change Event Handler to pass on query string and token to show/hide a panel. You might have to unset other tokens to hide unwanted panels. Also you can use these tokens within queries to ensure that hidden panels do not run query in background. However, details will depend on your use case and you need to provide more details as requested for the same.
Following run anywhere example gives a demo of coding change event handler for Drop downs and set/unset tokens. $value$ and $label$ are default Drop down tokens. It further exemplifies the use of depends to hide a panel when the token/s is not set (PS: reverse behavior can be achieved via rejects)
<fieldset submitButton="false">
<input type="dropdown" token="field1" searchWhenChanged="true">
<label>field1</label>
<choice value="value1">Value 1</choice>
<choice value="value2">Value 2</choice>
<choice value="value3">Value 3</choice>
<change>
<condition value="value1">
<set token="query1">| makeresults | eval $label$="$value$"</set>
<set token="showHTML1">true</set>
<unset token="showHTML2"></unset>
</condition>
<condition value="value2">
<set token="query1">| makeresults | eval $label$="$value$"</set>
<set token="showHTML1">true</set>
<unset token="showHTML2"></unset>
</condition>
<condition value="value3">
<set token="query1">| makeresults | eval $label$="$value$"</set>
<set token="showHTML1">true</set>
<unset token="showHTML2"></unset>
</condition>
</change>
</input>
<input type="dropdown" token="field2" searchWhenChanged="true">
<label>field2</label>
<choice value="value1">Value 1</choice>
<choice value="value2">Value 2</choice>
<choice value="value3">Value 3</choice>
<change>
<condition value="value1">
<set token="query2">| makeresults | eval $label$="$value$"</set>
<set token="showHTML2">true</set>
<unset token="showHTML1"></unset>
</condition>
<condition value="value2">
<set token="query2">| makeresults | eval $label$="$value$"</set>
<set token="showHTML2">true</set>
<unset token="showHTML1"></unset>
</condition>
<condition value="value3">
<set token="query2">| makeresults | eval $label$="$value$"</set>
<set token="showHTML2">true</set>
<unset token="showHTML1"></unset>
</condition>
</change>
</input>
</fieldset>
<row>
<panel>
<html depends="$showHTML1$">
<style>
.mytitle{
font-size:150%;
color:red;
}
.myinfo{
font-size:120%;
color:blue;
}
</style>
<div class="mytitle">
HTML Panel 1
</div>
<div>
<p class="myinfo">$query1$</p>
</div>
</html>
<html depends="$showHTML2$">
<div class="mytitle">
HTML Panel 2
</div>
<div>
<p class="myinfo">$query2$</p>
</div>
</html>
</panel>
</row>
You can get the Splunk 6.x Dashboard Examples App from Splunkbase to get examples of these and many more. For us to assist please provide more details of your use case.
____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
