<?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: Problems with data structure in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852023#M1008014</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi DataNibbler,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sorry for the poor explanation. Seems about right wwhat you are saying. I'll check out the thing you mentioned about mapping and see if that helps.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 18 May 2015 06:51:49 GMT</pubDate>
    <dc:creator />
    <dc:date>2015-05-18T06:51:49Z</dc:date>
    <item>
      <title>Problems with data structure</title>
      <link>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852021#M1008012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm having some problems with how too structure the data. We're using Qlikview to follow up our ticket system BMC Remedy.&lt;/P&gt;&lt;P&gt;I started having problems when I have too many tables that "have" to be linked to each other.&lt;/P&gt;&lt;P&gt;Here's some pictures to help you understand my problem.&lt;/P&gt;&lt;P&gt;&lt;IMG alt="QV-Q.JPG" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/86426_QV-Q.JPG" style="width: 620px; height: 344px;" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have 5 tables with data. 3 of them (incident, change, problem) contains all the tickets and Incident_Assciation and Task contains some ticket information but also a "relationship" value to the other tickets.&lt;/P&gt;&lt;P&gt;This is how our data model looks right now:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="QV-Q2.JPG" class="jive-image image-2" src="https://community.qlik.com/legacyfs/online/86427_QV-Q2.JPG" style="width: 620px; height: 381px;" /&gt; &lt;/P&gt;&lt;P&gt;The Incident_Assocation contains both two values, $Related_INC which is the original ticket and $Related which is a Problem or Change ticket. The problem now is that I also want the Task information to get linked with these tables. It contains TaskID and Related_to which is a Incident, Change or Problem ticket number. When I try to link these tables I get a loop.&lt;/P&gt;&lt;P&gt;Which is the best approach to fix build this data model?&lt;/P&gt;&lt;P&gt;Heres a pictures of some dummy values to help see what I mean:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="QV-Q3.JPG" class="jive-image image-3" src="https://community.qlik.com/legacyfs/online/86428_QV-Q3.JPG" style="width: 620px; height: 442px;" /&gt;&lt;/P&gt;&lt;P&gt;Sorry for type-o's and such, English isn't my main language. &lt;IMG src="https://community.qlik.com/legacyfs/online/emoticons/happy.png" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 11:55:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852021#M1008012</guid>
      <dc:creator />
      <dc:date>2015-05-13T11:55:08Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with data structure</title>
      <link>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852022#M1008013</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Christian,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't fully understand your issue, but apparently, that table has fields that should actually be linked to two different tables, which will give you a loop. So you can link it to only one table, but that way some flexibility will be lost. Is that about right?&lt;/P&gt;&lt;P&gt;=&amp;gt; In that case, mapping instead of joining would be an optimal solution, at least I think so because it seems that in that table there are only two fields (as in a lot of your tables, is that right)?&lt;/P&gt;&lt;P&gt;Are they both unique keys (when you hover over the field in the Table_viewer, does it read either "Perfect key" or "Primary key"?) That is a prerequisite for the mapping to work as expected.&lt;/P&gt;&lt;P&gt;=&amp;gt; If that is the case, mapping will allow you to transfer one field from one table to another without physically joining (or linking) them.&lt;/P&gt;&lt;P&gt;There is a related blog_post on that issue around. Have a read on that.&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 May 2015 12:34:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852022#M1008013</guid>
      <dc:creator>datanibbler</dc:creator>
      <dc:date>2015-05-13T12:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: Problems with data structure</title>
      <link>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852023#M1008014</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi DataNibbler,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sorry for the poor explanation. Seems about right wwhat you are saying. I'll check out the thing you mentioned about mapping and see if that helps.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Christian&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 May 2015 06:51:49 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Problems-with-data-structure/m-p/852023#M1008014</guid>
      <dc:creator />
      <dc:date>2015-05-18T06:51:49Z</dc:date>
    </item>
  </channel>
</rss>

