Qlik Community

Ask a Question

QlikView App Dev

Discussion Board for collaboration related to QlikView App Development.

Support Cases coming to Qlik Community Oct. 4! Start chats, open cases, explore resources: READ DETAILS
Showing results for 
Search instead for 
Did you mean: 

Why cant i directly build my dashboard on 2nd layer i.e data model(data mart) itself


I created my data model in 2nd layer.

So I don't want to call that as binary load in another qvw file rather on 2nd layer only I will create dashboard..

If any suggestions wts the advantage if I use it as binary and create only front end in different dashboard.

Please exprets can comment  bcs, I felt why to unnecessarily increase one more layer in the name of 3teir architecture..

IF really needed whats the advantage (anything like dashboard on 2nd layer may b 200 mb and if used binary might become 100mb )..

Request you to comment with valid proofs why Binary wt it ll do?

why should I create 1more layer? which will increase my task running time by adding 1more application?

Why Qlik recommend 3layer..(nt looking fr docs as I have many but need justifications)

Else I think in 2nd layr we can build dashboard..Plss comment as its going to effect entire my organization??


22 Replies

Hi marcus_sommer

Actually my intension to create this thread is inline with your first paragraph (That's hw I got my doubt on Binary keyword)

And your 2nd para yess..I gree with them bcs if I have to share data model then,we have also done the same/followed the same.

Yess,some times 4 layer, seen it when even subsequent QVD's r also shared and even latr data model as well.

Then,fr stand alone QV-applications, I think going with only 2 layer is good only (only if Binary is just key word)..And 3 layer is definitely preferred if Binary lightens the file or make it more efficient and tht doubt remains as doubt as we need to know logics behing Binary I guess



MVP & Luminary
MVP & Luminary

For me it's easier (to try) to apply the same logic to all of my tasks even if they are quite simple and could be implemented with less layers to keep the number of exceptions as small as possible (especially in the beginning of the environment life-cycle).

In real life there are coming enough requirements to change and adjust things and implement new ones and often are they not well elaborate from the business and quite experimental solutions are going live without the layer-logic and other best practice approaches and I swear they won't never be cleaned properly or documented in any way ... as far as they are running but they are a nightmare if I must maintain them later ...

- Marcus


"Or its just a statement to load 1 QVW file into other??"

It just loads the datamodel from the source QVW, producing the exact same physical data model in the target QVW.  The resulting model is not smaller or optimized in any way by BINARY, 

The key word here is BINARY -- meaning the datamodel is copied in it's physical internal storage format with no logical processing of the contents.


View solution in original post