topic Re: Tab level security issue in QlikView

Tab level security issue

newhere2014 — Thu, 18 Oct 2012 14:26:16 GMT

I want to implement security on Tab level. I searched the forum and found an exmple here http://community.qlik.com/thread/38348

Actually, this method works well. But the issue is I want to use excel sheet to reload the Control table, instead of INLINE load, since we have many records to maintain.After the application is reloaded and distributed through PUBLISHER, I can not open this application from Access Point. Here is the security code I used in this application.

It is urgent to solve this problem. I really appreciate your help.

1. With INLINE load, it works after Publisher

Section Access;

LOAD

ACCESS,

NTNAME

FROM

F:\...\Security.xls

(biff, embedded labels, table is Sheet4$);

Section Application;

Control :

LOAD * INLINE [

NTNAME, Tab

USER1, Y

USER2,

];

2. With excel sheet load, it failed to open a file after Publisher

Section Access;

LOAD

ACCESS,

NTNAME

FROM

F:\...\Security.xls

(biff, embedded labels, table is Sheet4$);

Section Application;

Control :

LOAD NTNAME,

Tab

FROM

F:\...\Security.xls

(biff, embedded labels, table is Sheet4$);

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:01:25 GMT

What's in your spreadsheet? Just USER1 and USER2?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:03:09 GMT

I have 60 users. This is just an example

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:07:46 GMT

But is the access level, ADMIN or USER in there?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:09:43 GMT

yes. In the excel sheet I've other fields. I only pull information I need.

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:11:22 GMT

Why aren't you loading from the spreadhseet in the Section Access part of the script as well as in the Section Application part?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:13:28 GMT

Yes, i did load all information from excel. I'll modify the above example.

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:23:46 GMT

Is it a CAsE issue with the spreadsheet data?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:28:17 GMT

I've tried to make all value and field names UPPER case. The issue is why INLINE load works AFTER PUBLISHER, while Excel load does not. Is it possible the problem is related to PUBLISHER?

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:35:28 GMT

Hence the reason I wanted to check the data being loaded from the spreadsheet was EXACTLY the same as the inline table.

Can publisher access the Excel file OK? Anything in the logs?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:37:18 GMT

How to check the Publisher log?

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 15:41:42 GMT

In the QMC

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 15:45:07 GMT

Could you give me more detail how to check log from QMC? Thanks

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 16:42:51 GMT

Problem solved. Thanks, Jason

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 17:06:52 GMT

What was the problem?

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 17:08:26 GMT

one of the NTNAME caused the problem, not sure why now. After being removed, it works.

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 17:11:21 GMT

Strict Exclusion maybe? Anyway - glad you solved it. Please mark a correct answer to close the thread.

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 17:14:12 GMT

sure. BTW, could you tell me how to find publisher log? thanks

Re: Tab level security issue

Jason_Michaelides — Thu, 18 Oct 2012 17:17:13 GMT

In the QMC, goto Status > Tasks, then expand the tree to find your job and click "Show Task Details" on the top right. Then select Log.

Hope this helps,

Jason

Re: Tab level security issue

newhere2014 — Thu, 18 Oct 2012 17:23:17 GMT

oh, I see. Thank you very much!