How to prevent translation of labels and input fields in dashboards?

[DATEVeG]

Hello community,

we are using the german localization which is fine for the general ease of use of our users to navigate through Splunk. 
But the localization also leads to automatic translation of parts of the labels and input fields (e.g. multiselect input fields)  in user-created dashboards. The latter is particularly irritating, because the translation isn't always 100 percent fitting and most of the time you get an ugly mix of translated and english values.
Is there a way to prevent a dashboard  from getting auto-translated - without having to set the language specifier and localization specifier to english?

Regards,

Jens

[MMahlberg · Accepted solution]

Hi Jens,
I found a solution which does not require for a change of system language settings in case people view this dashboard with different language settings:

In your dropdown search configuration create a new field with

| eval field2 = original_field + " "

which simply adds a space at the end.

In the dropdown then use
Field For Label = field2
Field For Value = field

With the added empty space Splunk will not translate the field.

greetings & happy splunking,

Max

[NPfister]

Hi Max,

i implemented your  hints into our dashboard.

So the search macro now is

index=our_index sourcetype="our_sourcetype" earliest=-1w latest=now 
| dedup event_priority 
| sort event_priority
| eval sel_priority_blank = event_priority + " "
| table event_priority sel_priority_blank _time 
| rename event_priority as sel_priority _time as latest_record 
| convert timeformat="%+" ctime(latest_record)

And corresponding in the dashboard

      <fieldForLabel>sel_priority_blank</fieldForLabel>
      <fieldForValue>sel_priority</fieldForValue>

This works file so the problem is solved 😁

Regards, Norbert

[MMahlberg]

Hi Norbert,

glad I was able to help you even after over a year. Please select my answer as the solution 🙂

greetings,
Max

[NPfister]

*works fine*