I have some non-time-based data that I'd like to summarize using chart with a small number of bins.  For example,   <some search> | stats count as c by foo | sort -c | chart sum(c) by foo bins=10   "foo" is not numeric, so it automatically fails, but I don't want the bins to be determined by an intrinsic order on foo anyway: The bins should respect the order that comes from the sort command. Thus, in the chart, the first "bar" should represent the greatest decile of the "sort -c" command, the second, the second decile, and so on. I can't figure out how to wrangle an order into the chart command or otherwise make it respect the sort and use that order as the basis for the separations into bins. Am I barking up the wrong tree here? ... View more

I have a dropdown in a dashboard that uses a lookup table with columns X and Y.  The values in X are unique; the values in Y are not.  I am using X in "Field for Label" and Y in "Field for Value". The problem is that when I do not dedup Y, I get an error below the dropdown that says, Duplicate values causing conflict. The search string I'm using is this: | inputlookup LT | fields X, Y When I change it to this: | inputlookup LT | fields X, Y | dedup Y sortby X ...the error disappears. What I would like is to retain all the values of X instead of removing some with the dedup operation.  Is this possible? ... View more