<?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: Detailed dimension or total based on user in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1769227#M454495</link>
    <description>&lt;P&gt;at the end of the day, what you really need is just association between your user's IDs and the specific rows you want them to access.&amp;nbsp; now if you have a fact with concatenated detail and aggregations there should be a way to associate the IDs to the rows you want them to have:&lt;BR /&gt;&lt;BR /&gt;USERID1 - Detail1&lt;BR /&gt;USERID2 - Detail2&lt;BR /&gt;USERID3 - Detail3&lt;BR /&gt;USERID1 - AGGR OF Detail1 and Detail2&lt;BR /&gt;USERID2 - AGGR OF&amp;nbsp;Detail1 and Detail2&lt;BR /&gt;USERID3 - AGGR of Detail3&lt;BR /&gt;&lt;BR /&gt;this means each user can only see their individual details, but Users 1 and 2 share the same AGGR and user3 has exclusive on AGGR3.&amp;nbsp;&lt;/P&gt;&lt;P&gt;this will not work if your AGGR is in a separate table and your section access is linked only to the detail table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;it will work if your detail and AGGR are&amp;nbsp; concatenated into one fact table or the detail and aggr tables are linked and your section access is on the link table.&lt;/P&gt;</description>
    <pubDate>Thu, 17 Dec 2020 11:47:35 GMT</pubDate>
    <dc:creator>edwin</dc:creator>
    <dc:date>2020-12-17T11:47:35Z</dc:date>
    <item>
      <title>Detailed dimension or total based on user</title>
      <link>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1767586#M454387</link>
      <description>&lt;P&gt;In my authorisation-table some people are authorized for the same dimension.&lt;/P&gt;&lt;P&gt;I want to show detailed dimension based on username, otherwise the dimensions should be presented with the text "Total not authorized".&lt;/P&gt;&lt;P&gt;In included qvw details are shown for the selected user, however the line "Total not authorized" include some values which are in the detailed information too, because an other user is authorized to some same dimensions. So the sum of the rules is not equal to the grand total.&lt;/P&gt;&lt;P&gt;How to prevent that the the detailed records are not included in the "Total not authorized" line&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 10 Dec 2020 10:03:04 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1767586#M454387</guid>
      <dc:creator>curiousfellow</dc:creator>
      <dc:date>2020-12-10T10:03:04Z</dc:date>
    </item>
    <item>
      <title>Re: Detailed dimension or total based on user</title>
      <link>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1768727#M454469</link>
      <description>&lt;P&gt;Look at Henric's blog on section access re detailed and aggregated data - which sounds like what you need&lt;BR /&gt;&lt;BR /&gt;&lt;A href="https://community.qlik.com/t5/Qlik-Design-Blog/Data-Reduction-Yes-but-How/ba-p/1463051" target="_blank" rel="noopener"&gt;Data Reduction – Yes, but How? - Qlik Community - 1463051&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 15 Dec 2020 20:10:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1768727#M454469</guid>
      <dc:creator>edwin</dc:creator>
      <dc:date>2020-12-15T20:10:55Z</dc:date>
    </item>
    <item>
      <title>Re: Detailed dimension or total based on user</title>
      <link>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1769171#M454494</link>
      <description>&lt;P&gt;Allthough Henric advices to use two seperate applications it seems to be possible to use &lt;STRONG&gt;Aggregation-level access&lt;/STRONG&gt;&amp;nbsp;.&lt;/P&gt;&lt;P&gt;I have to investigate how to use that, was not aware of that possiblility.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 09:01:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1769171#M454494</guid>
      <dc:creator>curiousfellow</dc:creator>
      <dc:date>2020-12-17T09:01:08Z</dc:date>
    </item>
    <item>
      <title>Re: Detailed dimension or total based on user</title>
      <link>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1769227#M454495</link>
      <description>&lt;P&gt;at the end of the day, what you really need is just association between your user's IDs and the specific rows you want them to access.&amp;nbsp; now if you have a fact with concatenated detail and aggregations there should be a way to associate the IDs to the rows you want them to have:&lt;BR /&gt;&lt;BR /&gt;USERID1 - Detail1&lt;BR /&gt;USERID2 - Detail2&lt;BR /&gt;USERID3 - Detail3&lt;BR /&gt;USERID1 - AGGR OF Detail1 and Detail2&lt;BR /&gt;USERID2 - AGGR OF&amp;nbsp;Detail1 and Detail2&lt;BR /&gt;USERID3 - AGGR of Detail3&lt;BR /&gt;&lt;BR /&gt;this means each user can only see their individual details, but Users 1 and 2 share the same AGGR and user3 has exclusive on AGGR3.&amp;nbsp;&lt;/P&gt;&lt;P&gt;this will not work if your AGGR is in a separate table and your section access is linked only to the detail table.&amp;nbsp;&lt;/P&gt;&lt;P&gt;it will work if your detail and AGGR are&amp;nbsp; concatenated into one fact table or the detail and aggr tables are linked and your section access is on the link table.&lt;/P&gt;</description>
      <pubDate>Thu, 17 Dec 2020 11:47:35 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Detailed-dimension-or-total-based-on-user/m-p/1769227#M454495</guid>
      <dc:creator>edwin</dc:creator>
      <dc:date>2020-12-17T11:47:35Z</dc:date>
    </item>
  </channel>
</rss>

