<?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: Geolocation in Data Explorer - mixed results in Dashboarding</title>
    <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191102#M2430</link>
    <description>&lt;P&gt;true indeed, forgot about :names ;). good catch and I will update by time.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 21 Jul 2022 13:15:00 GMT</pubDate>
    <dc:creator>zietho</dc:creator>
    <dc:date>2022-07-21T13:15:00Z</dc:date>
    <item>
      <title>Geolocation in Data Explorer - how to avoid mixed results?</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/177468#M2065</link>
      <description>&lt;P&gt;When I base a graph or table in the Data Explorer on geolocation, the resulting data is on several different 'levels' - cities, countries, continents - all mixed up. Is there a way to prevent this, by filtering on one level for instance?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 30 May 2023 13:45:18 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/177468#M2065</guid>
      <dc:creator>marc_zantingh</dc:creator>
      <dc:date>2023-05-30T13:45:18Z</dc:date>
    </item>
    <item>
      <title>Re: Geolocation in Data Explorer - mixed results</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/183651#M2253</link>
      <description>&lt;P&gt;You can set a filter to filter it by continent, but not list it by continents. The Ascending/Descending isn't by location name either, its based off the values for each location.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This would be a great RFE to put in tho.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Mar 2022 15:47:57 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/183651#M2253</guid>
      <dc:creator>ChadTurner</dc:creator>
      <dc:date>2022-03-30T15:47:57Z</dc:date>
    </item>
    <item>
      <title>Re: Geolocation in Data Explorer - mixed results</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191030#M2421</link>
      <description>&lt;P&gt;Chad is right.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can, however, influence the sorting. To do so use the code mode like:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;before&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="zietho_2-1658352504380.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/6689iD38FC819A1330A97/image-size/medium?v=v2&amp;amp;px=400" role="button" title="zietho_2-1658352504380.png" alt="zietho_2-1658352504380.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;after (using dimension instead of value):&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="zietho_0-1658353535050.png" style="width: 400px;"&gt;&lt;img src="https://community.dynatrace.com/t5/image/serverpage/image-id/6690iD4B8255D6FFF8F7F/image-size/medium?v=v2&amp;amp;px=400" role="button" title="zietho_0-1658353535050.png" alt="zietho_0-1658353535050.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;regards&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thomas&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2022 21:45:55 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191030#M2421</guid>
      <dc:creator>zietho</dc:creator>
      <dc:date>2022-07-20T21:45:55Z</dc:date>
    </item>
    <item>
      <title>Re: Geolocation in Data Explorer - mixed results</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191063#M2426</link>
      <description>&lt;P&gt;&lt;a href="https://community.dynatrace.com/t5/user/viewprofilepage/user-id/23400"&gt;@zietho&lt;/a&gt;&amp;nbsp;I disagree on this. This will sort on the internal dimension value, not on the human readable value, so it's not applicable in general.&lt;BR /&gt;So it sorts on the values like APPLICATION-CB0200BF7867BEA0 instead of "Easytravel Angular". You need to engage the &lt;STRONG&gt;:names&lt;/STRONG&gt; transformation to get another dimension value - the human readable one.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 08:11:24 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191063#M2426</guid>
      <dc:creator>Julius_Loman</dc:creator>
      <dc:date>2022-07-21T08:11:24Z</dc:date>
    </item>
    <item>
      <title>Re: Geolocation in Data Explorer - mixed results</title>
      <link>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191102#M2430</link>
      <description>&lt;P&gt;true indeed, forgot about :names ;). good catch and I will update by time.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 13:15:00 GMT</pubDate>
      <guid>https://community.dynatrace.com/t5/Dashboarding/Geolocation-in-Data-Explorer-how-to-avoid-mixed-results/m-p/191102#M2430</guid>
      <dc:creator>zietho</dc:creator>
      <dc:date>2022-07-21T13:15:00Z</dc:date>
    </item>
  </channel>
</rss>

