Does admin(user) rights is required in document with section access

[#1]

Hi All,

I don't have the admin user in my section access part. As per the document it says that admin user have the authority to restrict edit script,reload,save,etc options for the non admin user. But i admin user is not there in my document. Is there is any way to reduce restrict the user from accessing edit script,reload,save,etc options. Is it must that all the document with section access must have the admin user to restrict the non admin user? As currently we don't want the admin rights in our document.

Also let me know is it necessary that user name should only be 'admin' for the admin user. Can't it be with different name. Something like vadmin or administrator???

Hope some one will let me know the best possible way.

[#2]

Hi Rikab,

Can you try sending the QVD files you have saved through the script? Today I tried to attach a file and it was allowing to attach, please try from your side too.

Thanks,

Sajeevan

[#3]

Hi

I removed "SecurityTable" from my script but still it is not working! Check is there is any other solution for this problem. I will also try from my side also!

Section Access;

LOAD * INLINE [
ACCESS, USERID, PASSWORD, ACCOUNT CODE, MFAC CODE // Removed the bracket as it was not working with brackets
ADMIN, Rikab, Rikab2010, *, *
];

LOAD

'USER' as [ACCESS], userid as USERID, upper(password) as PASSWORD, account as [account code], mfaccode as [mfaccode]
RESIDENT items;

Section Application;

star is *;

load account as [ACCOUNT CODE], account resident items;

load mfaccode as [MFAC CODE], mfaccode resident items;

Thanks and Regards,

Rikab

[#4]

Here I just want to add some points:

I recomend to load ADMIN user and password details using INLINE.If we load it from external file maintanance will increase.

ADMIN User required 'To edit the hidden scripts" and sometime to validate security data in the dashboards

[#5]

Hi Ramchander!

Thanks for your reply! I have replied to your idea but i am not too sure whether my thought is right or wrong. Please check and get back to me if i am wrong somewhere.

I recomend to load ADMIN user and password details using INLINE.If we load it from external file maintanance will increase. --> If i load using INLINE don't you think that i every time when the password has been changed or new user is added as admin i need to do manually using INLINE. If it is LOAD it will be dynamically updated. As per me maintanence will increase if we use INLINE and will

ADMIN User required 'To edit the hidden scripts" and sometime to validate security data in the dashboards --> I am not able to understand why you have added this point. Can you please explain!

Thanks and Regards,

Rikab

[#6]

Hi Rikab,

I am successful in coming up with the solution. Basically some of your original variables needed a renaming. Find attached what I have done. The username to open the QVW file is "Rikab" and the password is "Rikab2010".

What I have done is like below

Step 1:

I used your original QVW file as a binary load to another QVW file. Renamed some variables and removed the synthetic connections by renaming variables. Then I stored the new tables to a QVD file.

Step 2:

I created a new QVW file (attached) and loaded the data from QVD files. Added your orinal sheets and inline loading tables. Setup the user level access etc.

If you go through the QVW file script you can understand what I have done. The user linking variables must always be in CAPITAL letters.

Hope the solution is good. Let me know your views and what you understood.

Best Regards,

Sajeevan

[#7]

Hi Sajeevan!

I have done basic level of testing before i go in depth. When i login as admin(useris:rikab and password: rikab2010) it works but when i login as user(userid:0010012021 and password:c2info99) it is not working and the same has been working earlier. Rest of the things i will check and will let you know my view.

Thanks and Regards,

Rikab

[#8]

Hi,

To cut down on house keeping I load the section access data from a spreadsheet, secured by windows security. It means you can quickly add users and set up data reduction very quickly without script changes. You only need a reload.

If you were to do this I would recommend you use xls and not xlsx ie excel 2003 compatible.....I have seen some strange behaviour with xlsx files in relation to security which Qliktech could not explain.

Hope this is of help,

Regards,

Neil

[#9]

Hi Sajeevan!

It was a good effort unfortunately it is not working. Can you please script that you have wrote in items and sales table. I want to look into it may be i can get to know something from that. Do reply!

Thanks and Regards,

Rikab

[#10]

Hi Rikab,

All the scripts are there in the QVW file I supplied to you. I am also testing from my side to see why it is not working.

Thanks,

Sajeevan

[#11]

Hi Sajeevan!

Other than the below one i am not able to see any other script for items and sales. Is this is the one you are talking about?

/*
// This step is to be done in your original QVW file

ItemsData:
load account as ACCOUNT, account&itemcode as account_itemcode, pack,
mfaccode as MFACCODE, itemname, userid as Item_userid, password as Item_Password,
MRP, recentitem, schemes, mfacname, contentname, contentname1 resident items;

SalesData:
load account&itemcode as account_itemcode, Month, Year, Date,
PurQty, PurSch, PurValue, SalQty, SalSch, SalValue, RtnQty, RtnSch, RtnValue,
StkQty, StkValue resident sales;

drop table sales;
drop table items;

Store * from ItemsData into C:\Sajeevan\QlikView\2010\items.qvd;
Store * from SalesData into C:\Sajeevan\QlikView\2010\sales.qvd;

*/