<?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 Data Reduction/Section Access - data access/presentation issue in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153167#M376601</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I implemented Section Access so that the salesperson can only see his/her sales.&amp;nbsp; We use SALESNO (Salesperson ID)as the field to reduce access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have sales that are split sometimes up to 4 ways.&amp;nbsp; Data for a sale might look like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" style="border: 1px solid rgb(0, 0, 0); width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;OrderNo&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;SalesNo&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Percent&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Sales $&lt;BR /&gt;&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;Sales Credit&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;1&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;001&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;100&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;1000&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;1000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;001&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;002&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;002&lt;/TD&gt;&lt;TD&gt;25&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;004&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;007&lt;/TD&gt;&lt;TD&gt;25&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Problem&lt;/STRONG&gt;:&amp;nbsp; With Section Access, in the split sales the Salesperson would only see his/her portion of the sale.&amp;nbsp; This is fine if you are analyzing Sales by Salesperson.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What if you are analyzing Customer Sales or Product Sales? The salesperson will only see their percentage contribution to that sale.&amp;nbsp;&amp;nbsp; In this example, we would want sum up the complete sale regardless of salesperson while still restricting access&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 08 Aug 2016 23:44:32 GMT</pubDate>
    <dc:creator />
    <dc:date>2016-08-08T23:44:32Z</dc:date>
    <item>
      <title>Data Reduction/Section Access - data access/presentation issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153167#M376601</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I implemented Section Access so that the salesperson can only see his/her sales.&amp;nbsp; We use SALESNO (Salesperson ID)as the field to reduce access.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We have sales that are split sometimes up to 4 ways.&amp;nbsp; Data for a sale might look like this&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;TABLE border="1" class="jiveBorder" style="border: 1px solid rgb(0, 0, 0); width: 100%;"&gt;&lt;TBODY&gt;&lt;TR&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;OrderNo&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;SalesNo&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Percent&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;&lt;STRONG&gt;Sales $&lt;BR /&gt;&lt;/STRONG&gt;&lt;/TH&gt;&lt;TH style="text-align: center; background-color: #6690bc; color: #ffffff; padding: 2px;" valign="middle"&gt;Sales Credit&lt;/TH&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD style="padding: 2px;"&gt;1&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;001&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;100&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;1000&lt;/TD&gt;&lt;TD style="padding: 2px;"&gt;1000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;001&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;2&lt;/TD&gt;&lt;TD&gt;002&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;002&lt;/TD&gt;&lt;TD&gt;25&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;004&lt;/TD&gt;&lt;TD&gt;50&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;1000&lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;3&lt;/TD&gt;&lt;TD&gt;007&lt;/TD&gt;&lt;TD&gt;25&lt;/TD&gt;&lt;TD&gt;2000&lt;/TD&gt;&lt;TD&gt;500&lt;/TD&gt;&lt;/TR&gt;&lt;/TBODY&gt;&lt;/TABLE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG style="text-decoration: underline;"&gt;Problem&lt;/STRONG&gt;:&amp;nbsp; With Section Access, in the split sales the Salesperson would only see his/her portion of the sale.&amp;nbsp; This is fine if you are analyzing Sales by Salesperson.&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What if you are analyzing Customer Sales or Product Sales? The salesperson will only see their percentage contribution to that sale.&amp;nbsp;&amp;nbsp; In this example, we would want sum up the complete sale regardless of salesperson while still restricting access&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 08 Aug 2016 23:44:32 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153167#M376601</guid>
      <dc:creator />
      <dc:date>2016-08-08T23:44:32Z</dc:date>
    </item>
    <item>
      <title>Re: Data Reduction/Section Access - data access/presentation issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153168#M376602</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cam,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had a similar requirement and it is not easy to deal with.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the end I created a dummy field which is a copy of SalesNo but NOT linked to it so say just a field called 'Access Code'&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then don't use the data reduction option, but use set analysis like:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SalesNo={concat(Access Code,',')}&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(Sorry I don't recall the exact syntax off the top of my head)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its a proper faf, but at least it then allows you to do the kind of comparitors that you want.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Aug 2016 09:28:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153168#M376602</guid>
      <dc:creator>adamdavi3s</dc:creator>
      <dc:date>2016-08-09T09:28:25Z</dc:date>
    </item>
    <item>
      <title>Re: Data Reduction/Section Access - data access/presentation issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153169#M376603</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;STRONG&gt;one way to handle this is , create a separate which is disconnected from the model and use this table for the customer sales analysis ...&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Aug 2016 09:32:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153169#M376603</guid>
      <dc:creator>avinashelite</dc:creator>
      <dc:date>2016-08-09T09:32:17Z</dc:date>
    </item>
    <item>
      <title>Re: Data Reduction/Section Access - data access/presentation issue</title>
      <link>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153170#M376604</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I reworked my data model and made a new table with KEY and SalesNo as SECLINK - this separated from the Percent calculation appears to have done the trick.&amp;nbsp;&amp;nbsp; Not sure why i was overthinking it?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 09 Mar 2017 00:33:02 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Data-Reduction-Section-Access-data-access-presentation-issue/m-p/1153170#M376604</guid>
      <dc:creator />
      <dc:date>2017-03-09T00:33:02Z</dc:date>
    </item>
  </channel>
</rss>

