<?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 Datamodelling and SA security in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Datamodelling-and-SA-security/m-p/1601677#M444393</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've got a app that several bosses is using, showing all kinds of KPIs etc.&lt;BR /&gt;I'm&amp;nbsp; using SA so that each boss only sees the economics and KPIs&amp;nbsp;related to their own department.&lt;BR /&gt;Now I got a question if I can tighten up the security so that each boss only sees specific accounts, still within their department. This is only used when they is looking at the economic-part of the app. Fine, I did a synthetic key with department and accounts and a table with all combinations and it worked nicely in the transform-stage. But I had forgot one small detail when I moved over to the load-stage, I still need the department in the fact-table due all the KPIs.&lt;/P&gt;&lt;P&gt;Anyone got a idea how I can work around this?&lt;BR /&gt;I've made a simple demo to show what I mean.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Demo showing the synthetic table" style="width: 436px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15322iDD7A8E93C2421C0E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Skärmklipp.PNG" alt="Demo showing the synthetic table" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Demo showing the synthetic table&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;</description>
    <pubDate>Sat, 16 Nov 2024 03:01:39 GMT</pubDate>
    <dc:creator>t_hylander</dc:creator>
    <dc:date>2024-11-16T03:01:39Z</dc:date>
    <item>
      <title>Datamodelling and SA security</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodelling-and-SA-security/m-p/1601677#M444393</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I've got a app that several bosses is using, showing all kinds of KPIs etc.&lt;BR /&gt;I'm&amp;nbsp; using SA so that each boss only sees the economics and KPIs&amp;nbsp;related to their own department.&lt;BR /&gt;Now I got a question if I can tighten up the security so that each boss only sees specific accounts, still within their department. This is only used when they is looking at the economic-part of the app. Fine, I did a synthetic key with department and accounts and a table with all combinations and it worked nicely in the transform-stage. But I had forgot one small detail when I moved over to the load-stage, I still need the department in the fact-table due all the KPIs.&lt;/P&gt;&lt;P&gt;Anyone got a idea how I can work around this?&lt;BR /&gt;I've made a simple demo to show what I mean.&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Demo showing the synthetic table" style="width: 436px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/15322iDD7A8E93C2421C0E/image-size/large?v=v2&amp;amp;px=999" role="button" title="Skärmklipp.PNG" alt="Demo showing the synthetic table" /&gt;&lt;span class="lia-inline-image-caption" onclick="event.preventDefault();"&gt;Demo showing the synthetic table&lt;/span&gt;&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 16 Nov 2024 03:01:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodelling-and-SA-security/m-p/1601677#M444393</guid>
      <dc:creator>t_hylander</dc:creator>
      <dc:date>2024-11-16T03:01:39Z</dc:date>
    </item>
    <item>
      <title>Re: Datamodelling and SA security</title>
      <link>https://community.qlik.com/t5/QlikView/Datamodelling-and-SA-security/m-p/1610258#M445069</link>
      <description>&lt;P&gt;Check out the following Design Blog posts:&lt;/P&gt;
&lt;P&gt;Section Access Primer:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/A-Primer-on-Section-Access/ba-p/1465766&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;There are some other links at the bottom of that post related to dynamic data reduction you will want to review as well, just FYI.&lt;/P&gt;
&lt;P&gt;Synthetic Keys:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Synthetic-Keys/ba-p/1472634" target="_blank"&gt;https://community.qlik.com/t5/Qlik-Design-Blog/Synthetic-Keys/ba-p/1472634&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Hopefully these will help you get things sorted out the way you want.&lt;/P&gt;
&lt;P&gt;Regards,&lt;BR /&gt;Brett&lt;/P&gt;</description>
      <pubDate>Wed, 07 Aug 2019 12:26:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Datamodelling-and-SA-security/m-p/1610258#M445069</guid>
      <dc:creator>Brett_Bleess</dc:creator>
      <dc:date>2019-08-07T12:26:58Z</dc:date>
    </item>
  </channel>
</rss>

