I had this happening, too. In my case, I had a default value for the controlling token. Because the <condition /> section is under <change/>, I wouldn't have set the token under <condition/> because there had been no change. One way to force <change/> is to set no default, no initial value. Alternatively, if you must have an initial or default value, you can set a dummy search at the beginning of Simple XML, e.g., <search>
<query>
| makeresults
| eval tokenSearchOption1 = $tokenSearchOption1$
</query>
<progress>
<condition match="tokenSearchOption1=="Original"">
<set token="tokenSearchQuery">
blah
</set>
...
</condition>
</progress>
</search> Here is a test dashboard I set up when I was learning this: <form>
<label>Set token on load</label>
<fieldset submitButton="false">
<input type="dropdown" token="master_token" searchWhenChanged="true">
<label>master token</label>
<choice value="Data Entry">Data entry</choice>
<choice value="Click Only">Click only</choice>
<choice value="Attachment">Attachment</choice>
<default>Data Entry</default>
</input>
</fieldset>
<search>
<query>
| makeresults
| fields - _time
| eval master_token="$master_token$"
</query>
<progress>
<condition match="master_token=="Data Entry"">
<set token="data_entry">True</set>
<unset token="attachment"></unset>
<unset token="click_only"></unset>
</condition>
<condition match="master_token=="Click Only"">
<set token="click_only">True</set>
<unset token="data_entry"></unset>
<unset token="attachment"></unset>
</condition>
<condition match="master_token=="Attachment"">
<set token="attachment">True</set>
<unset token="click_only"></unset>
<unset token="data_entry"></unset>
</condition>
</progress>
</search>
<row>
<panel>
<html>
<div>master_token: $master_token$</div>
<div>data_entry: $data_entry$</div>
<div>click_only: $click_only$</div>
<div>attachment: $attachment$</div>
</html>
</panel>
</row>
</form>
... View more
