Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
joeybird
Creator III
Creator III

OSUser not working on qlik sense / server version June 2017

Hi

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?

14 Replies
joeybird
Creator III
Creator III
Author

hi

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

felipedl
Partner - Specialist III
Partner - Specialist III

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:

Sample.png

Which gives me the following

Sample.png

see this as reference: Quotes in Set Analysis

joeybird
Creator III
Creator III
Author

Hi

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

felipedl
Partner - Specialist III
Partner - Specialist III

Glad it helped .

joeybird
Creator III
Creator III
Author

Hi

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