Splunk Search

Dashboard Classic Dropdown text length limit

dmoberg
Path Finder

I have a drop-down in my Classic Dashboard that is populating from an inputlookup.

Looks like this:

<input type="dropdown" token="_ApiID" searchWhenChanged="false">
<label>API ID</label>
<fieldForLabel>APIIDLBL</fieldForLabel>
<fieldForValue>APIID</fieldForValue>
<search>
<query>| inputlookup XXXXXXXXXX | dedup APIID,APIIDLBL | stats count by APIID,APIIDLBL | sort APIID,APIIDLBL | fields APIIDLBL,APIID</query>
<earliest>$timerange.earliest$</earliest>
<latest>$timerange.latest$</latest>
</search>
<choice value="*">All API IDs</choice>
<choice value="NotMeantToBeFound">Select API</choice>
<change>
<set token="OperationID">*</set>
<set token="form.OperationID">*</set>
<set token="ProductID">*</set>
<set token="form.ProductID">*</set>
<set token="sourceregionselector">*</set>
<set token="form.sourceregionselector">*</set>
</change>
<initialValue>NotMeantToBeFound</initialValue>
<default>NotMeantToBeFound</default>
</input>

For the above I get an error message below the drop-down stating: "Duplicate values causing conflict", however there are no Duplicates in the list.

This made me think that Splunk is only looking at the first Y number of chars of the value to determine if there are any duplicates. To test this I extracted the first 20 chars of each value and removed duplicates, as per this:

<query>| inputlookup XXXXXXXXXX | dedup APIID,APIIDLBL | stats count by APIID,APIIDLBL | sort APIID,APIIDLBL | fields APIIDLBL,APIID | eval APIIDLBL=substr(APIIDLBL,1,20) | dedup APIIDLBL</query>

This did indeed resolve my issue and no longer see an error message, but this is obviously not a fix since I then can't see the full values.

Any ideas on how to solve it? I would take this is a bug........

Labels (1)
Tags (1)
0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust

Hi @dmoberg ,

in your search, you are deduping by APIID and APIIDLBL, but you must declare only one field in fieldForLabel, so probably you have duplicated values for this field (APIIDLBL ).

Ciao.

Giuseppe

View solution in original post

ITWhisperer
SplunkTrust
SplunkTrust

Deduping by two fields does not guaranteed uniqueness in either field, you should just dedup by APIID, as this is the field being used for the value, which is the one which needs to have unique values in.

0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @dmoberg ,

in your search, you are deduping by APIID and APIIDLBL, but you must declare only one field in fieldForLabel, so probably you have duplicated values for this field (APIIDLBL ).

Ciao.

Giuseppe

dmoberg
Path Finder

Awesome. It works now!

0 Karma
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...