<?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: circular references in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799063#M1050108</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When designing a datamodel in Qlikview, circular reference is quite a common thing.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;There are several solutions to prevent such loops like the concatenate function or link table. Although the best solution to fix circular reference depends on the situation, I personally prefer the link table most of the times. When you have two fact tables for example, which shares more then one dimension, it means there is circular reference.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture11.JPG" style="color: #333333;"&gt;&lt;IMG alt="picture1" class="wp-image-918 size-medium aligncenter jiveImage" height="239" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture11-300x239.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture1" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;To prevent this situation we could use the concatenate function to create one major facttable. You could consider this solution when both tables have many similarities. When using the concatenate function, always dwell on the fact that, if the measure fields in both facttables are the same, calculations will cover all records of the table. Of course there is the possibility to create a field and specify the facttype so you can select ‘Fact1’ or ‘Fact2’ and use set analysis in your expressions but I think it’s clear that this isn’t an easy solution when the records always need to be separated in all expressions.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;Example 1: Concatenate two fact tables.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;//**************************************************************************&lt;BR /&gt;// FACT TABLE&lt;BR /&gt;//**************************************************************************&lt;BR /&gt;FACT:&lt;BR /&gt;load&lt;BR /&gt;‘Fact1’&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS Facttype&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS %KEY_FACT1_ID&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; Measure&lt;BR /&gt;From……&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;CONCATENATE&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;load&lt;BR /&gt;‘Fact2’&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS Facttype&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS %KEY_FACT2_ID&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; Measure&lt;BR /&gt;From……&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;What about concatenate if the fields in the facttables are quite different? Rationally this does not seem to be a good idea is it? Let’s demonstrate this with an example of two different processes.&amp;nbsp; The facts are:&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;- The purchase of products&lt;BR /&gt;- The selling of products&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When loading the original datamodel, Qlikview has to create a synthetic key because the dimensions date and product are shared. Although the synthetic key in this situation works fine, it’s better to prevent this.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture3.JPG" style="color: #333333;"&gt;&lt;IMG alt="picture3" class="size-medium aligncenter jiveImage wp-image-935" height="162" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture3-300x162.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture3" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When we concatenate the purchase and selling table, the synthetic key is gone and the problem is solved. Allthough naturally this just doesn’t feel like the ‘right’ way, there is no difference for the end user because the interface of Qlikview works on attribute level. For Qlikview, this is best practice and a good way of solving circular reference. Keep in mind that, for solutions with many tables, the overall picture for the developer is getting less clear. In that case it’s better (in my opinion) to use link tables.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture4.JPG" style="color: #555555;"&gt;&lt;IMG alt="picture4" class="size-medium aligncenter wp-image-936 jiveImage" height="236" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture4-300x236.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture4" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Nov 2014 09:55:44 GMT</pubDate>
    <dc:creator>sujeetsingh</dc:creator>
    <dc:date>2014-11-10T09:55:44Z</dc:date>
    <item>
      <title>circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799061#M1050106</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;what is&amp;nbsp; circular references and how we can remove.?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 09:47:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799061#M1050106</guid>
      <dc:creator />
      <dc:date>2014-11-10T09:47:54Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799062#M1050107</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Go through this link&amp;nbsp;&amp;nbsp; &lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2013/06/25/circular-references"&gt;http://community.qlik.com/blogs/qlikviewdesignblog/2013/06/25/circular-references&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 09:49:23 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799062#M1050107</guid>
      <dc:creator>senpradip007</dc:creator>
      <dc:date>2014-11-10T09:49:23Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799063#M1050108</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When designing a datamodel in Qlikview, circular reference is quite a common thing.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;There are several solutions to prevent such loops like the concatenate function or link table. Although the best solution to fix circular reference depends on the situation, I personally prefer the link table most of the times. When you have two fact tables for example, which shares more then one dimension, it means there is circular reference.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture11.JPG" style="color: #333333;"&gt;&lt;IMG alt="picture1" class="wp-image-918 size-medium aligncenter jiveImage" height="239" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture11-300x239.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture1" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;To prevent this situation we could use the concatenate function to create one major facttable. You could consider this solution when both tables have many similarities. When using the concatenate function, always dwell on the fact that, if the measure fields in both facttables are the same, calculations will cover all records of the table. Of course there is the possibility to create a field and specify the facttype so you can select ‘Fact1’ or ‘Fact2’ and use set analysis in your expressions but I think it’s clear that this isn’t an easy solution when the records always need to be separated in all expressions.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;Example 1: Concatenate two fact tables.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;//**************************************************************************&lt;BR /&gt;// FACT TABLE&lt;BR /&gt;//**************************************************************************&lt;BR /&gt;FACT:&lt;BR /&gt;load&lt;BR /&gt;‘Fact1’&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS Facttype&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS %KEY_FACT1_ID&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; Measure&lt;BR /&gt;From……&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;CONCATENATE&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;load&lt;BR /&gt;‘Fact2’&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS Facttype&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; ID&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AS %KEY_FACT2_ID&lt;BR /&gt;,&amp;nbsp;&amp;nbsp;&amp;nbsp; Measure&lt;BR /&gt;From……&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;What about concatenate if the fields in the facttables are quite different? Rationally this does not seem to be a good idea is it? Let’s demonstrate this with an example of two different processes.&amp;nbsp; The facts are:&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;- The purchase of products&lt;BR /&gt;- The selling of products&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When loading the original datamodel, Qlikview has to create a synthetic key because the dimensions date and product are shared. Although the synthetic key in this situation works fine, it’s better to prevent this.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture3.JPG" style="color: #333333;"&gt;&lt;IMG alt="picture3" class="size-medium aligncenter jiveImage wp-image-935" height="162" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture3-300x162.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture3" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;When we concatenate the purchase and selling table, the synthetic key is gone and the problem is solved. Allthough naturally this just doesn’t feel like the ‘right’ way, there is no difference for the end user because the interface of Qlikview works on attribute level. For Qlikview, this is best practice and a good way of solving circular reference. Keep in mind that, for solutions with many tables, the overall picture for the developer is getting less clear. In that case it’s better (in my opinion) to use link tables.&lt;/P&gt;&lt;P style="margin-bottom: 18px; color: #555555; font-family: 'Century Gothic', 'Avant Garde', Arial, Helvetica, sans-serif; font-size: 14px;"&gt;&lt;A href="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture4.JPG" style="color: #555555;"&gt;&lt;IMG alt="picture4" class="size-medium aligncenter wp-image-936 jiveImage" height="236" src="http://www.quickqlearqool.nl/wp-content/uploads/2009/10/picture4-300x236.jpg" style="border: none; margin-left: auto; margin-right: auto; margin-bottom: 10px;" title="picture4" width="300" /&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 09:55:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799063#M1050108</guid>
      <dc:creator>sujeetsingh</dc:creator>
      <dc:date>2014-11-10T09:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799064#M1050109</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;In the load script use &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Qualify or Unqualify&lt;/P&gt;&lt;P&gt;2. If possible join the tables &lt;/P&gt;&lt;P&gt;3. By renaming using alias names to the field&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 10:00:16 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799064#M1050109</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-11-10T10:00:16Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799065#M1050110</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;among 2 fact tables sharing multiple dimension then we will get circular refernce.&lt;/P&gt;&lt;P&gt;Ways to remove&lt;/P&gt;&lt;P&gt;1)commenting field&lt;/P&gt;&lt;P&gt;2)renaming field&lt;/P&gt;&lt;P&gt;3)using qualifier unqulifier statments ,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 10:09:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799065#M1050110</guid>
      <dc:creator />
      <dc:date>2014-11-10T10:09:30Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799066#M1050111</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;Let assume this simple example&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD * Inline&lt;/P&gt;&lt;P&gt;[ Name,Address&lt;/P&gt;&lt;P&gt; A,India &lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;];&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD * Inline&lt;/P&gt;&lt;P&gt;[ Name,Sale&lt;/P&gt;&lt;P&gt;&amp;nbsp; A,150000&amp;nbsp; ];&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Sale_Address:&lt;/P&gt;&lt;P&gt;LOAD * Inline&lt;/P&gt;&lt;P&gt;[ Sale,Address&lt;/P&gt;&lt;P&gt;&amp;nbsp; 150000,India ];&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;LOAD&lt;/P&gt;&lt;P&gt;Sale,Address as PersonAddress&lt;/P&gt;&lt;P&gt;Resident Salary_Address;&lt;/P&gt;&lt;P&gt;DROP Table Salary_Address;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here you can join the two tables or qualify the tables&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 10:10:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799066#M1050111</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-11-10T10:10:34Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799067#M1050112</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;assume that if u have A,B,C table.you have relationship between A-B,B-C,C-A like this situation shows there is a circuler refference&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to avoid this situation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1)Using qualify and unqualify statements&lt;/P&gt;&lt;P&gt;2)renaming field&lt;/P&gt;&lt;P&gt;3) Here we got Circular refference between A,B,C so we use below statement after all load statements of table&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Loosen tables A,B,C;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 10:15:51 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799067#M1050112</guid>
      <dc:creator />
      <dc:date>2014-11-10T10:15:51Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799068#M1050113</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;Please close the thread if you got correct answer from the thread as appropriate answer correct or helpful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;Anand&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Nov 2014 11:51:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799068#M1050113</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-11-10T11:51:45Z</dc:date>
    </item>
    <item>
      <title>Re: circular references</title>
      <link>https://community.qlik.com/t5/QlikView/circular-references/m-p/799069#M1050114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've created a tutorial which includes a section on circular references.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The start of the tutorial is here: &lt;A href="https://community.qlik.com/docs/DOC-7364"&gt;QlikView 11 Developer Tutorial&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The circular references piece is here: &lt;A href="https://community.qlik.com/docs/DOC-7500"&gt;QlikView 11 Developer Tutorial - part 18&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Nov 2014 22:44:36 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/circular-references/m-p/799069#M1050114</guid>
      <dc:creator />
      <dc:date>2014-11-26T22:44:36Z</dc:date>
    </item>
  </channel>
</rss>

