<?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: Matching Several IDs in one table in App Development</title>
    <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507493#M36251</link>
    <description>&lt;P&gt;Thank you Juraj - it does seem that separate instances of the HR table is the way to go as I do need access to the full file.&amp;nbsp; This messages was an attempt to understnad what other users would do in similar situations.&amp;nbsp; I doubt I'm the only one that has tried this.&lt;/P&gt;&lt;P&gt;Appreciate your input!&lt;/P&gt;</description>
    <pubDate>Thu, 15 Nov 2018 17:23:04 GMT</pubDate>
    <dc:creator>gfisch13</dc:creator>
    <dc:date>2018-11-15T17:23:04Z</dc:date>
    <item>
      <title>Matching Several IDs in one table</title>
      <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1506572#M36198</link>
      <description>&lt;P&gt;Good Afternoon All,&lt;/P&gt;&lt;P&gt;I'm working with a Purchase Order workflow table that contains a unique ID for the Requester, Preparer, and Approver of the Purchase&amp;nbsp;Order.&amp;nbsp;&amp;nbsp; Each of these unique ID's corresponds to an Active Employee ID number.&amp;nbsp;&amp;nbsp; There are times when these three values are completely different, but there are also situations where 1/3 or 2/3 are the same.&amp;nbsp;&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a separate HR Table that includes these Active Employee ID numbers along with associated names, job titles and departments.&lt;/P&gt;&lt;P&gt;I'm unsure how to relate these records.&amp;nbsp;&amp;nbsp; I can associate one ID with no issue, do I&amp;nbsp;need to have 2 additional instances of the HR table (named differently I'd assume)&amp;nbsp;to associate the other two ids?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;P&gt;George&lt;/P&gt;</description>
      <pubDate>Wed, 14 Nov 2018 18:58:31 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1506572#M36198</guid>
      <dc:creator>gfisch13</dc:creator>
      <dc:date>2018-11-14T18:58:31Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Several IDs in one table</title>
      <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1506641#M36199</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;the question here is whether or not you need to associate the whole HR table, or are you OK with employee name. If employee name is enough, then I'd create a mapping table mapping EmployeeID to Employee Name and map that instead of IDs in the PO table. On the other hand, if you need the whole HR table connected to all three IDs, then you have two options:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;separate identical tables with qualified attributes (this is what you suggest)&lt;/LI&gt;&lt;LI&gt;create a bridge table between PO and HR tables with three attributes: PO_ID, EmployeeID and EmployeeRole (Requester || Preparer || Approver). You can then use EmployeeRole field as a dimension, filter or in set analysis to select respective employee data.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Hope this helps.&lt;/P&gt;&lt;P&gt;Juraj&lt;/P&gt;</description>
      <pubDate>Wed, 14 Nov 2018 20:37:12 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1506641#M36199</guid>
      <dc:creator>juraj_misina</dc:creator>
      <dc:date>2018-11-14T20:37:12Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Several IDs in one table</title>
      <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507493#M36251</link>
      <description>&lt;P&gt;Thank you Juraj - it does seem that separate instances of the HR table is the way to go as I do need access to the full file.&amp;nbsp; This messages was an attempt to understnad what other users would do in similar situations.&amp;nbsp; I doubt I'm the only one that has tried this.&lt;/P&gt;&lt;P&gt;Appreciate your input!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Nov 2018 17:23:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507493#M36251</guid>
      <dc:creator>gfisch13</dc:creator>
      <dc:date>2018-11-15T17:23:04Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Several IDs in one table</title>
      <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507508#M36252</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;have a look at &lt;A title="Link to Canonical Date blog post" href="https://community.qlik.com/t5/Qlik-Design-Blog/Canonical-Date/ba-p/1463578" target="_blank"&gt;Canonical Date&lt;/A&gt;. You can use this approach in your case as well.&lt;/P&gt;&lt;P&gt;Juraj&lt;/P&gt;</description>
      <pubDate>Thu, 15 Nov 2018 17:47:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507508#M36252</guid>
      <dc:creator>juraj_misina</dc:creator>
      <dc:date>2018-11-15T17:47:17Z</dc:date>
    </item>
    <item>
      <title>Re: Matching Several IDs in one table</title>
      <link>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507560#M36256</link>
      <description>&lt;P&gt;Juraj - this is very interesting and I just need some time to evaluate it and apply, I'm a junior user but learn quick.&amp;nbsp; This has possibilities.&amp;nbsp;&amp;nbsp; Thanks again!&lt;/P&gt;</description>
      <pubDate>Thu, 15 Nov 2018 20:11:11 GMT</pubDate>
      <guid>https://community.qlik.com/t5/App-Development/Matching-Several-IDs-in-one-table/m-p/1507560#M36256</guid>
      <dc:creator>gfisch13</dc:creator>
      <dc:date>2018-11-15T20:11:11Z</dc:date>
    </item>
  </channel>
</rss>

