<?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: Breakdown The Adobe Reports&amp;Analytics way in Adobe Analytics Discussions</title>
    <link>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185838#M174</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think there are advantages of both. What I think could be useful is if you kept the draggable rail like it is now. And then, if you hover over an entry in the table, it gives you an icon where you could get the navigational like the breakdown link does in a normal report (kind of like how the filter icon shows up if you hover over the dimension).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 16 Oct 2015 02:29:42 GMT</pubDate>
    <dc:creator>mikethompson</dc:creator>
    <dc:date>2015-10-16T02:29:42Z</dc:date>
    <item>
      <title>Breakdown The Adobe Reports&amp;Analytics way</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185836#M172</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Breakdown endlessly is definitely a great function however the way of breakdown is not structured.&lt;/P&gt;&lt;P&gt;I personally prefer Adobe&amp;nbsp;Reports&amp;amp;Analytics breakdown. It gives a clear path of what I want to break with. Still &lt;STRONG&gt;search&lt;/STRONG&gt; bar is something missing in this breakdown function. However Freeform Analysis holds the search bar.&lt;/P&gt;&lt;P&gt;It would be great if we combine Freeform Analysis search and Report&amp;amp;Analytics breakdown.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:29:42 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185836#M172</guid>
      <dc:creator>kishore_tallada</dc:creator>
      <dc:date>2015-10-16T02:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Breakdown The Adobe Reports&amp;Analytics way</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185837#M173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great feedback, Kishore. I'll bring this up with our engineering team. Anyone else on here have any thoughts about the breakdown menu? Should it maintain the navigation structure, or should all dimension be treated in one bucket (like they are in the draggable left rail in Freeform Analysis)?&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:29:42 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185837#M173</guid>
      <dc:creator>BenjaminGaines</dc:creator>
      <dc:date>2015-10-16T02:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Breakdown The Adobe Reports&amp;Analytics way</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185838#M174</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think there are advantages of both. What I think could be useful is if you kept the draggable rail like it is now. And then, if you hover over an entry in the table, it gives you an icon where you could get the navigational like the breakdown link does in a normal report (kind of like how the filter icon shows up if you hover over the dimension).&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:29:42 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185838#M174</guid>
      <dc:creator>mikethompson</dc:creator>
      <dc:date>2015-10-16T02:29:42Z</dc:date>
    </item>
    <item>
      <title>Re: Breakdown The Adobe Reports&amp;Analytics way</title>
      <link>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185839#M175</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Interesting idea, Mike. I agree that there are probably advantages to both. I like your suggestion. It's a a&amp;nbsp;nice little&amp;nbsp;challenge for our UX team to solve!&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 16 Oct 2015 02:29:42 GMT</pubDate>
      <guid>https://experienceleaguecommunities.adobe.com/t5/adobe-analytics-discussions/breakdown-the-adobe-reports-analytics-way/m-p/185839#M175</guid>
      <dc:creator>BenjaminGaines</dc:creator>
      <dc:date>2015-10-16T02:29:42Z</dc:date>
    </item>
  </channel>
</rss>

