topic Re: Direct Discovery - QlikView in QlikView

Direct Discovery - QlikView

Tue, 29 Jul 2014 13:19:17 GMT

Hi Friends,

My requirement to have real time reports i.e. my reports should be connected with database, and show the results in real time. Forum I get to know the best to tackle this situation is to use Direct Discovery feature.

But I found plenty of challenges. Did any one used it?

DIRECT QUERY

DIMENSION

"party_id",agent_name, "role_display_name"

MEASURE

"role_end_date"

FROM XXXX.dbo.XXX;

I am displaying above records in table box, but I am unable to export it to excel because role_end_date is used measure, is there any way I can export the measure column as well.

Thanks

Arindam

Re: Direct Discovery - QlikView

Wed, 30 Jul 2014 04:32:52 GMT

Any pointers guys?

Re: Direct Discovery - QlikView

avinashelite — Wed, 30 Jul 2014 04:46:31 GMT

Hi Arindam,

Since your making it as measure, the data will not come into Qlikview i.e in-memory. It will be fetched directly from DB so you cannot export it!!!! make it as Dimension then only you can.

Regards,

@vi

Re: Direct Discovery - QlikView

Wed, 30 Jul 2014 04:52:49 GMT

HI Avinash,

You are correct, and I understand if I make it as dimension, problem will resolve.

But there are certain columns which have to be in measure, and requirement to have them in exported excel. When I did a print I see all my columns (including measure column as well), but export not working.

Is there any way to sort it via writing some Macro?

Thanks

Arindam

Re: Direct Discovery - QlikView

avinashelite — Wed, 30 Jul 2014 05:00:23 GMT

Hi Arindam,

Macro will cause performance issue, ok to resolve your problem do one thing load your column in both Dimension and measure like below:

DIRECT QUERY

DIMENSION

"party_id",agent_name, "role_display_name", "role_end_date" as Role_date

MEASURE

"role_end_date"

FROM XXXX.dbo.XXX;

Hope this may help you.

Regards,

@vi

Re: Direct Discovery - QlikView

Wed, 30 Jul 2014 05:02:54 GMT

Okay, good idea let me check, I will revert Avinash.

Re: Direct Discovery - QlikView

Wed, 30 Jul 2014 05:09:02 GMT

Hi Avinash,

If I do the way you suggested, then in my table box, I need to show --> "role_end_date" as Role_date (dimension) right?

The reason I used "role_end_date" (measure) in table box is to get the data directly from data source.

So if I use the dimension in my table box it will export fine, but data will be coming from memory not from direct data source.

Let me know if you agree?

Thanks

Arindam

Re: Direct Discovery - QlikView

avinashelite — Wed, 30 Jul 2014 05:12:22 GMT

Hi Arindam,

Yes, your correct.

Re: Direct Discovery - QlikView

Wed, 30 Jul 2014 05:16:22 GMT

Then Avinash, I am in same track again

Let me see if there anyway to track this. Please let me know if you come across any other alternates?

Thanks

Arindam

Re: Direct Discovery - QlikView

JonnyPoole — Thu, 07 Aug 2014 17:11:28 GMT

You know i couldn't find anywhere in the documentation that said its normal that the excel export feature should be disabled on table boxes when measures are included so i logged the issue with customer support. We'll see if R&D deem it to be a bug. I'll repost if/when i hear something back. It could just be a bug but we'll see.

Re: Direct Discovery - QlikView

Fri, 08 Aug 2014 04:31:16 GMT

Thanks Jonathan, will be great help, if you get any updates.

Re: Direct Discovery - QlikView

sujeetsingh — Fri, 08 Aug 2014 04:37:45 GMT

QlikView determines which data resides in-memory and which data is direct discovery data by

using the special script syntax, “DIRECT SELECT”. This syntax allows certain data elements not to

be loaded into the QlikView data model during the script reload process, but still available for

query purposes from the QlikView User Interface and to be combined for analysis with the

QlikView in memory dataset.

Once the direct discovery structure is established, the direct discovery fields can be used with

certain QlikView objects. When a direct discovery field is used on the QlikView object, QlikView

will automatically create the appropriate SQL query to run on the external data source. The

result of the query will be displayed on the QlikView object. When selections are made on the

QlikView application, the associated data values of the direct discovery fields will be used in the

WHERE conditions of the queries. With each selection, the direct discovery charts will be

calculated, where the calculations and aggregations will be done on the source table by

executing the SQL query created by QlikView. It is possible to use calculation condition feature of

the QlikView charts to set a condition indicating when the chart should be calculated. Until that

condition is met, QlikView will not run queries and the chart will not be calculated. Please note

that QlikView will execute SQL queries on the data source for some of the list boxes that use

direct discovery fields. This is required to achieve the associative navigation capability.

Re: Direct Discovery - QlikView

Fri, 08 Aug 2014 04:44:03 GMT

Thank You Sujeet for explanation.

My problem is in export feature, columns which are in Measures, cannot be exported, understand it is not in the memory, but trying to explore if/ in case there are any possibility to have export feature enabled.

Thanks!