<?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: Master Calendar without transaction dates in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440268#M432211</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you decide to go down the route of creating a single master calendar, it might be useful to think about what events are associated with your employees. In this case this might be a joining event and (possibly) a leaving event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you then create a fact table based on these two event types, it's a simple matter to create a single date field, and a couple of flags, one for a join event and one for a leave event. With this in place, you can chart your joiners, leavers and headcount (using accumulation).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 22 Aug 2017 08:46:35 GMT</pubDate>
    <dc:creator>marcus_malinow</dc:creator>
    <dc:date>2017-08-22T08:46:35Z</dc:date>
    <item>
      <title>Master Calendar without transaction dates</title>
      <link>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440265#M432208</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Qlikers,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are going to implement HR module at one client. &lt;/P&gt;&lt;P&gt;The scenario is, We are having Employee information like Date Of Joining, Date of Leaving, Dept and other information related to the employee.&lt;/P&gt;&lt;P&gt;Now we don't have any transaction date field related to employees and reports to be created are like below:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Monthly&amp;gt;Yearly Hiring/Leaving trends&lt;/LI&gt;&lt;LI&gt;Monthly Strength/headcount&lt;/LI&gt;&lt;LI&gt;Yearly Strength/Head Count&lt;/LI&gt;&lt;LI&gt;Headcount, Employees about to retire in next N months.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Need your advice and suggestions on how to build a data model in Qliksense so that we can work with calendar flexibility &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Many Thanks in advance..........&lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/plain.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 21 Aug 2017 20:57:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440265#M432208</guid>
      <dc:creator>ashishkalia</dc:creator>
      <dc:date>2017-08-21T20:57:32Z</dc:date>
    </item>
    <item>
      <title>Re: Master Calendar without transaction dates</title>
      <link>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440266#M432209</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I think you need 2 master calendar here. Because, you don't have transaction date. Create one calendar for DOJ and other is for DOL&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 00:52:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440266#M432209</guid>
      <dc:creator>Anil_Babu_Samineni</dc:creator>
      <dc:date>2017-08-22T00:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: Master Calendar without transaction dates</title>
      <link>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440267#M432210</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Ashish,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Check out this post by &lt;A href="https://community.qlik.com/people/hic"&gt;hic&lt;/A&gt; that sets out very clearly when multiple calendars will meet your needs and when you may need something extra called a canonical calendar.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3585"&gt;Canonical Date&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Andrew&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 07:58:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440267#M432210</guid>
      <dc:creator>effinty2112</dc:creator>
      <dc:date>2017-08-22T07:58:48Z</dc:date>
    </item>
    <item>
      <title>Re: Master Calendar without transaction dates</title>
      <link>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440268#M432211</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ashish,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;if you decide to go down the route of creating a single master calendar, it might be useful to think about what events are associated with your employees. In this case this might be a joining event and (possibly) a leaving event.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you then create a fact table based on these two event types, it's a simple matter to create a single date field, and a couple of flags, one for a join event and one for a leave event. With this in place, you can chart your joiners, leavers and headcount (using accumulation).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 22 Aug 2017 08:46:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Master-Calendar-without-transaction-dates/m-p/1440268#M432211</guid>
      <dc:creator>marcus_malinow</dc:creator>
      <dc:date>2017-08-22T08:46:35Z</dc:date>
    </item>
  </channel>
</rss>

