topic Re: OSUser not working on qlik sense / server version June 2017 in App Development

OSUser not working on qlik sense / server version June 2017

joeybird — Tue, 24 Oct 2017 10:42:43 GMT

I have been having trouble using the following code in Qlik , since the new June 2017 upgrade

has there been a amendment on how this code should be used or is there an error with the new server?

here is an example

Count({<UserID = {'$(=SubField(upper(OSUser(), '=', -1)))'}>}distinct([Order_Number]))

I have also for the

for UserID and OSUser I have made sure in the load it looks like the following in the load

Upper(UserID) as UserID

Upper(OSUser) as OSUser

any ideas please team?

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Tue, 24 Oct 2017 11:09:58 GMT

Hi Joanna,

You're missing a parenthesis of the "upper(OSUser()" statement, you have:

Count({<UserID = {'$(=SubField(upper(OSUser(), '=', -1)))'}>}distinct([Order_Number]))

but should be

Count({<UserID = {'$(=SubField(upper(OSUser()), '=', -1)))'}>}distinct([Order_Number]))

Just testes it here with the expression =Subfield(upper(OSUser()),'\',-1) and works fine.

Felipe.

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Tue, 24 Oct 2017 12:42:29 GMT

sorry this did not work

checking the server the username (for computer login is) is a mixture of letters and numbers e.g

aa123456789

I have checked the server and it reads in as lowercase too

so this is as

aa123456789

but in app I have used the upper command so it looks like AA123456789 in the load

so I also tried

Count({<UserID = {'$(=SubField(lower(OSUser()), '=', -1)))'}>}distinct([Order_Number]))

with no joy

any more ideas team please?

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Tue, 24 Oct 2017 12:50:24 GMT

Hi Joanna,

Just try out OSUser() and see the result it gives, i'm assuming the user name doesn have the '=' you're putting in the subfield statement.

Can you share the app?

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 10:00:12 GMT

I cant really share the app sorry

but using OSUSER() has outputted

UserDirectory = Domain; UserId=aa123456789

please help

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Wed, 25 Oct 2017 11:10:10 GMT

Hi Joanna,

It seems the evaluation on the set analysis is probably returning null or some value incompatible with what your trying to compare *UserID". It will need some debbuging to get it right.

Try the following, put the =SubField(lower(OSUser()), '=', -1) expression in a text box and see what it returns and see which values you have for UserID,.

My guess it's that you don't have the user you posted above in your bae, or $ expansion is returning null.

Felipe.

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 11:47:28 GMT

=SubField(lower(OSUser()), '=', -1) returns

aa123456789

I have replaced the set anaylsis with the above and I still get no answer

I tried to remove the $ and I get error in set analysis

please help

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Wed, 25 Oct 2017 11:53:10 GMT

Is there an association between the tables and for the table that has the UserID, does it have the entry (row) with the value UserID = aa123456789 (with the lowercase letters)?

Since I can't see the data, i'm doing guesses to see if it helps.

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 12:06:55 GMT

yes, I have even now in the data load

done lower(OSUSER) as UserId

also changed the UserID to UserId to see if it help with the matching

UserDirectory = Domain; UserId=aa123456789

any more ideas.. how would you remove the $ expansion?

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Wed, 25 Oct 2017 12:11:43 GMT

What I meant was, do you have on the loaded table the value "aa123456789".

Check in the data model or create a simple filter and check if your base has the "aa123456789".

IF not, set analysis wont find the specified user id and can't use it for calculations.

This part you mentioned "UserDirectory = Domain; UserId=aa123456789" is the value from the AD, but somewhere you need to have this value in Qlik so that set analysis can search it.

Final thing is that you might not have a Order_Number associated to this user in your tables, check those too .

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 12:34:52 GMT

yes there is a table with two columns

OSUSER and AccountantName

I have this in the load

lower(OSUSER) as UserId

the UserId aa123456789 has come through as checking with a filter pane, along with the AccountantName e.g Joe Bloggs

and yes there are orders linking to Joe Bloggs

hence why I am thinking its the $ is now causing the issue

I have done a test of Count( {<UserId={'aa123456789'}>} distinct [Order_Number])

and I have records in the kpi

please help

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Wed, 25 Oct 2017 12:55:41 GMT

Joanna,

Might be dumb, but its because of the single quotes your using on the set analysis.

Instead, use

Count( {<UserId={"$(=SubField(lower(UserId), '=', -1))"}>} distinct [Order_Number])

As an e4xpression.

Theres a difference between the two now in this release.

Used the following code:

Which gives me the following

see this as reference: Quotes in Set Analysis

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 12:57:33 GMT

yes! the double quotes! worked and and also too many ) after the - 1 it should only have two of these and not three

amazing team

thank you

Re: OSUser not working on qlik sense / server version June 2017

felipedl — Wed, 25 Oct 2017 12:58:36 GMT

Glad it helped .

Re: OSUser not working on qlik sense / server version June 2017

joeybird — Wed, 25 Oct 2017 12:59:59 GMT

also lowing the case works...with qlik view you had to upper everything as the same with the first releases of qlik sense

thanks again x