<?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: Restriction to data in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475654#M1301416</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looking at the issue again, I guess the question here is whether we could have multiple values added to a given field/column when loading inline tables. This is not a security or section access issue I think.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we could do this inline table in qlikview, I guess the section access can work automatically.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 04 Nov 2013 15:57:55 GMT</pubDate>
    <dc:creator />
    <dc:date>2013-11-04T15:57:55Z</dc:date>
    <item>
      <title>Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475650#M1301412</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm trying ot restrict data to users based on the Area they belong to.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One user can belong to multiple areas. With below code, could I add multiple areas either in the security code or in a flat file that can be loaded to give users access to multiple areas.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In below example, User1 currently has access to Area1 and User 2 to Area2.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm looking for a way where User1 can have access to Area1 and Area3.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I don't think comma separated areas will work here.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACCESS:&lt;BR /&gt;LOAD * Inline [&lt;BR /&gt;ACCESS,NTNAME,USER_GROUP, AREA&lt;BR /&gt;ADMIN,Domain\User1,QV_XOPS 16 COO_METRICS, Area1&lt;BR /&gt;ADMIN,Domain\User2,QV_XOPS 16 COO_METRICS, Area2&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;P&gt;Section Access;&lt;BR /&gt;Load&lt;BR /&gt;ACCESS,&lt;BR /&gt;UPPER(NTNAME) AS NTNAME&lt;BR /&gt;RESIDENT ACCESS;&lt;BR /&gt;Section Application;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475650#M1301412</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
    <item>
      <title>Re: Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475651#M1301413</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;You could add a second line for User1:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;ACCESS:&lt;BR /&gt;LOAD * Inline [&lt;BR /&gt;ACCESS,NTNAME,USER_GROUP, AREA&lt;BR /&gt;ADMIN,Domain\User1,QV_XOPS 16 COO_METRICS, Area1&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;&lt;SPAN style="color: #3d3d3d; font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif;"&gt;&lt;STRONG&gt;ADMIN,Domain\User1,QV_XOPS 16 COO_METRICS, Area&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;STRONG&gt;3&lt;/STRONG&gt;&lt;BR /&gt;ADMIN,Domain\User2,QV_XOPS 16 COO_METRICS, Area2&lt;/P&gt;&lt;P style="font-family: 'Helvetica Neue', Helvetica, Arial, 'Lucida Grande', sans-serif; color: #3d3d3d;"&gt;];&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;Hope this helps!&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 15:30:58 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475651#M1301413</guid>
      <dc:creator>salto</dc:creator>
      <dc:date>2013-11-04T15:30:58Z</dc:date>
    </item>
    <item>
      <title>Re: Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475652#M1301414</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would like to avoid adding extra lines for each user as the list can be very long.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was trying to find a way where one line is added to each user and then multiple areas are added to this user on the same line either through a comma separate values or an excel spreadsheet.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 15:40:07 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475652#M1301414</guid>
      <dc:creator />
      <dc:date>2013-11-04T15:40:07Z</dc:date>
    </item>
    <item>
      <title>Re: Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475653#M1301415</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have faced that problem before... and always added an extra line to the access section. At the end of the day, what you get is a list much longer than desrired.&lt;/P&gt;&lt;P&gt;I manage it via Excel sheets. As far as I know, there is no other way to handle this. It would be a great improevement for next versions of Qlik if this feature was included.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 15:55:45 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475653#M1301415</guid>
      <dc:creator>salto</dc:creator>
      <dc:date>2013-11-04T15:55:45Z</dc:date>
    </item>
    <item>
      <title>Re: Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475654#M1301416</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Looking at the issue again, I guess the question here is whether we could have multiple values added to a given field/column when loading inline tables. This is not a security or section access issue I think.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If we could do this inline table in qlikview, I guess the section access can work automatically.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 04 Nov 2013 15:57:55 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475654#M1301416</guid>
      <dc:creator />
      <dc:date>2013-11-04T15:57:55Z</dc:date>
    </item>
    <item>
      <title>Re: Restriction to data</title>
      <link>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475655#M1301417</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Why don't you use pipe as separator instead of comma?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;load * inline [&lt;/P&gt;&lt;P&gt;field, field 2&lt;/P&gt;&lt;P&gt;a, one|two|three&lt;/P&gt;&lt;P&gt;b, four|five|six&lt;/P&gt;&lt;P&gt;];&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You could use that pipe separated values field to filter your records with Section Access. Just make sure the data model is designed for that kind of values.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 12 Nov 2013 18:57:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Restriction-to-data/m-p/475655#M1301417</guid>
      <dc:creator>Carlos_Reyes</dc:creator>
      <dc:date>2013-11-12T18:57:39Z</dc:date>
    </item>
  </channel>
</rss>

