Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
I have created dasboard in Qlik Sense. I created variables for my measures like example below. I want to use Nprinting based on user values, so I set an employee ID number value in variable part of filter, then I added this filter for user but it does not work. Any help will be really appreciated?
SET v_RESPONSIBLE = 'SEC_ACC_ADMA';
SET v_RESPONSIBLE_PS = 'SEC_ACC_PS';
SET v_OsUser = (upper(SubField(OSUser(),'=',-1);
Measure: count({<SEC_ACC_PS={$(v_OsUser)},TASK_ENTITY={"Proje Ziyareti"}>} [Task_Subject])
Nprinting :
Thanks.
Hi @ElifGuler
I’m not very sure where you are having the problem, if it’s in nprinting or sense app, but you are missing some single quotes in the formula because you are evaluating text and not number
count({<SEC_ACC_PS={'$(v_OsUser)'},TASK_ENTITY={"Proje Ziyareti"}>} [Task_Subject])
Best,
Hi,
The logical error is that your variable does not have expression in it so you cannot use "EVALUATE" checkbox. You just want variable v_OsUser to be set to HTR0410 therefore there is nothing to evaluate! Untick the "evaluate" box and try again.
I also agree that having single quotes is more elegant and should be applied in your set analysis.
I suggest studying how to use particular functions to be sure that correct methods are used - here is a link https://help.qlik.com/en-US/nprinting/May2022/Content/NPrinting/ReportsDevelopment/Static-dynamic-fi...
cheers
Lech
On completely different subject. Is there any reason why you had to do set analysis for user selection instead of just regular section access or filters?
Since some users are managers and they should see also their team employee's data , we could not apply section access or user filter.
That Section access souldnt be a problem if done propperly.
Using section access you can set the managers to see others user data, just add more lines for manager to link with other users data.
Best,
Correct - just like @RafaelBarrios said - section access shouldn't be a problem if planned and done properly
ohh - same would apply for user filters - at the end you are using a filter anyway, right?