<?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: Multiply Occurring Fields in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437918#M163255</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why do u want join here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qlikview will automaticaly associate it and when u will select Z1 then u will be able to see the secondary as well...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 13 Mar 2013 16:49:50 GMT</pubDate>
    <dc:creator>sushil353</dc:creator>
    <dc:date>2013-03-13T16:49:50Z</dc:date>
    <item>
      <title>Multiply Occurring Fields</title>
      <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437917#M163254</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Community,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am running into an issue where the table I want to join to the "Fact table" has multiply occuring fields (acct #s in this case). This is causeing my calculations to be skewed (Sum (LOS), Sum(Total Charges) etc.) So for example my two tables would looks like this:&lt;/P&gt;&lt;P&gt;FACT_TABLE:&lt;/P&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="jiveBorder" height="130" style="width: 295px; border: 1px solid #000000; height: 112px;" width="293"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;&lt;STRONG style="color: #ffffff; text-align: -webkit-center; background-color: #6690bc;"&gt;Acct #&lt;/STRONG&gt;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Principal Diagnosis&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Cases&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Length of Stay&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Total Charges&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX5&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;5 days&lt;/TD&gt;&lt;TD&gt;$10000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z2&lt;/TD&gt;&lt;TD&gt;DX7&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;10 days&lt;/TD&gt;&lt;TD&gt;$20000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z3&lt;/TD&gt;&lt;TD&gt;DX4&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;20 days&lt;/TD&gt;&lt;TD&gt;$40000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z4&lt;/TD&gt;&lt;TD&gt;DX3&lt;/TD&gt;&lt;TD&gt;1&lt;/TD&gt;&lt;TD&gt;2 days&lt;/TD&gt;&lt;TD&gt;$5000&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SEC_DIAG:&lt;/P&gt;&lt;TABLE border="1" cellpadding="3" cellspacing="0" class="jiveBorder" height="149" style="width: 273px; border: 1px solid #000000; height: 151px;" width="271"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Acct #&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;TH align="center" style="background-color: #6690bc;" valign="middle"&gt;&lt;SPAN style="color: #ffffff;"&gt;&lt;STRONG&gt;Secondary Diagnosis&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX15&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX23&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX6&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z2&lt;/TD&gt;&lt;TD&gt;DX2&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Z2&lt;/TD&gt;&lt;TD&gt;DX9&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would have orginally liked to do a join so that for Acct# Z1 you can see the Principal Diagnosis and the 3 related Secondary Diagnosis while Cases (1), LOS (5 days), and Total Charges ($10000) remain static. Obviously with a join I am going to see all these fields populated 3 times and therefore my Cases, LOS, and Total Charges become skewed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there a work around for this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help or suggestions is appreciated,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EK &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 16:36:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437917#M163254</guid>
      <dc:creator />
      <dc:date>2013-03-13T16:36:08Z</dc:date>
    </item>
    <item>
      <title>Re: Multiply Occurring Fields</title>
      <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437918#M163255</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why do u want join here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Qlikview will automaticaly associate it and when u will select Z1 then u will be able to see the secondary as well...&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 16:49:50 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437918#M163255</guid>
      <dc:creator>sushil353</dc:creator>
      <dc:date>2013-03-13T16:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Multiply Occurring Fields</title>
      <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437919#M163256</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Right, even without saying join it will connect the two tables in that same fashion (excuse my use of join). it will look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" width="512"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD height="20" width="63"&gt;Acct#&lt;/TD&gt;&lt;TD width="124"&gt;Principal Diagnosis&lt;/TD&gt;&lt;TD width="95"&gt;Secondary Diagnosis&lt;/TD&gt;&lt;TD width="71"&gt;Cases&lt;/TD&gt;&lt;TD width="95"&gt;Length of Stay&lt;/TD&gt;&lt;TD width="64"&gt;Total Charges&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX5&lt;/TD&gt;&lt;TD&gt;DX15&lt;/TD&gt;&lt;TD align="right"&gt;1&lt;/TD&gt;&lt;TD&gt;5 days&lt;/TD&gt;&lt;TD align="right" class="xl63"&gt;$10,000 &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX5&lt;/TD&gt;&lt;TD&gt;DX23&lt;/TD&gt;&lt;TD align="right"&gt;1&lt;/TD&gt;&lt;TD&gt;5 days&lt;/TD&gt;&lt;TD align="right" class="xl63"&gt;$10,000 &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;Z1&lt;/TD&gt;&lt;TD&gt;DX5&lt;/TD&gt;&lt;TD&gt;DX6&lt;/TD&gt;&lt;TD align="right"&gt;1&lt;/TD&gt;&lt;TD&gt;5 days&lt;/TD&gt;&lt;TD align="right" class="xl63"&gt;$10,000 &lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then as I enter in my formulas Sum(LOS)=15 days. This is incorrect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How I would like it to "see" the data is like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="0" cellpadding="0" cellspacing="0" width="512"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TD height="20" width="63"&gt;Acct#&lt;/TD&gt;&lt;TD width="124"&gt;Principal Diagnosis&lt;/TD&gt;&lt;TD width="95"&gt;Secondary Diagnosis&lt;/TD&gt;&lt;TD width="71"&gt;Cases&lt;/TD&gt;&lt;TD width="95"&gt;Length of Stay&lt;/TD&gt;&lt;TD width="64"&gt;Total Charges&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD class="xl65" height="60" rowspan="3"&gt;Z1&lt;/TD&gt;&lt;TD class="xl65" rowspan="3"&gt;DX5&lt;/TD&gt;&lt;TD&gt;DX15&lt;/TD&gt;&lt;TD class="xl65" rowspan="3"&gt;1&lt;/TD&gt;&lt;TD class="xl65" rowspan="3"&gt;5 days&lt;/TD&gt;&lt;TD class="xl66" rowspan="3"&gt;$10,000 &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;DX23&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD height="20"&gt;DX6&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you can see wihat Secondary Diagnosis are associated with the account but it does not skew my financial fields.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 17:02:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437919#M163256</guid>
      <dc:creator />
      <dc:date>2013-03-13T17:02:08Z</dc:date>
    </item>
    <item>
      <title>Re: Multiply Occurring Fields</title>
      <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437920#M163257</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Check the attached hope it helps&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 13 Mar 2013 17:26:53 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437920#M163257</guid>
      <dc:creator>CELAMBARASAN</dc:creator>
      <dc:date>2013-03-13T17:26:53Z</dc:date>
    </item>
    <item>
      <title>Re: Multiply Occurring Fields</title>
      <link>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437921#M163258</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Celam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The solution did work, however, the concatenated field looks poor and creates useless composite keys. Is there a way to clean this up so a list box would only show single codes? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Such as:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DX1&lt;/P&gt;&lt;P&gt;DX2&lt;/P&gt;&lt;P&gt;DX3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DX1,DX2,DX3&lt;/P&gt;&lt;P&gt;DX4,DX5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I understand this may be changing the solution entirely, however, this way I can create a crosstable that will make the correct associations. Right now it links everything together because of all the concatenated strings.&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;EK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 29 Mar 2013 14:34:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Multiply-Occurring-Fields/m-p/437921#M163258</guid>
      <dc:creator />
      <dc:date>2013-03-29T14:34:07Z</dc:date>
    </item>
  </channel>
</rss>

