topic Dynamically populating dropdown and receving the error "duplicate labels causing conflict" in Dashboards & Visualizations

Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Wed, 07 Sep 2016 13:07:06 GMT

<input type="dropdown" token="c" searchWhenChanged="true">
      <label>Cube</label>
      <search>
        <query>BASE SEARCH  | stats count by DatabaseName</query>
        <earliest>@w0</earliest>
        <latest>now</latest>
      </search>
      <fieldForLabel>clabel</fieldForLabel>
      <fieldForValue>cvalue</fieldForValue>
      <choice value="*">All</choice>
      <default>*</default>
      <initialValue>*</initialValue>
    </input>

I have this code for dynamically populating my dropdown but I'm still getting the error

duplicate labels causing conflict

I checked 100 times on but using stats count by DatabaseName should be the correct way.

Any idea on why I'm getting this error?

Thanks

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

sundareshr — Wed, 07 Sep 2016 13:11:21 GMT

Try this

 <input type="dropdown" token="c" searchWhenChanged="true">
       <label>Cube</label>
       <search>
         <query>BASE SEARCH  | eval DatabaseName=upper(DatabaseName) | stats count by DatabaseName</query>
         <earliest>@w0</earliest>
         <latest>now</latest>
       </search>
       <fieldForLabel>DatabaseName</fieldForLabel>
       <fieldForValue>DatabaseName</fieldForValue>
       <choice value="*">All</choice>
       <default>*</default>
       <initialValue>*</initialValue>
     </input>

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Wed, 07 Sep 2016 13:17:18 GMT

Same error, as the query I first posted, if run a simple search everything works.
When i put the search in the dropdown I get that error. 😞

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

sundareshr — Wed, 07 Sep 2016 13:48:50 GMT

Try removing the static value (All). See if that makes a difference

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Wed, 07 Sep 2016 14:01:21 GMT

No difference

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

sundareshr — Wed, 07 Sep 2016 14:44:33 GMT

And you confirmed when you run this search outside of dropdown, you get unique list of DatabaseName? Can you share your BASE SEARCH

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Wed, 07 Sep 2016 15:17:50 GMT

My base search is like this: i cannot share more:

index=something sourcetype=somthing_else

Yes, I can confirm that the names are unique.

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

gcusello — Wed, 07 Sep 2016 15:58:45 GMT

Bye.
Giuseppe

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

s2_splunk — Wed, 07 Sep 2016 18:54:57 GMT

Hint: Better to use fields instead of table at the end of this search. table does a lot of work for UI formatting, which is not needed anywhere you don't want to render a table.

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Thu, 08 Sep 2016 10:25:42 GMT

Same error 😞

Re: Dynamically populating dropdown and receving the error "duplicate labels causing conflict"

andreafebbo — Thu, 08 Sep 2016 11:01:59 GMT

I discovered that the error depended by field for value and for label.
If I changefrom this:
clabel <fieldForValue>cvalue</fieldForValue>

to this:

<fieldForLabel>DatabaseName</fieldForLabel>
        <fieldForValue>DatabaseName</fieldForValue>

It works and I don't know why.

I thought that the 2 fields have to be that same, but if I chenge like this:

<fieldForLabel>DatabaseNameeeeeee</fieldForLabel>
        <fieldForValue>DatabaseName</fieldForValue>

it works, but like this:

<fieldForLabel>bla</fieldForLabel>
            <fieldForValue>bla</fieldForValue>

It does not work.
Can you tell me why?