SIX years later and this is still the behavior. Why is this even allowed to persist? The DESIGN of your software practically means the only foolproof way to deploy ssl is to use the password "password" because splunk *just might not* feel like re-hashing anything.  Do YOU think it's worth your time to fix this for the love of the hundreds of millions of dollars you've earned? @splunk You owe me and my partner some hair.  ... View more

oooh can doo! Format a column first, and make a range map or value match then take note of that in the code, for instance the "Users in group" column:  "Users in Group": { "data": "> table | seriesByName(\"Users in Group\") | formatByType(Users_in_GroupColumnFormatEditorConfig)", "rowColors": "> table | seriesByName('Users in Group') | pick(Users_in_GroupRowColorsEditorConfig)", "rowBackgroundColors": "> table | seriesByName(\"Users in Group\") | rangeValue(Users_in_GroupRowBackgroundColorsEditorConfig)" }    Then find tableFormat and change rowBackgroundColors to the same as you used to color the column "headerVisibility": "fixed", "backgroundColor": "transparent", "tableFormat": {     "rowBackgroundColors": "> table | seriesByName('Users in Group') | rangeValue(Users_in_GroupRowBackgroundColorsEditorConfig)",     "headerBackgroundColor": "> backgroundColor | setColorChannel(tableHeaderBackgroundColorConfig)",     "rowColors": "> rowBackgroundColors | maxContrast(tableRowColorMaxContrast)",     "headerColor": "> headerBackgroundColor | maxContrast(tableRowColorMaxContrast)" }  And the whole row is now that color.      ... View more

How in the wide world of sports is this acceptable?  If I have a table, I and literally 100% of everyone on the planet expects EXPORT to actually EXPORT the data, and not give me a picture of the table.  This is the most useless feature I've ever seen. 0/10 would not use again.   ... View more