Load Data from Db during presentation filter

[#1]

Hi all,

to prevent a future problem with an application Qlik that is going to load a huge quantity of data, i'll like to know if it is possible to have an hybrid system.

During the presentation of the data some area, for example the product takes data from a qvd, other area, for example orders, takes data directly from the database.

In this way i can present all the data without load all from qvd, saving some terabyte and don't strain on the resurce of the server.

If it is possible do you have some example or documentation?

The second question is if it is possible to have a qvw that present generic data and, for example when i filter some data in a table or chart, automatically switch to another qvw that usa the filter set before and show detail data.

Thanks for your help!

Regards

Marco

[#2]

take a look at the direct discovery feature.

http://community.qlik.com/blogs/qlikviewdesignblog/2012/11/08/qlikview-112-and-direct-discovery

or

http://bi-review.blogspot.it/2013/04/first-look-at-qlikview-direct-discovery.html

Alessandro

[#3]

Hi Alessandro,

i've try the function Direct Select as in the first video.

if i have understand how use , I think it's useless.

1) I can use it only for one table in qvw

2) if i want to use some description field i cant. for example, i load a table that has   1 primary key, 1 field NAME and one field that AMOUNT.

if i use the field NAME in a table as calculated dimension it show NAME for all the row of the table. i can't see the value of the field.

the field NAME can't be use in a single field as filter.

for use it i have to load and in this way it is exactly the same as i load from a qvd.

The field Amount: i can use only if i write sum(amount) if i write an expression like sum (if (AMOUNT>10, 1,0)) it doesn't work.

I hope i haven't understand the possibility of the DIRECT function otherwise i think it is absolutly limited.

thanks for your help

[rbecher]

Hi Marco,

you're right Direct Discovery is still very limited. We hope to see more functionality in the future. Another downturn of DD is the initial load of all dimension occurances from the given fact table. It could take at least hours in Big Data enviroments to gather this data. To solve this we could think about query rewrite in the background but this is another story.

One solutions would be to segment the data in several QVWs and to address or jump the right segment in the right QVW document from a central generic QVW (document chaining). You can open the related document by link or button depending from the current selection.

Another solution is a 2-step approach where you would have a similar generic QVW and after a selection of the data you want to analyse to start a reload of a second QVW with this filter. Btw. we use this kind of scenario in Big Data environments where you never would be able to load all data into QlikView.

- Ralf