Splunk Search

Dropdown Not Populating

CannonT
Engager

I'm trying to populate a dropdown box with this search which returns the values I would expect, but the dropdown is not populating. I have also tried using inputlookup to populate directly from the csv to no avail.

index=test_index sourcetype=recipients OR sourcetype=opened OR sourcetype=submitted  
    | lookup list.csv identity AS userID OUTPUT bunit as bunit company AS Location  
    | rename FN as "First Name" LN as "Last Name" 
    | lookup BusinessUnit.csv bunit AS bunit OUTPUT "Corporate Division" AS "cdiv" 
    | stats count by cdiv

This is my dropdown

<input type="dropdown" token="Corporate Division">
      <label>Coporate Division Selection</label>
      <selectFirstChoice>true</selectFirstChoice>
      <populatingSearch fieldForLabel="Coporate Division" fieldForValue="Coporate Division">
      <![CDATA[index=test_index sourcetype=recipients OR sourcetype=opened OR sourcetype=submitted | lookup list.csv identity AS userID OUTPUT bunit as bunit company AS Location | rename FN as "First Name" LN as "Last Name" | lookup BusinessUnit.csv bunit AS bunit OUTPUT "Corporate Division" AS "cdiv" | stats count by cdiv]]>
      </populatingSearch>
      <choice value="*" selected="true">All Division</choice>
      <default>*</default>
    </input>
0 Karma
1 Solution

somesoni2
Revered Legend

From your search query, the output fields are "count" and "cdiv" only (after stats) and you're trying to use the fields "Coporate Division" in the dropdown, which doesn't exists. Try using the field name "cdiv" in the dropdown properties (fieldForLabel and fieldForValue).

<input type="dropdown" token="Corporate Division">
      <label>Coporate Division Selection</label>
      <selectFirstChoice>true</selectFirstChoice>
      <populatingSearch fieldForLabel="cdiv" fieldForValue="cdiv">
      <![CDATA[index=test_index sourcetype=recipients OR sourcetype=opened OR sourcetype=submitted | lookup list.csv identity AS userID OUTPUT bunit as bunit company AS Location | rename FN as "First Name" LN as "Last Name" | lookup BusinessUnit.csv bunit AS bunit OUTPUT "Corporate Division" AS "cdiv" | stats count by cdiv]]>
      </populatingSearch>
      <choice value="*" selected="true">All Division</choice>
      <default>*</default>
    </input>

View solution in original post

somesoni2
Revered Legend

From your search query, the output fields are "count" and "cdiv" only (after stats) and you're trying to use the fields "Coporate Division" in the dropdown, which doesn't exists. Try using the field name "cdiv" in the dropdown properties (fieldForLabel and fieldForValue).

<input type="dropdown" token="Corporate Division">
      <label>Coporate Division Selection</label>
      <selectFirstChoice>true</selectFirstChoice>
      <populatingSearch fieldForLabel="cdiv" fieldForValue="cdiv">
      <![CDATA[index=test_index sourcetype=recipients OR sourcetype=opened OR sourcetype=submitted | lookup list.csv identity AS userID OUTPUT bunit as bunit company AS Location | rename FN as "First Name" LN as "Last Name" | lookup BusinessUnit.csv bunit AS bunit OUTPUT "Corporate Division" AS "cdiv" | stats count by cdiv]]>
      </populatingSearch>
      <choice value="*" selected="true">All Division</choice>
      <default>*</default>
    </input>
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

At .conf26, Don’t Just See What’s Next. Help Shape It at Innovation Labs.

Long before a new capability reaches the keynote stage, it begins as an idea waiting to be tested. At ...

Forwarder Topology Guidance: Intermediate HF vs Intermediate UF

Why Universal Forwarders Should Not Be Used as Intermediate Forwarders A practical Splunk forwarding topology ...

Data Management Digest – August 2026

Data Management Digest   Welcome to the August 2026 edition of Data Management Digest! August was a big month ...