<?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 Two date ranges as dimensions in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148216#M26540</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With methods 1 and 2, you would indeed have "quarter ordered" and "quarter billed". But that is, after all, "necessary" if you want to be able to select different values for each.&lt;/P&gt;&lt;P&gt;Method 3 won't allow your users (at least without even more complexity) to select orders that were ordered in quarter 1 and billed in quarter 2, for instance. But if that's not a problem, then I'm a big fan of just having a "Quarter" field, a single chart that lets you easily switch between types of dates, and so on. I've done it in several applications, and like the results.&lt;/P&gt;&lt;P&gt;But for most applications, I suspect it is better to just create more than one calendar and have a bunch of different date names.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 02 Jul 2009 06:06:51 GMT</pubDate>
    <dc:creator>johnw</dc:creator>
    <dc:date>2009-07-02T06:06:51Z</dc:date>
    <item>
      <title>Two date ranges as dimensions</title>
      <link>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148213#M26537</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 have the folowing tables:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* Orders (OrderID, Date1, Date2)&lt;/P&gt;&lt;P&gt;* OrderItems(OrderID,ItemID,Item_Price)&lt;/P&gt;&lt;P&gt;* DateTable(Date1,year,month,quarter,etc...)&lt;/P&gt;&lt;P&gt;I have a chart with the quarter as the dimension an I present the sum of the items.&lt;/P&gt;&lt;P&gt;I want also to present on another bar that shows the same info but to use Date2 instead of Date1.&lt;/P&gt;&lt;P&gt;The reason is - Date1 shows the original date order. Date 2 shows the date of the billing.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is it even possible? or do i have to build another table and show on another chart?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tnx 4 your help&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 01 Jul 2009 23:51:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148213#M26537</guid>
      <dc:creator>xtrimf</dc:creator>
      <dc:date>2009-07-01T23:51:13Z</dc:date>
    </item>
    <item>
      <title>Two date ranges as dimensions</title>
      <link>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148214#M26538</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, it's possible, in a number of ways... Before anything else, we have to understand and agree that we have 2 different Date fields, and therefore the attributes (Year, Month, etc...) have to be different. Once we understand that, we can continue...&lt;/P&gt;&lt;P&gt;A few ways to resolve this problem:&lt;/P&gt;&lt;P&gt;1. Create a separate Calendar table for the Billing Dates and have a separate set of attributes - Billing Year, Billing Month, etc...&lt;/P&gt;&lt;P&gt;2. Or, you can simply join both Calendar tables into the data table and keep those attributes in the same table (you still need separate attributes for Order Date and Billing Date).&lt;/P&gt;&lt;P&gt;3. Finally, you can build the solution with a single Calendar, but it would be the most complex... You'd need to "normalize" your Orders table and have a separate tables for dates - one row for each date. Some thing like this:&lt;/P&gt;&lt;P&gt;Orders (OrderID, ... other Order Attributes)&lt;/P&gt;&lt;P&gt;OrderDates(OrderID, Date, DateTypeFlag), where DateTypeFlag differentiates between Order Date vs. Billing Date.&lt;/P&gt;&lt;P&gt;Then, in all your expressions and dimensions you'd have to use DateTypeFlag in order to specify what date needs to be used.&lt;/P&gt;&lt;P&gt;Even though the later solution only requires a single Calendar, it's the most complex and time consuming. I'd recommend one of the first two options, unless you have any other requirements that definitely call for a single Calendar...&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;Oleg&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jul 2009 01:19:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148214#M26538</guid>
      <dc:creator>Oleg_Troyansky</dc:creator>
      <dc:date>2009-07-02T01:19:34Z</dc:date>
    </item>
    <item>
      <title>Two date ranges as dimensions</title>
      <link>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148215#M26539</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Oleg,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I still don't see how I can manage to have "quarter" as the dimention and two different expressions that reffer to different date fields.&lt;/P&gt;&lt;P&gt;I don't want to have on my dimention "quarter" &amp;amp; " quarter2"....&lt;/P&gt;&lt;P&gt;Maybe method 3 will work...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tnx&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jul 2009 02:24:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148215#M26539</guid>
      <dc:creator>xtrimf</dc:creator>
      <dc:date>2009-07-02T02:24:04Z</dc:date>
    </item>
    <item>
      <title>Two date ranges as dimensions</title>
      <link>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148216#M26540</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;With methods 1 and 2, you would indeed have "quarter ordered" and "quarter billed". But that is, after all, "necessary" if you want to be able to select different values for each.&lt;/P&gt;&lt;P&gt;Method 3 won't allow your users (at least without even more complexity) to select orders that were ordered in quarter 1 and billed in quarter 2, for instance. But if that's not a problem, then I'm a big fan of just having a "Quarter" field, a single chart that lets you easily switch between types of dates, and so on. I've done it in several applications, and like the results.&lt;/P&gt;&lt;P&gt;But for most applications, I suspect it is better to just create more than one calendar and have a bunch of different date names.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Jul 2009 06:06:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Two-date-ranges-as-dimensions/m-p/148216#M26540</guid>
      <dc:creator>johnw</dc:creator>
      <dc:date>2009-07-02T06:06:51Z</dc:date>
    </item>
  </channel>
</rss>

