<?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: Arranging data in a tabular format in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Arranging-data-in-a-tabular-format/m-p/1760512#M718799</link>
    <description>&lt;P&gt;item2: how did you envision the branch added in your table if not a separate field?&amp;nbsp; would that be under the account type column (column A)?&lt;/P&gt;&lt;P&gt;item3: what does is requirement mean - that the measures will be under 12 columns (Jan - Dec)?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why are there a lot of restrictions on the design/datamodel?&amp;nbsp; these aspects are transparent to the user and must be molded in a form that is easy to maintain, optimized for large data sets, and drives ease of building on the UI side.&lt;/P&gt;&lt;P&gt;Normally, Account, Branch, subaccount(your column A),and Date will be your dimensions (individual fields) and the numbers will be the measures.&amp;nbsp; a pivot table would be the simplest chart to use.&lt;/P&gt;&lt;P&gt;if you are unable (actually unwilling) to crosstab your data, then you can have 12 separate measures representing the months.&amp;nbsp; you will have to have the other dimensions though.&amp;nbsp; then you just sum each month as one expression and you will have a straight table with 12 expressions.&amp;nbsp; + 13th expression which is sum across months&lt;BR /&gt;&lt;BR /&gt;Obviously, these will be in text boxes:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="edwin_0-1605061382423.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/43938iBBF00B4700C4BED3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="edwin_0-1605061382423.png" alt="edwin_0-1605061382423.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Nov 2020 02:23:14 GMT</pubDate>
    <dc:creator>edwin</dc:creator>
    <dc:date>2020-11-11T02:23:14Z</dc:date>
    <item>
      <title>Arranging data in a tabular format</title>
      <link>https://community.qlik.com/t5/QlikView/Arranging-data-in-a-tabular-format/m-p/1760395#M718798</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;As per the attachment, there are two sheets (FR &amp;amp; HH). This is the data for a Branch AS &amp;amp; this Branch field is not there in the table. I need following to be achieved with no any changes being done on to this table.&lt;/P&gt;&lt;P&gt;1: Need to arrange the same data as looks in the Excel tables&lt;/P&gt;&lt;P&gt;2: Without adding Branch code in a separate field, is there a way of showing it?&lt;/P&gt;&lt;P&gt;3: Without using cross table structure, is it possible to be arranged in a pivot table?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Neville&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2020 18:58:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Arranging-data-in-a-tabular-format/m-p/1760395#M718798</guid>
      <dc:creator>nevilledhamsiri</dc:creator>
      <dc:date>2020-11-20T18:58:42Z</dc:date>
    </item>
    <item>
      <title>Re: Arranging data in a tabular format</title>
      <link>https://community.qlik.com/t5/QlikView/Arranging-data-in-a-tabular-format/m-p/1760512#M718799</link>
      <description>&lt;P&gt;item2: how did you envision the branch added in your table if not a separate field?&amp;nbsp; would that be under the account type column (column A)?&lt;/P&gt;&lt;P&gt;item3: what does is requirement mean - that the measures will be under 12 columns (Jan - Dec)?&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;why are there a lot of restrictions on the design/datamodel?&amp;nbsp; these aspects are transparent to the user and must be molded in a form that is easy to maintain, optimized for large data sets, and drives ease of building on the UI side.&lt;/P&gt;&lt;P&gt;Normally, Account, Branch, subaccount(your column A),and Date will be your dimensions (individual fields) and the numbers will be the measures.&amp;nbsp; a pivot table would be the simplest chart to use.&lt;/P&gt;&lt;P&gt;if you are unable (actually unwilling) to crosstab your data, then you can have 12 separate measures representing the months.&amp;nbsp; you will have to have the other dimensions though.&amp;nbsp; then you just sum each month as one expression and you will have a straight table with 12 expressions.&amp;nbsp; + 13th expression which is sum across months&lt;BR /&gt;&lt;BR /&gt;Obviously, these will be in text boxes:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="edwin_0-1605061382423.png" style="width: 400px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/43938iBBF00B4700C4BED3/image-size/medium?v=v2&amp;amp;px=400" role="button" title="edwin_0-1605061382423.png" alt="edwin_0-1605061382423.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2020 02:23:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Arranging-data-in-a-tabular-format/m-p/1760512#M718799</guid>
      <dc:creator>edwin</dc:creator>
      <dc:date>2020-11-11T02:23:14Z</dc:date>
    </item>
  </channel>
</rss>

