<?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: Avoiding Circular Joins in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604577#M1234063</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes.But if you have more than one common column Qlikview&amp;nbsp; will generate synthetic tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is fine until unless you have any issue interns of performance or understanding of data model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of synthetic keys you never get wrong data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 20 Mar 2014 20:48:19 GMT</pubDate>
    <dc:creator>chiru_thota</dc:creator>
    <dc:date>2014-03-20T20:48:19Z</dc:date>
    <item>
      <title>Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604575#M1234059</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If multiple columns from different tables are having the same name, does Qlikview automatically join them? If yes, how does it take care of circular joins etc. ?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 16:26:21 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604575#M1234059</guid>
      <dc:creator />
      <dc:date>2026-01-26T16:26:21Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604576#M1234061</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is true. Qlikview links tables on similar field names. If there is a circular loop the largest table will be loosely coupled. This is not recommended.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 20:45:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604576#M1234061</guid>
      <dc:creator>cgdonders</dc:creator>
      <dc:date>2014-03-20T20:45:49Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604577#M1234063</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes.But if you have more than one common column Qlikview&amp;nbsp; will generate synthetic tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this is fine until unless you have any issue interns of performance or understanding of data model.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of synthetic keys you never get wrong data.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 20:48:19 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604577#M1234063</guid>
      <dc:creator>chiru_thota</dc:creator>
      <dc:date>2014-03-20T20:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604578#M1234065</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;use below url in the attached txt file to understand circular reference and how it is different from synthetic keys.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Circular reference will give wrong data if data is coming from loosely coupled tables.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;also have look at below ppt.it is really helpful.&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/docs/DOC-5830"&gt;Data Modeling issues and solutions&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 20 Mar 2014 20:50:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604578#M1234065</guid>
      <dc:creator>chiru_thota</dc:creator>
      <dc:date>2014-03-20T20:50:52Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604579#M1234066</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/45424"&gt;How circular reference can be avoided?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/thread/28959"&gt;What is Circular reference? How to avoid them?&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/blogs/qlikviewdesignblog/2013/06/25/circular-references" title="http://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>Thu, 20 Mar 2014 20:51:01 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604579#M1234066</guid>
      <dc:creator>MK_QSL</dc:creator>
      <dc:date>2014-03-20T20:51:01Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular Joins</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604580#M1234068</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your prompt responses.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Apr 2014 17:51:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-Joins/m-p/604580#M1234068</guid>
      <dc:creator />
      <dc:date>2014-04-09T17:51:59Z</dc:date>
    </item>
  </channel>
</rss>

