<?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 Reference Problem in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422771#M157544</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Qualify statement helps, but if you really need the relationship between Calls and Manta2, why not do a join? e.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualify *;&lt;/P&gt;&lt;P&gt;Unqualify transporter_ID, hub_id, manta2_id, call_id // so you can still have your other links working without rewriting all your code&lt;/P&gt;&lt;P&gt;(other selects)&lt;/P&gt;&lt;P&gt;Select * from Calls&lt;/P&gt;&lt;P&gt;LEFT OUTER JOIN Manta2 on Call_Manta2_ID=Call_Manta2_ID&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had a similar problem recently, and this worked for me. Using the Qualify statement breaks the implicit joins that QV makes when fields in different tables have the same name, but you can unqualify the links you do want. Then you just do an explicit join in your script. You get the same result, but the circular reference is broken. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My manager thinks it's good coding practice to use a Qualify statement in all scripts that involve more than two tables, unless you're absolutely certain all the field names are unique. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 19 Sep 2012 20:53:30 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-09-19T20:53:30Z</dc:date>
    <item>
      <title>Circular Reference Problem</title>
      <link>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422769#M157542</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;I have a problem with circular reference and i can't solve it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attached the data diagram&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can i solve it ???&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance,&lt;/P&gt;&lt;P&gt;Mona&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 14:15:54 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422769#M157542</guid>
      <dc:creator />
      <dc:date>2012-09-19T14:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: Circular Reference Problem</title>
      <link>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422770#M157543</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is happening because you can get to multiple tables in multiple different ways.&amp;nbsp; I would start by using the QUALIFY * statement on your load script, and then rename like fields so that you can link the tables the way you would like them to be linked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Either this, or just rename the key fields to break the link between one of the tables such as the Mant2a and Calls table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 18:17:26 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422770#M157543</guid>
      <dc:creator>goldnejea8</dc:creator>
      <dc:date>2012-09-19T18:17:26Z</dc:date>
    </item>
    <item>
      <title>Re: Circular Reference Problem</title>
      <link>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422771#M157544</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The Qualify statement helps, but if you really need the relationship between Calls and Manta2, why not do a join? e.g.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qualify *;&lt;/P&gt;&lt;P&gt;Unqualify transporter_ID, hub_id, manta2_id, call_id // so you can still have your other links working without rewriting all your code&lt;/P&gt;&lt;P&gt;(other selects)&lt;/P&gt;&lt;P&gt;Select * from Calls&lt;/P&gt;&lt;P&gt;LEFT OUTER JOIN Manta2 on Call_Manta2_ID=Call_Manta2_ID&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had a similar problem recently, and this worked for me. Using the Qualify statement breaks the implicit joins that QV makes when fields in different tables have the same name, but you can unqualify the links you do want. Then you just do an explicit join in your script. You get the same result, but the circular reference is broken. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My manager thinks it's good coding practice to use a Qualify statement in all scripts that involve more than two tables, unless you're absolutely certain all the field names are unique. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Sep 2012 20:53:30 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Circular-Reference-Problem/m-p/422771#M157544</guid>
      <dc:creator />
      <dc:date>2012-09-19T20:53:30Z</dc:date>
    </item>
  </channel>
</rss>

