<?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: IntervalMatch and synthetic key in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357783#M132762</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks a lot!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 19 Jun 2012 13:46:39 GMT</pubDate>
    <dc:creator />
    <dc:date>2012-06-19T13:46:39Z</dc:date>
    <item>
      <title>IntervalMatch and synthetic key</title>
      <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357779#M132758</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 use IntervalMatch function in my script to match discrets values witch buckets (0-10; 11-20...).&lt;/P&gt;&lt;P&gt;That's build a synthetic key all the time. Do you know a way to do the samething without synthetic key (My supervisor isn't agree to have them)?&lt;/P&gt;&lt;P&gt;thanks a lot&lt;/P&gt;&lt;P&gt;Eva&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 14:56:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357779#M132758</guid>
      <dc:creator />
      <dc:date>2012-06-18T14:56:13Z</dc:date>
    </item>
    <item>
      <title>Re: IntervalMatch and synthetic key</title>
      <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357780#M132759</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that the synthetic key is a problem here, but's if that's what would keep you from pass, you could probably join the two tables after the match:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Ranges:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD *, rowno() as RangeID INLINE [&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Rangestart, Rangeend&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;1,10&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;11, 15,&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;16, 20&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Numbers:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;LOAD *, rowno() as NumberID INLINE [&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Test&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;3&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;11&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;15&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;3&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;17&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;];&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;inner join Intervalmatch (Test) LOAD Rangestart, Rangeend resident Ranges;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;join (Ranges) LOAD * Resident Numbers;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;drop table Numbers;&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 17:36:47 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357780#M132759</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2012-06-18T17:36:47Z</dc:date>
    </item>
    <item>
      <title>Re: IntervalMatch and synthetic key</title>
      <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357781#M132760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks a &lt;/P&gt;&lt;P&gt;do you know shy the interval match is better than add a column with ranges inside the Numbers table?&lt;/P&gt;&lt;P&gt;with a if(value &amp;lt;0, 'under 0'&lt;STRONG&gt;,&lt;/STRONG&gt;if(value &amp;gt;=0 and value &amp;lt;=10, '0 - 10',...))&lt;/P&gt;&lt;P&gt;Is it optimization reason?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 18 Jun 2012 20:54:37 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357781#M132760</guid>
      <dc:creator />
      <dc:date>2012-06-18T20:54:37Z</dc:date>
    </item>
    <item>
      <title>Re: IntervalMatch and synthetic key</title>
      <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357782#M132761</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well, if it's just to classify some numbers into few well defined buckets, I probably won't use interval match at all (but some if() statements like you said, class() function, mapping table ...)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I think interval match is really powerful if you're buckets / ranges are defined in another table, there are a lot of buckets and you may need to take care of other key fields to select the right bucket (look into the extended version of the interval match for that).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;As always, there might not be the optimal solution for all cases, so it all depends on your setting and needs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2012 13:34:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357782#M132761</guid>
      <dc:creator>swuehl</dc:creator>
      <dc:date>2012-06-19T13:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: IntervalMatch and synthetic key</title>
      <link>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357783#M132762</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks a lot!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 19 Jun 2012 13:46:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/IntervalMatch-and-synthetic-key/m-p/357783#M132762</guid>
      <dc:creator />
      <dc:date>2012-06-19T13:46:39Z</dc:date>
    </item>
  </channel>
</rss>

