<?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: 2 calendars - best practice in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299913#M111082</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my case this dynamical was not really the wish &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ... it's just another way to solve the problem &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/grin.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 07 Nov 2011 11:15:25 GMT</pubDate>
    <dc:creator>Anonymous</dc:creator>
    <dc:date>2011-11-07T11:15:25Z</dc:date>
    <item>
      <title>2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299908#M111077</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;i my app i have to implement something like a switch to change the data field associated with my calendar:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;By default my calendar is associated with the registration date of a person to an event. I need also to have the ability to associate the calendar with a start date of an event. I was wondering if there is any simple best practice approach to that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a lot.&lt;/P&gt;&lt;P&gt;K&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 08:42:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299908#M111077</guid>
      <dc:creator />
      <dc:date>2011-11-07T08:42:36Z</dc:date>
    </item>
    <item>
      <title>2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299909#M111078</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear kalinkula,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could work with a variable to get a dynamic association. Set up a variable (e.g. vTimestamp) and create a listbox with predefined Values (the names of the table name you want to use as a key). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Edit afterwards your script and add the line §(vTimestamp) as MasterDate.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now the user can chose how he wants to associate the source_date with your calendar.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;David&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 09:38:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299909#M111078</guid>
      <dc:creator />
      <dc:date>2011-11-07T09:38:38Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299910#M111079</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi david,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thax for this hint - However, i am having dificulties to understand. I have attached a little sample file that illustrates my issue - maybe you can add your idea to it ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In its current status the calendar is linked to registration dates of people registrating to events. The events themselves have start dates. In this case i want to switch the calendar to work with the start dates of the event table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks a million.&lt;/P&gt;&lt;P&gt;K&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 10:04:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299910#M111079</guid>
      <dc:creator />
      <dc:date>2011-11-07T10:04:23Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299911#M111080</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had some simular issue here ... I solved it using 2 calendar's which are randomly visible according to the requested calender type.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;See attachement&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 10:37:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299911#M111080</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-11-07T10:37:59Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299912#M111081</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i read you oroiginal post about this topic - I would rather have something dynamically like Davin described...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 10:45:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299912#M111081</guid>
      <dc:creator />
      <dc:date>2011-11-07T10:45:04Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299913#M111082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;In my case this dynamical was not really the wish &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; ... it's just another way to solve the problem &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/grin.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 11:15:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299913#M111082</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-11-07T11:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299914#M111083</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 edited your qvw and implemented first a real calender (adjust start/enddate if you need). You can see a Inputfield as Dropdown filled with the fieldnames StartDate and RegDate. Depending on what you chose it will adjust your association like you can see when you do ctrl+t after running the script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; I hope this was what you were looking for.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 11:32:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299914#M111083</guid>
      <dc:creator />
      <dc:date>2011-11-07T11:32:43Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299915#M111084</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I also try to understand what you did ... so the association is only changed during load?? That's not really flexibel is it . . . in this way the user cannot select between the date fields.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 11:45:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299915#M111084</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-11-07T11:45:52Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299916#M111085</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks, David.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It works - but it seems only to work with a reload - i have to agree to Anita - that is unfortunately not very flexible.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any chance this works without a reload ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 12:29:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299916#M111085</guid>
      <dc:creator />
      <dc:date>2011-11-07T12:29:53Z</dc:date>
    </item>
    <item>
      <title>Re: 2 calendars - best practice</title>
      <link>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299917#M111086</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could consider doing something with a seperate calendar, which is not connected to any other table.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This table you use to make the date selections, in the set analysis of the expression you could take over the selection made in the seperate calendar, using the calender which you need of want (you could do this with a variable or as in my last example with an inline loaded table with the options).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I did do something like that before . . . but in the set analysis you got a lot of different options and possibilities . . . it didn't made me a happy programmer &lt;span class="lia-unicode-emoji" title=":winking_face:"&gt;😉&lt;/span&gt; . . .&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 07 Nov 2011 12:56:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/2-calendars-best-practice/m-p/299917#M111086</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2011-11-07T12:56:13Z</dc:date>
    </item>
  </channel>
</rss>

