<?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 selection across different dates in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/selection-across-different-dates/m-p/587719#M1112286</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to create a 'master date' dimension, so people pick one date and have all three tables zoomed on that one date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about concatenate the 3 qty table, but then realize it's bad for my overall data structure which i didn't show in the example below. After few rounds of trying, i realize creating 3 stand alone tbls for each qty is easiest and cleanest approach. I didn't have any syn keys in my actual application, i used product + site# as key, where description of product and site are stored in status table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now all i need is the ability for people for find the date they are looking for and update the selection across 3 tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Mar 2014 03:53:24 GMT</pubDate>
    <dc:creator>yelin_nyu</dc:creator>
    <dc:date>2014-03-01T03:53:24Z</dc:date>
    <item>
      <title>selection across different dates</title>
      <link>https://community.qlik.com/t5/QlikView/selection-across-different-dates/m-p/587719#M1112286</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I want to create a 'master date' dimension, so people pick one date and have all three tables zoomed on that one date.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I thought about concatenate the 3 qty table, but then realize it's bad for my overall data structure which i didn't show in the example below. After few rounds of trying, i realize creating 3 stand alone tbls for each qty is easiest and cleanest approach. I didn't have any syn keys in my actual application, i used product + site# as key, where description of product and site are stored in status table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So now all i need is the ability for people for find the date they are looking for and update the selection across 3 tables.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Mar 2014 03:53:24 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/selection-across-different-dates/m-p/587719#M1112286</guid>
      <dc:creator>yelin_nyu</dc:creator>
      <dc:date>2014-03-01T03:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: selection across different dates</title>
      <link>https://community.qlik.com/t5/QlikView/selection-across-different-dates/m-p/587720#M1112287</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check out these blog posts : &lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2012/10/16/the-master-calendar" title="http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/16/the-master-calendar"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2012/10/16/the-master-calendar&lt;/A&gt;&lt;/P&gt;&lt;P&gt;and&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table" title="http://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2013/05/17/concatenate-vs-link-table&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Mar 2014 04:57:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/selection-across-different-dates/m-p/587720#M1112287</guid>
      <dc:creator>tresB</dc:creator>
      <dc:date>2014-03-01T04:57:39Z</dc:date>
    </item>
  </channel>
</rss>

