<?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 Best practices in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Best-practices/m-p/192752#M54299</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is an old post, but for the benefit of anyone (else) who finds it in Google results, I'll share this comment: Store data at the lowest practical atomicity in your warehouse, and pull that into QlikView. QlikView can handle large data sets quite well, and will aggregate the data without any trouble.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 01 Apr 2011 21:35:53 GMT</pubDate>
    <dc:creator />
    <dc:date>2011-04-01T21:35:53Z</dc:date>
    <item>
      <title>Best practices</title>
      <link>https://community.qlik.com/t5/QlikView/Best-practices/m-p/192751#M54298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all. I am new to QlikView and i have to say that for the moment it is a real chalange to understand what is the best way to build a data model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have many questions that the training i did for a week did not answer them. It was just basics about qlikview technical part.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to know which is the best way for example to put on a report aggregated data ? Aggregate it in front end ? Create aggregate tables in the backend ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If i do it the backend then i will have problems with dates - calendars, etc...&lt;/P&gt;&lt;P&gt;What is your experience with thos things ?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Cristian.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Mar 2010 23:37:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Best-practices/m-p/192751#M54298</guid>
      <dc:creator />
      <dc:date>2010-03-24T23:37:10Z</dc:date>
    </item>
    <item>
      <title>Best practices</title>
      <link>https://community.qlik.com/t5/QlikView/Best-practices/m-p/192752#M54299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is an old post, but for the benefit of anyone (else) who finds it in Google results, I'll share this comment: Store data at the lowest practical atomicity in your warehouse, and pull that into QlikView. QlikView can handle large data sets quite well, and will aggregate the data without any trouble.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 01 Apr 2011 21:35:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Best-practices/m-p/192752#M54299</guid>
      <dc:creator />
      <dc:date>2011-04-01T21:35:53Z</dc:date>
    </item>
  </channel>
</rss>

