<?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 Drilldown / aggregation by multiple date fields in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Drilldown-aggregation-by-multiple-date-fields/m-p/342901#M702756</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I havent needed to do a model like this before so am unsure of a good way to approach it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Worked example QVW - MultidatesTest.qvw - below with generic data. I have a autogenerated script calendar table, with 2 data tables both of which contain a date field, primary key is the OrderNo.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="19504" class="jive-image-thumbnail jive-image" onclick="" alt="2QlikView x64 - [X50 DEVMultidatesTest.png" src="/legacyfs/online/19504_2QlikView x64 - [X50 DEVMultidatesTest.png" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was hoping to create a single calendar and then provide aggregation by month so when I click on say Jun it shows me all date fields that fall into that dimension.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case it works that way with the calendar table, but clearly because there is no common key the orderdate and deliverydate fields remain unaffected by such filtering.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also realise that in many instances OrderDate and DeliveryDate don't fall into the same MonthName, so then I suppose one needs to choose one or the other field to aggregate on and ignore the other.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="19503" class="jive-image" alt="1X50 DEVMultidatesTest.png" src="/legacyfs/online/19503_1X50 DEVMultidatesTest.png" /&gt;&lt;/P&gt;&lt;P&gt;I realise I can rename one of the non calendar date fields to the same as the CalendarDate and then that will work, but then I lose the identity of that field, Of course I could load that field twice and have say&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;DeliveryDate,&lt;/P&gt;&lt;P&gt;DeliveryDate as CalendarDate&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then I would link Order table to Calendar Table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I did this with Delivery table as well then I'd get synthetic keys I'd expect. Is this an issue or not? Having done this I'm still not sure which field I should actually use for a weekly, monthly, quarterly aggregation pivot table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought of joining tables, and/or creating a separate additional table with just the date fields from the different tables but the avenues I've tried are getting me into knots.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sure my example is a common type of scenario. Maybe I'm searching with inadequate keywords but I havent yet found anything to point me the the right direction in the community forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are good ways to tackle such a sort of drilldown / aggregation effectively?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 07 Aug 2012 15:28:00 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-08-07T15:28:00Z</dc:date>
    <item>
      <title>Drilldown / aggregation by multiple date fields</title>
      <link>https://community.qlik.com/t5/QlikView/Drilldown-aggregation-by-multiple-date-fields/m-p/342901#M702756</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I havent needed to do a model like this before so am unsure of a good way to approach it. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Worked example QVW - MultidatesTest.qvw - below with generic data. I have a autogenerated script calendar table, with 2 data tables both of which contain a date field, primary key is the OrderNo.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="19504" class="jive-image-thumbnail jive-image" onclick="" alt="2QlikView x64 - [X50 DEVMultidatesTest.png" src="/legacyfs/online/19504_2QlikView x64 - [X50 DEVMultidatesTest.png" width="450" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was hoping to create a single calendar and then provide aggregation by month so when I click on say Jun it shows me all date fields that fall into that dimension.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case it works that way with the calendar table, but clearly because there is no common key the orderdate and deliverydate fields remain unaffected by such filtering.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also realise that in many instances OrderDate and DeliveryDate don't fall into the same MonthName, so then I suppose one needs to choose one or the other field to aggregate on and ignore the other.&lt;/P&gt;&lt;P&gt;&lt;IMG __jive_id="19503" class="jive-image" alt="1X50 DEVMultidatesTest.png" src="/legacyfs/online/19503_1X50 DEVMultidatesTest.png" /&gt;&lt;/P&gt;&lt;P&gt;I realise I can rename one of the non calendar date fields to the same as the CalendarDate and then that will work, but then I lose the identity of that field, Of course I could load that field twice and have say&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;DeliveryDate,&lt;/P&gt;&lt;P&gt;DeliveryDate as CalendarDate&lt;/P&gt;&lt;P&gt;...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and then I would link Order table to Calendar Table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I did this with Delivery table as well then I'd get synthetic keys I'd expect. Is this an issue or not? Having done this I'm still not sure which field I should actually use for a weekly, monthly, quarterly aggregation pivot table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought of joining tables, and/or creating a separate additional table with just the date fields from the different tables but the avenues I've tried are getting me into knots.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sure my example is a common type of scenario. Maybe I'm searching with inadequate keywords but I havent yet found anything to point me the the right direction in the community forums.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What are good ways to tackle such a sort of drilldown / aggregation effectively?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2012 15:28:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Drilldown-aggregation-by-multiple-date-fields/m-p/342901#M702756</guid>
      <dc:creator />
      <dc:date>2012-08-07T15:28:00Z</dc:date>
    </item>
    <item>
      <title>Re: Drilldown / aggregation by multiple date fields</title>
      <link>https://community.qlik.com/t5/QlikView/Drilldown-aggregation-by-multiple-date-fields/m-p/342902#M702757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hmmm, of course as usually happens I find something potentially promising *after* posting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm going to try this - method 2 and see how I go.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="loading" href="https://community.qlik.com/message/30971#30971" title="http://community.qlik.com/message/30971#30971"&gt;http://community.qlik.com/message/30971#30971&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 07 Aug 2012 16:18:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Drilldown-aggregation-by-multiple-date-fields/m-p/342902#M702757</guid>
      <dc:creator />
      <dc:date>2012-08-07T16:18:00Z</dc:date>
    </item>
  </channel>
</rss>

