<?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: Architecture to avoid loops in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420188#M1159622</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you point me to the documentation on the Link table model?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Feb 2013 20:09:43 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-02-25T20:09:43Z</dc:date>
    <item>
      <title>Architecture to avoid loops</title>
      <link>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420186#M1159620</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am facing the following problem (see attached diagram).&lt;/P&gt;&lt;P&gt;I have 2 systems (SysA and SysB) with some databases (SQL and MySQL).&lt;/P&gt;&lt;P&gt;Both have tables related to users and projects.&lt;/P&gt;&lt;P&gt;Both contain different information (ie one table has the user name while the other has its telefon number) and I would like to aggregate that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I already 'joined' the projects tables using the AS keyword to rename the key in both project tales.&lt;/P&gt;&lt;P&gt;Now I would like to do the same with the users but it creates loops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is the best approch to handle this?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 08 Feb 2013 17:08:14 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420186#M1159620</guid>
      <dc:creator />
      <dc:date>2013-02-08T17:08:14Z</dc:date>
    </item>
    <item>
      <title>Re: Architecture to avoid loops</title>
      <link>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420187#M1159621</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Whenever I have an association challenge like this, I turn to the Link Table model.&amp;nbsp; It has yet to fail me in the most complex association situations.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Feb 2013 21:39:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420187#M1159621</guid>
      <dc:creator>hallquist_nate</dc:creator>
      <dc:date>2013-02-11T21:39:49Z</dc:date>
    </item>
    <item>
      <title>Re: Architecture to avoid loops</title>
      <link>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420188#M1159622</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you point me to the documentation on the Link table model?&amp;nbsp; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Feb 2013 20:09:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Architecture-to-avoid-loops/m-p/420188#M1159622</guid>
      <dc:creator />
      <dc:date>2013-02-25T20:09:43Z</dc:date>
    </item>
  </channel>
</rss>

