<?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: Help in Qlik Sense Section Access in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292411#M9112</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IMHO, you'll need to add the project and community keys to the &lt;SPAN style="text-decoration: line-through;"&gt;household&lt;/SPAN&gt; (Edit. Member) table (using joins or applymaps), which is the one that unifies both entities... so you have a table with all the possible or valid household, project and community combinations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have that, you can rename the filelds so you don't get synthetic keys or create a new field that combines the project and community fields into one by concatenating them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then its up to you if you want to use the concatenated field or both renamed fields as the Section Access filters.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 17 Feb 2017 00:40:43 GMT</pubDate>
    <dc:creator>Carlos_Reyes</dc:creator>
    <dc:date>2017-02-17T00:40:43Z</dc:date>
    <item>
      <title>Help in Qlik Sense Section Access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292410#M9111</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;I'm working on a Qlik Sense dashboard and I got the following schema:&lt;/P&gt;&lt;P&gt;&lt;IMG alt="schema.png" class="jive-image image-1" src="https://community.qlik.com/legacyfs/online/153421_schema.png" style="height: 271px; width: 620px;" /&gt;&lt;/P&gt;&lt;P&gt;there are two tables Community and Projects (highlighted) in red&lt;/P&gt;&lt;P&gt;Users who will access the dashboard need to have permissions on communities and projects i.e. some users may see community C1 and related projects P1 and P2&lt;/P&gt;&lt;P&gt;Other users may see all communities and thus all projects&lt;/P&gt;&lt;P&gt;Other users may see communities C1, and all related projects and community C2 and project P3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help in the section access syntax here as reduction is to be made on 2 fields in separate tables&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Feb 2017 18:59:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292410#M9111</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2017-02-16T18:59:58Z</dc:date>
    </item>
    <item>
      <title>Re: Help in Qlik Sense Section Access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292411#M9112</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;IMHO, you'll need to add the project and community keys to the &lt;SPAN style="text-decoration: line-through;"&gt;household&lt;/SPAN&gt; (Edit. Member) table (using joins or applymaps), which is the one that unifies both entities... so you have a table with all the possible or valid household, project and community combinations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you have that, you can rename the filelds so you don't get synthetic keys or create a new field that combines the project and community fields into one by concatenating them.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then its up to you if you want to use the concatenated field or both renamed fields as the Section Access filters.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 00:40:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292411#M9112</guid>
      <dc:creator>Carlos_Reyes</dc:creator>
      <dc:date>2017-02-17T00:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Help in Qlik Sense Section Access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292412#M9113</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;no I think I should add community to project_household_assoc table&lt;/P&gt;&lt;P&gt;not the member because households reside in communities and households are assigned to projects&lt;/P&gt;&lt;P&gt;so the household key would be field containing both the household_id and community_id&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 07:50:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292412#M9113</guid>
      <dc:creator>ali_hijazi</dc:creator>
      <dc:date>2017-02-17T07:50:43Z</dc:date>
    </item>
    <item>
      <title>Re: Help in Qlik Sense Section Access</title>
      <link>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292413#M9114</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Knowing that makes perfect sense to join both in the household table.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 17 Feb 2017 14:04:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Help-in-Qlik-Sense-Section-Access/m-p/1292413#M9114</guid>
      <dc:creator>Carlos_Reyes</dc:creator>
      <dc:date>2017-02-17T14:04:29Z</dc:date>
    </item>
  </channel>
</rss>

