<?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 References in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-References/m-p/1060343#M354991</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need either a different key between Invoices and Adwords maybe a combined key like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;autonumber(Shop &amp;amp; '|' &amp;amp; Date) as KEY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so that you could use only one key to master-calendar or if this isn't suitable a second master-calendar so that each fact-table gets a own calendar and/or matching both fact-tables to a single table - for this see also:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/2730"&gt;Why You sometimes should Load a Master Table several times&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3585"&gt;Canonical Date&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 06 Feb 2016 14:22:48 GMT</pubDate>
    <dc:creator>marcus_sommer</dc:creator>
    <dc:date>2016-02-06T14:22:48Z</dc:date>
    <item>
      <title>Avoiding Circular References</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-References/m-p/1060342#M354990</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I would like you to help me with the following issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example I have some data from our ERP in QlikView. For information: We have 7 OnlineShops.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now I import data (via QVSource) from our Google Adwords Account and the challenge is, that the managers of the different shops are able to compare the costs from Google Adwords with the sales in our ERP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I try to show our QlikView database structure in a simplified example.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;IMG alt="Screenshot_5.png" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/113721_Screenshot_5.png" style="height: 471px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ERP data and the adwords data are linked via MasterCalendar. This enables us to choose calendar weeks, month, ...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If I now would link the ERP Shop field with the Adwords Shop field, I would get a circular reference. I think, there must be an easy way to compare data from different sources splitted into single shops and I think I've got an error in reasoning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you please help me..I feel like theres an absolute easy way and I'm blind at the moment...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in Advance&lt;/P&gt;&lt;P&gt;Oliver&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Feb 2016 13:27:44 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-References/m-p/1060342#M354990</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2016-02-05T13:27:44Z</dc:date>
    </item>
    <item>
      <title>Re: Avoiding Circular References</title>
      <link>https://community.qlik.com/t5/QlikView/Avoiding-Circular-References/m-p/1060343#M354991</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need either a different key between Invoices and Adwords maybe a combined key like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;autonumber(Shop &amp;amp; '|' &amp;amp; Date) as KEY&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;so that you could use only one key to master-calendar or if this isn't suitable a second master-calendar so that each fact-table gets a own calendar and/or matching both fact-tables to a single table - for this see also:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/2730"&gt;Why You sometimes should Load a Master Table several times&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.qlik.com/qlik-blogpost/3585"&gt;Canonical Date&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Marcus&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 06 Feb 2016 14:22:48 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Avoiding-Circular-References/m-p/1060343#M354991</guid>
      <dc:creator>marcus_sommer</dc:creator>
      <dc:date>2016-02-06T14:22:48Z</dc:date>
    </item>
  </channel>
</rss>

