Support sheet for admins - how to see all users?

[#1]

Hi,

I have a working section access.

I would like to have a support sheet that will be reachable on the Access Point with a separate Bookmark. My question is now, how can I create the table in the data model, with the current implementation the NTNAME gets reduced to only show my own user. But I would like to click on any user's name to see what he is able to see when logged in.

Is that possible?

Thanks.

[marcus_sommer]

Bei mir sieht das so aus. Am AUTHKEY hängt die Section Access Tabelle und am MATCHKEY die zusätzlich parallel geladene und damit sichtbare Autorisierung der User gegenüber dem Datenmodell. Wenn Du diese Tabelle in eine Tabellenbox packst, siehst Du die definierten Zugriffe.

i

- Marcus

[#3]

I found out that the problem comes from this piece of code:

     //Adding 'VIEW ALL' users and concrete PARTY_IDs

     concatenate (Access_TMP)

     LOAD

       'USER' as ACCESS,

       NTNAME as NTNAME,

       if(PARTY_ID_all = 1, 'ALL', PARTY_ID) as PARTY_AUTONUM,

       if(PARTY_ID_all = 1, 'ALL', 'PLACEHOLDER') as TERRITORY_AUTONUM

     FROM [..\InputData\99_REF\ACCESS_TABLE_PARTY_bigger_model.xlsx]

     (ooxml, embedded labels, table is Tabelle1)

     where NTNAME<>'*';

If I use my model and load the smaller Excel input, it works. If I use the big QVD files, The admin cannot see the user to territory relationship. Still need to figure out what makes the difference.

[marcus_sommer]

You will need to load all your matching-values from this qvd and compare and check them against the values from your excel. Are there any abnormalities? This could be quite difficult - maybe you used at first some where-filter on the qvd-load to minimze the amount of values which are to check.

I have had last week a similar case with section access which won't matched with the section application area because in this structure data was a special char - chr(8203) - which you couldn't see and which won't be removed from trim(). I have it then removed with purgechar().

But first you need to find it. For this you could use something like:

ord(mid(YourValue, 1, 1))

- Marcus

[#5]

Thanks, good hints.

When I load the same data from the QVD that I  load from the Excel file, it works. As soon as I load more data from the QVD, the error happens.

I also tried to analyze the data with ord() and right(), still didn't find the issue. Seems I have to dig deeper

[#6]

I'm one step closer to the solution. There is a certain user that causes the trouble. Loading him in the section access and the problem occurs, keeping him out with a where clause leads to a successful application.

Problem is, that I don't know what the difference is between him and the rest,,,

[marcus_sommer]

Maybe there are some special chars into that user. I would try to check the length and each single char to detect any abnormalities. Maybe it's related to: Search - But what shall you find?

- Marcus

[#8]

Thanks for your patience to still look into this thread 😉

I checked the user's data, but I cannot find anything that looks strange.

What I've done in the meanwhile: Generally I'm reducing two fields, which, as they do not correlate, is not a problem. I found out that if I do not load that specific user's section access for PARTY_AUTONUM, everythings works fine. TERRITORY_AUTONUM load does not cause trouble.

So I changed my load, to only load certain PARTY_AUTONUMs and see what happens. This is a numeric fields up to 8 digits by the way:

     concatenate (Access_TMP)

     LOAD

       'USER' as ACCESS,

       NTNAME as NTNAME,

       PARTY_ID as PARTY_AUTONUM,

       'PLACEHOLDER' as TERRITORY_AUTONUM

       FROM ..\QVD\Access_Table_Party_Debug.qvd (qvd)

     where NTNAME='user.name@company.com' and wildmatch(PARTY_ID, '10*', '11*');

Loading this with only '10*' or with '11*' in the wildmatch will work. As soon as I load both, the problems with the visibility of TERRITORY_NUM appear again.

[marcus_sommer · Accepted solution]

It's not clear what's going wrong in this case and the following ideas are only trial and error:

- bug in QlikView --> upgrade to a newer version

- app is corrupt --> create a new one

- username contained a Key-Word/Key-Sign like CALL or $ and  qv tried to interpret it not as a simple text --> text(NTNAME)

- problems with blanks or wildcards or statements like STAR is *;

Maybe you could find here some more hints: Section Access.

If this all don't worked you should rather build a simplified datamodel from this case and make a request by the qlikview support.

- Marcus

[#10]

Ok thanks Marcus,

As I don't know how long further research / trial&error will take, I'll mark your last post as Correct Answer.

I'll give an update once I found the solution.

Thanks a lot & have a nice weekend

Jens