Dashboards & Visualizations

What's causing the error "Duplicate values causing conflict" on my multi search input box?

patricianaguit
Explorer

I'm getting an error on my multi search input box. It says "Duplicate values causing conflict"
Below is my code

<form>
  <label>token trial</label>
  <fieldset submitButton="false">
    <input type="dropdown" token="view_token">
      <label>Views</label>
      <fieldForLabel>Views</fieldForLabel>
      <fieldForValue>Views</fieldForValue>
      <search>
        <query>index="ape_idx" sourcetype="ape_csv"  | lookup geo_region "Dominant Geographic Unit" as "Geographic Unit" outputnew "Geographic Region"   | dedup "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" | table "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" | transpose 0  | rename column AS Views | table Views</query>
        <earliest>0</earliest>
        <latest></latest>
      </search>
    </input>
    <input type="multiselect" token="test_tok">
      <label>Selection</label>
      <prefix>(</prefix>
      <suffix>)</suffix>
      <valuePrefix>Selection="</valuePrefix>
      <valueSuffix>"</valueSuffix>
      <delimiter> OR </delimiter>
      <fieldForLabel>"$view_token$"</fieldForLabel>
      <fieldForValue>"$view_token$"</fieldForValue>
      <search>
        <query>index="ape_idx" sourcetype="ape_csv" 
| lookup geo_region "Dominant Geographic Unit" as "Geographic Unit" outputnew "Geographic Region" 
| dedup "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" 
| sort "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" 
| table "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" 
| transpose 
| rename column AS Views 
| table Views 
| where Views="$view_token$"
| append 
    [| search index="ape_idx" sourcetype="ape_csv" 
    | lookup geo_region "Dominant Geographic Unit" as "Geographic Unit" outputnew "Geographic Region" 
    | dedup"Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" 
    | sort "Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style" 
    | table "$view_token$"]</query>
        <earliest>0</earliest>
        <latest></latest>
      </search>
    </input>
  </fieldset>
</form>
Tags (3)
0 Karma

Shan
Builder

I agree with the command of @kmaron and @ Woodcock. Here i want to make another point . Rather than using dedup as mentioned below. Try to narrow down the result which exactly required. Remove the unnecessary fields. So that can even minimize the duplication of records ..

| dedup"Geographic Region" "GDN Account Group", "Operating Group" "Service Group" "Interaction Style"

0 Karma

kmaron
Motivator

I'd start by running the query you're using to build your multi-select information and see if there are duplicates. If there are then you'll need to dedup them.

0 Karma

patricianaguit
Explorer

Thanks for the help!

0 Karma

niketn
Legend

@patricianaguit, I have converted @kmaron's comment to answer. If your issue is resolved please accept to mark this question as answered. Do up vote the comments that helped 🙂

____________________________________________
| makeresults | eval message= "Happy Splunking!!!"
0 Karma

woodcock
Esteemed Legend

I agree with @kmaron; you have duplicate values which is not allowed. Run the search manually and figure out why and fix your populating search.

0 Karma

patricianaguit
Explorer

Thanks for the help!

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...