Join the Conversation
- Find Answers
- :
- Using Splunk
- :
- Dashboards & Visualizations
- :
- dynamic query for dropddown
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have a Query from 1 index that brings a list of some ID (about 300) they have dedup comand so that it brings me unique values. simple query like this
index= index1 |table partnerId|dedup partnerId
partnerID
aaaa
ssss
ffff
hkfk
I exported table to Excel and check that no value was duplicated.
But when i create a dropdown (so i can filter some results by this ID) to include it in a dashboard, and i put that Query it says: "Duplicate values causing conflict". what can it be causing this? As i said, i exported results in excel and no duplicated value was found (excel usually matches value wheter they are upper or lowercase).
Maybe the list of values is too long ? I don´t know what else to think.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Two things you might want to check:
Are you sure you're setting the correct "Field for Value" and "Field for Label"?
Also are you sure that you don't have any "Static Options" set that might be conflicting with the dynamically populating values?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Try reversing the order of the table and dedup command index=index1 | dedup partnerId | table partnerId
Might be that Splunk ignores the dedup once you've listed the results with table.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Two things you might want to check:
Are you sure you're setting the correct "Field for Value" and "Field for Label"?
Also are you sure that you don't have any "Static Options" set that might be conflicting with the dynamically populating values?
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That was it The field for label had a space when y pasted it...hehe thanks man
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
