Dashboards & Visualizations

How to resolve this Multiselect Filter Issue?

jason_hotchkiss
Communicator

I have the following XML

 

     <input type="multiselect" token="exclude_user" searchWhenChanged="true">
        <label>Exclude User</label>
        <valuePrefix>"</valuePrefix>
        <valueSuffix>"</valueSuffix>
        <delimiter>, </delimiter>
        <fieldForLabel>user</fieldForLabel>
        <fieldForValue>user</fieldForValue>
        <search base="filtered">
          <query>| stats values(User) as user
| mvexpand user
| dedup user</query>
        </search>
        <choice value="SYSTEM">SYSTEM</choice>
        <choice value="-">NONE</choice>
        <default>SYSTEM</default>
        <initialValue>SYSTEM</initialValue>
      </input>

 


The filter is setup as an exclusion filter using a post processing search in conjunction with the base search, such as:

| search NOT User IN ($exclude_user$)

The multiselect works, until the value of "NONE" is selected which inputs the values of

| search NOT User IN (" ") into the post processing search.

Text below the filter displays, "Duplicate values causing conflict".  This doesn't prevent the search from completing, and the results I receive are what I expect to be returned.

It would be ideal for the message below the multiselect filter to not be displayed.  Anyone have a suggestion on how I can get rid of it?

I have tried the following:

Adding | dedup User to the post processing search.
Changing the fieldForLabel value to " " and NONE

Not sure what to try next.  Thanks in advanced.

Labels (3)
0 Karma
Get Updates on the Splunk Community!

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  &#x1f680; Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Stronger Security with Federated Search for S3, GCP SQL & Australian Threat ...

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...