<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: How to prevent translation of labels and input fields in dashboards? in Dashboards &amp; Visualizations</title>
    <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/587984#M48235</link>
    <description>&lt;P&gt;Hi Jens,&lt;BR /&gt;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:&lt;/P&gt;&lt;P&gt;In your dropdown search configuration create a new field with&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval field2 = original_field + " "&lt;/LI-CODE&gt;&lt;P&gt;which simply adds a space at the end.&lt;/P&gt;&lt;P&gt;In the dropdown then use&lt;BR /&gt;Field For Label = field2&lt;BR /&gt;Field For Value = field&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the added empty space Splunk will not translate the field.&lt;/P&gt;&lt;P&gt;greetings &amp;amp; happy splunking,&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;</description>
    <pubDate>Tue, 08 Mar 2022 10:05:33 GMT</pubDate>
    <dc:creator>MMahlberg</dc:creator>
    <dc:date>2022-03-08T10:05:33Z</dc:date>
    <item>
      <title>How to prevent translation of labels and input fields in dashboards?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/537380#M36733</link>
      <description>&lt;P&gt;Hello community,&lt;BR /&gt;&lt;BR /&gt;we are using the german localization which is fine for the general ease of use of our users to navigate through Splunk.&amp;nbsp;&lt;BR /&gt;But the localization also leads to automatic translation of parts of the labels and input fields (e.g. multiselect input fields)&amp;nbsp; 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.&lt;BR /&gt;Is there a way to prevent a dashboard&amp;nbsp; from getting auto-translated - without having to set the language specifier and localization specifier to english?&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;/P&gt;&lt;P&gt;Jens&lt;/P&gt;</description>
      <pubDate>Wed, 27 Jan 2021 09:59:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/537380#M36733</guid>
      <dc:creator>DATEVeG</dc:creator>
      <dc:date>2021-01-27T09:59:35Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent translation of labels and input fields in dashboards?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/587984#M48235</link>
      <description>&lt;P&gt;Hi Jens,&lt;BR /&gt;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:&lt;/P&gt;&lt;P&gt;In your dropdown search configuration create a new field with&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| eval field2 = original_field + " "&lt;/LI-CODE&gt;&lt;P&gt;which simply adds a space at the end.&lt;/P&gt;&lt;P&gt;In the dropdown then use&lt;BR /&gt;Field For Label = field2&lt;BR /&gt;Field For Value = field&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With the added empty space Splunk will not translate the field.&lt;/P&gt;&lt;P&gt;greetings &amp;amp; happy splunking,&lt;/P&gt;&lt;P&gt;Max&lt;/P&gt;</description>
      <pubDate>Tue, 08 Mar 2022 10:05:33 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/587984#M48235</guid>
      <dc:creator>MMahlberg</dc:creator>
      <dc:date>2022-03-08T10:05:33Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent translation of labels and input fields in dashboards?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588231#M48245</link>
      <description>&lt;P&gt;Hi Max,&lt;/P&gt;&lt;P&gt;i implemented your&amp;nbsp; hints into our dashboard.&lt;/P&gt;&lt;P&gt;So the search macro now is&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;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)&lt;/LI-CODE&gt;&lt;P&gt;And corresponding in the dashboard&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;      &amp;lt;fieldForLabel&amp;gt;sel_priority_blank&amp;lt;/fieldForLabel&amp;gt;
      &amp;lt;fieldForValue&amp;gt;sel_priority&amp;lt;/fieldForValue&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;This works file so the problem is solved&amp;nbsp;&lt;span class="lia-unicode-emoji" title=":beaming_face_with_smiling_eyes:"&gt;😁&lt;/span&gt;&lt;/P&gt;&lt;P&gt;Regards, Norbert&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2022 13:19:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588231#M48245</guid>
      <dc:creator>NPfister</dc:creator>
      <dc:date>2022-03-09T13:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent translation of labels and input fields in dashboards?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588232#M48246</link>
      <description>&lt;P&gt;*works fine*&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2022 13:20:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588232#M48246</guid>
      <dc:creator>NPfister</dc:creator>
      <dc:date>2022-03-09T13:20:02Z</dc:date>
    </item>
    <item>
      <title>Re: How to prevent translation of labels and input fields in dashboards?</title>
      <link>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588247#M48247</link>
      <description>&lt;P&gt;Hi Norbert,&lt;/P&gt;&lt;P&gt;glad I was able to help you even after over a year. Please select my answer as the solution &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;greetings,&lt;BR /&gt;Max&lt;/P&gt;</description>
      <pubDate>Wed, 09 Mar 2022 15:14:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Dashboards-Visualizations/How-to-prevent-translation-of-labels-and-input-fields-in/m-p/588247#M48247</guid>
      <dc:creator>MMahlberg</dc:creator>
      <dc:date>2022-03-09T15:14:48Z</dc:date>
    </item>
  </channel>
</rss>

