<?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: How to understand data modelling in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1733895#M721032</link>
    <description>&lt;P&gt;A Data Model in QlikView can be said as a combination of fact and dimension and it is part of schema.&lt;/P&gt;&lt;P&gt;When the source&amp;nbsp;data&amp;nbsp;are from tables that have more than one common column,&amp;nbsp;QlikView&amp;nbsp;will end up adding synthetic keys to tables and create a more complicated&amp;nbsp;data model&amp;nbsp;when it translates relational&amp;nbsp;data&amp;nbsp;into associative&amp;nbsp;data.&lt;/P&gt;&lt;P&gt;One can create the data model as per the application requirement.&lt;/P&gt;&lt;P&gt;Commonly Snowflake is used to limit duplicate data which is irrelevant in QlikView's case as it automatically eliminates duplicates by design i.e. if a value is repeated, it only stores once.&lt;/P&gt;&lt;P&gt;In QlikView, Star schema is an ideal choice ,In a star schema, ideally, there is a fact table at the centre containing the key fields that servers as a link to other tables.&lt;/P&gt;&lt;P&gt;Best practice for data modelling in QlikView is all about making your data well-structured and logically feasible to optimize data processing and analysis in QlikView. This can achieve by plotting out a design with specific operations (ETL) you need to perform on your intended data set in order to get your data in a perfect data model.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Also Following the stated Practices an ideal data model can be achieved.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Incremental Load using QVD files - An incremental load is just the new data or the updated data that is to add in &amp;nbsp; &amp;nbsp; an already existing data file. For better and faster loading of incremental load,&amp;nbsp;QVD files&amp;nbsp;recommend.&lt;/P&gt;&lt;P&gt;2.Combining Tables with Join and Keep - To combine two&amp;nbsp;tables&amp;nbsp;which may or may not have fields or field values in common,&amp;nbsp;join&amp;nbsp;and Keep prefixes are used in QlikView.&lt;/P&gt;&lt;P&gt;3. Use Mapping as an Alternative to Joining - The Mapping function works much efficiently. Using Mapping keyword, you can map fields from one table into another.&lt;/P&gt;&lt;P&gt;4. Creating a Date Interval from a Single Date&lt;/P&gt;&lt;P&gt;5. Matching Intervals to Discrete Data&lt;/P&gt;&lt;P&gt;6. Working with Cross Tables&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Types of LOADS in QlikView&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There are various types of load used in QlikView, describing them below:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.Loading data from the file&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This method is normal method of loading data into the QlikView application. Load data from files like Excel, MSDB, CSV, Txt files etc., can be done by creating ODBC and connecting to your database directly.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;A,&lt;/P&gt;&lt;P&gt;B&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;FROM&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;(biff, embedded labels, table is Data$);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. Inline Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The second method of loading is Inline Load where the user can define their own data and load within QlikView. The Inline data can be defined in the inline Data Wizard . Insert&lt;/SPAN&gt;&lt;SPAN&gt;à&lt;/SPAN&gt;&lt;SPAN&gt;Load Data&lt;/SPAN&gt;&lt;SPAN&gt;à&lt;/SPAN&gt;&lt;SPAN&gt; Inline Data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD * INLINE [ A B C ];&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Resident Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Loading data from already loaded QlikView table is possible using Resident Load. Transformations and Calculations can be performed in the resident load script. Loading an existing field or a succeeding table is possible too.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Employees:&lt;/P&gt;&lt;P&gt;Select&lt;/P&gt;&lt;P&gt;Empname,&lt;/P&gt;&lt;P&gt;HireDate,&lt;/P&gt;&lt;P&gt;Salary,&lt;/P&gt;&lt;P&gt;Incentives&lt;/P&gt;&lt;P&gt;From Employee;&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; Empname,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Month(HireDate),&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Salary + Incentives as &lt;/SPAN&gt;&lt;SPAN&gt;‘&lt;/SPAN&gt;&lt;SPAN&gt;GrossSalary&lt;/SPAN&gt;&lt;SPAN&gt;’&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Resident Employees;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. Incremental Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Incremental load is used to load only the new or changed records. It will be very helpful where a database is big. This involves loading old data from the QVD and new records from the database and combine into single QVD.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SQL SELECT&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; PrimaryKey,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;X,&lt;/P&gt;&lt;P&gt;Y&lt;/P&gt;&lt;P&gt;FROM DB_TABLE WHERE ModificationTime &amp;gt;= #$(LastExecTime)# AND ModificationTime &amp;lt; #$(BeginningThisExecTime)#;&lt;/P&gt;&lt;P&gt;Concatenate&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;LOAD&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; PrimaryKey,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&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;&lt;/SPAN&gt;&lt;SPAN&gt; X,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&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;&lt;/SPAN&gt;&lt;SPAN&gt; Y&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;FROM File.QVD;&lt;/P&gt;&lt;P&gt;STORE QV_Table INTO File.QVD;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. &lt;/STRONG&gt;&lt;STRONG&gt;Binary Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Loading data from one QlikView file is called Binary Loading. The data model of one QVW file is copied from RAM to disk in 0s and 1s for another qvw file. This Binary Load will be more useful when you want to enhance the already built qvw with the same metrices defined.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Binary c:order.qvw;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;6. ADD Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Add Load is used to append or concatenate the data from one table to other table. During a partial reload the QlikView table, for which a table name is generated by the add load/add select statement (provided such a table exists), will be appended with the result of the add load/add select statement. Since it would not check for duplicates, it is required us suitable where condition in the script.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;ENO,&lt;/P&gt;&lt;P&gt;ENAME&lt;/P&gt;&lt;P&gt;FROM Employees.csv;&lt;/P&gt;&lt;P&gt;ADD LOAD ENO,&lt;/P&gt;&lt;P&gt;ENAME&lt;/P&gt;&lt;P&gt;FROM Employees1.csv Where Not Exists(ENO);&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;7. Buffer Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Buffer load helps to create the QVD files automatically. The created QVD will be maintained as defined in User Preferences Locations.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Buffer select * from Employees.csv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;8. Preceding&amp;nbsp;Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;T&lt;/STRONG&gt;his&amp;nbsp; allows you to load a table in one pass, but still define several successive transformations.&amp;nbsp;&lt;/P&gt;&lt;P&gt;eg:&lt;/P&gt;&lt;P&gt;LOAD ..., ReferenceDate, Age( ReferenceDate, BirthDate ) as Age&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;LOAD *, Date( FromDate + IterNo() – 1 ) as ReferenceDate Resident Policies While IterNo() &amp;lt;= ToDate - FromDate + 1&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 06 Aug 2020 18:48:57 GMT</pubDate>
    <dc:creator>maushmi</dc:creator>
    <dc:date>2020-08-06T18:48:57Z</dc:date>
    <item>
      <title>How to understand data modelling</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1733238#M721031</link>
      <description>&lt;P&gt;I wud like to understand data modelling in qlickview and how various loads r used&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 25 Nov 2020 16:16:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1733238#M721031</guid>
      <dc:creator>ashishtiwari</dc:creator>
      <dc:date>2020-11-25T16:16:04Z</dc:date>
    </item>
    <item>
      <title>Re: How to understand data modelling</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1733895#M721032</link>
      <description>&lt;P&gt;A Data Model in QlikView can be said as a combination of fact and dimension and it is part of schema.&lt;/P&gt;&lt;P&gt;When the source&amp;nbsp;data&amp;nbsp;are from tables that have more than one common column,&amp;nbsp;QlikView&amp;nbsp;will end up adding synthetic keys to tables and create a more complicated&amp;nbsp;data model&amp;nbsp;when it translates relational&amp;nbsp;data&amp;nbsp;into associative&amp;nbsp;data.&lt;/P&gt;&lt;P&gt;One can create the data model as per the application requirement.&lt;/P&gt;&lt;P&gt;Commonly Snowflake is used to limit duplicate data which is irrelevant in QlikView's case as it automatically eliminates duplicates by design i.e. if a value is repeated, it only stores once.&lt;/P&gt;&lt;P&gt;In QlikView, Star schema is an ideal choice ,In a star schema, ideally, there is a fact table at the centre containing the key fields that servers as a link to other tables.&lt;/P&gt;&lt;P&gt;Best practice for data modelling in QlikView is all about making your data well-structured and logically feasible to optimize data processing and analysis in QlikView. This can achieve by plotting out a design with specific operations (ETL) you need to perform on your intended data set in order to get your data in a perfect data model.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Also Following the stated Practices an ideal data model can be achieved.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;1. Incremental Load using QVD files - An incremental load is just the new data or the updated data that is to add in &amp;nbsp; &amp;nbsp; an already existing data file. For better and faster loading of incremental load,&amp;nbsp;QVD files&amp;nbsp;recommend.&lt;/P&gt;&lt;P&gt;2.Combining Tables with Join and Keep - To combine two&amp;nbsp;tables&amp;nbsp;which may or may not have fields or field values in common,&amp;nbsp;join&amp;nbsp;and Keep prefixes are used in QlikView.&lt;/P&gt;&lt;P&gt;3. Use Mapping as an Alternative to Joining - The Mapping function works much efficiently. Using Mapping keyword, you can map fields from one table into another.&lt;/P&gt;&lt;P&gt;4. Creating a Date Interval from a Single Date&lt;/P&gt;&lt;P&gt;5. Matching Intervals to Discrete Data&lt;/P&gt;&lt;P&gt;6. Working with Cross Tables&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Types of LOADS in QlikView&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;There are various types of load used in QlikView, describing them below:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.Loading data from the file&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;This method is normal method of loading data into the QlikView application. Load data from files like Excel, MSDB, CSV, Txt files etc., can be done by creating ODBC and connecting to your database directly.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;A,&lt;/P&gt;&lt;P&gt;B&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;FROM&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;(biff, embedded labels, table is Data$);&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;2. Inline Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The second method of loading is Inline Load where the user can define their own data and load within QlikView. The Inline data can be defined in the inline Data Wizard . Insert&lt;/SPAN&gt;&lt;SPAN&gt;à&lt;/SPAN&gt;&lt;SPAN&gt;Load Data&lt;/SPAN&gt;&lt;SPAN&gt;à&lt;/SPAN&gt;&lt;SPAN&gt; Inline Data.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD * INLINE [ A B C ];&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;3. Resident Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Loading data from already loaded QlikView table is possible using Resident Load. Transformations and Calculations can be performed in the resident load script. Loading an existing field or a succeeding table is possible too.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Employees:&lt;/P&gt;&lt;P&gt;Select&lt;/P&gt;&lt;P&gt;Empname,&lt;/P&gt;&lt;P&gt;HireDate,&lt;/P&gt;&lt;P&gt;Salary,&lt;/P&gt;&lt;P&gt;Incentives&lt;/P&gt;&lt;P&gt;From Employee;&lt;/P&gt;&lt;P&gt;Load&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; Empname,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Month(HireDate),&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Salary + Incentives as &lt;/SPAN&gt;&lt;SPAN&gt;‘&lt;/SPAN&gt;&lt;SPAN&gt;GrossSalary&lt;/SPAN&gt;&lt;SPAN&gt;’&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Resident Employees;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;4. Incremental Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Incremental load is used to load only the new or changed records. It will be very helpful where a database is big. This involves loading old data from the QVD and new records from the database and combine into single QVD.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;SQL SELECT&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; PrimaryKey,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;X,&lt;/P&gt;&lt;P&gt;Y&lt;/P&gt;&lt;P&gt;FROM DB_TABLE WHERE ModificationTime &amp;gt;= #$(LastExecTime)# AND ModificationTime &amp;lt; #$(BeginningThisExecTime)#;&lt;/P&gt;&lt;P&gt;Concatenate&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;LOAD&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt; PrimaryKey,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&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;&lt;/SPAN&gt;&lt;SPAN&gt; X,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&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;&lt;/SPAN&gt;&lt;SPAN&gt; Y&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;FROM File.QVD;&lt;/P&gt;&lt;P&gt;STORE QV_Table INTO File.QVD;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;5. &lt;/STRONG&gt;&lt;STRONG&gt;Binary Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Loading data from one QlikView file is called Binary Loading. The data model of one QVW file is copied from RAM to disk in 0s and 1s for another qvw file. This Binary Load will be more useful when you want to enhance the already built qvw with the same metrices defined.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Binary c:order.qvw;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;6. ADD Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Add Load is used to append or concatenate the data from one table to other table. During a partial reload the QlikView table, for which a table name is generated by the add load/add select statement (provided such a table exists), will be appended with the result of the add load/add select statement. Since it would not check for duplicates, it is required us suitable where condition in the script.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;ENO,&lt;/P&gt;&lt;P&gt;ENAME&lt;/P&gt;&lt;P&gt;FROM Employees.csv;&lt;/P&gt;&lt;P&gt;ADD LOAD ENO,&lt;/P&gt;&lt;P&gt;ENAME&lt;/P&gt;&lt;P&gt;FROM Employees1.csv Where Not Exists(ENO);&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;7. Buffer Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Buffer load helps to create the QVD files automatically. The created QVD will be maintained as defined in User Preferences Locations.&lt;/P&gt;&lt;P&gt;Ex:&lt;/P&gt;&lt;P&gt;Buffer select * from Employees.csv&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;8. Preceding&amp;nbsp;Load&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&amp;nbsp;T&lt;/STRONG&gt;his&amp;nbsp; allows you to load a table in one pass, but still define several successive transformations.&amp;nbsp;&lt;/P&gt;&lt;P&gt;eg:&lt;/P&gt;&lt;P&gt;LOAD ..., ReferenceDate, Age( ReferenceDate, BirthDate ) as Age&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;LOAD *, Date( FromDate + IterNo() – 1 ) as ReferenceDate Resident Policies While IterNo() &amp;lt;= ToDate - FromDate + 1&lt;/P&gt;&lt;P&gt;;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 06 Aug 2020 18:48:57 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1733895#M721032</guid>
      <dc:creator>maushmi</dc:creator>
      <dc:date>2020-08-06T18:48:57Z</dc:date>
    </item>
    <item>
      <title>Re: How to understand data modelling</title>
      <link>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1736876#M721033</link>
      <description>&lt;P&gt;In addition to the post below, I would recommend reviewing the following Help link, there is a lot of additional information there to absorb on the topic too:&lt;/P&gt;&lt;P&gt;&lt;A href="https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/Loading_data.htm" target="_blank"&gt;https://help.qlik.com/en-US/qlikview/April2020/Subsystems/Client/Content/QV_QlikView/Loading_data.htm&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Tue, 18 Aug 2020 18:58:03 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/How-to-understand-data-modelling/m-p/1736876#M721033</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2020-08-18T18:58:03Z</dc:date>
    </item>
  </channel>
</rss>

