topic Re: Best practice design pattern in QlikView

Best practice design pattern

arixooo123 — Tue, 23 May 2017 07:24:16 GMT

Hey Guys,

I am developing qlik sense by QVD approach, I stored the qvds by a qvd generator app, created the model in another app, then added section access in a separate app.

my question is how to follow the development with best practice approaches?

Should I develop the dashboards in a separate app too?

I also have another question, I imported the user list from a user table, each user has a key that defines what rows in fact table he can see.

Should I use NTNAME or USERID for usernames?

Re: Best practice design pattern

sibusiso90 — Tue, 23 May 2017 07:30:33 GMT

Hi AR eiuiew

Best Practise is to have an app which does all your transformation, then you have the last app that will only have the front end and will not have any transformation. They are usually three Tiers, were tier 1 just pulls the data and stores into qvds then tier 2 will do all the transformations then tier 3 will only have frontend. On Tier 1 and Tier 2 you will drop all the tables once they are stored into QVDs so that maintenance is quick and easy.

Re: Best practice design pattern

arixooo123 — Tue, 23 May 2017 07:35:40 GMT

Thanks Sibusiso,

Any comment on the section access?

I created an app, did the binary load, created the section access. the funny thing is that I don't have access to that app once I load it, maybe because my user name is not in the list of users in the UserTable.

What is the difference of NTNAME and USERID?

Which one should I use?

Re: Best practice design pattern

sibusiso90 — Tue, 23 May 2017 07:42:04 GMT

NTNAME: QlikView will fetch the logon information from the OS and compare it to the value in this field.

USERID: This is when you want the app to ask you for a log in everytime you open it and not for it to search your os for your logon information

It depends on your situation for which one to use. I hope this helps. if not please ask

Re: Best practice design pattern

arixooo123 — Tue, 23 May 2017 07:46:37 GMT

Thanks mate,

Any idea when should I create this layer? I mean security layer, should I create it after finishing the dashboard development?

Re: Best practice design pattern

sibusiso90 — Tue, 23 May 2017 07:53:39 GMT

I would advise creating the security layer when you are loading the data into the dashboard before you create the app as you will have data in the app and that could be sensitive data in wrong hands. What I always do, is to create an admin user for me to work and knowing my information is safe until you done, then add all the other users.