topic Re: Direct Discovery is not working in Qlik Sense in App Development

Direct Discovery is not working in Qlik Sense

rahulpawarb — Sat, 16 Nov 2024 19:05:22 GMT

Hello Team,

Hope you are doing well!

I am trying to build a Qlik Sense application with Direct Discovery feature (Direct Query); however, it is not working 😞

Below is the scenario:
- Fact tables and dimension tables loaded into Qlik application

- Config table (with frequent data changes) are loaded with Direct Query

- Fact tables are linked to Config

- We are passing config_uuid as parameter in iFrame tag (&select=config_uuid,14CBEE1A-8CBA-430F-9ECA-1E34E97CC999)

- When I insert/update/delete a record in Config table then it should be loaded in Qlik application with reload; WHICH IS NOT WORKING CURRENTLY.

Any help on this will be highly appreciated.

//Definition of Config table - Loaded from PostgreSQL database via ODBC

config:
DIRECT QUERY
DIMENSION
config_uuid
,config_name
FROM "dbo"."config";

Regards,

Rahul Pawar

Re: Direct Discovery is not working in Qlik Sense

rahulpawarb — Thu, 20 Feb 2020 06:32:52 GMT

@Michael_Tarallo could you please help me on this?

Re: Direct Discovery is not working in Qlik Sense

kaushiknsolanki — Thu, 20 Feb 2020 07:05:34 GMT

HI,

First of all check if the database connection is right. And see if Qlik can fetch the data without Direct Discovery.

Re: Direct Discovery is not working in Qlik Sense

rahulpawarb — Thu, 20 Feb 2020 07:19:52 GMT

Hello Kaushik,

Thank you for your response!

I did checked that! I am able to access the database without Direct Discover via ODBC as well as PostgreSQL connector.

I wonder why it is not working with Direct Discovery?

Regards,

Rahul Pawar

Re: Direct Discovery is not working in Qlik Sense

Michael_Tarallo — Thu, 20 Feb 2020 18:04:37 GMT

Hi Ranul -

First please verify this:

https://help.qlik.com/en-US/sense/November2019/Subsystems/Hub/Content/Sense_Hub/DirectDiscovery/data-sources-supported-in-direct-discovery.htm

DB2, Oracle and PostgreSQL

Direct discovery can be used in conjunction with DB2, Oracle and PostgreSQL but may require the following parameter in the set variables due to the quoting characters used in these sources:

SET DirectIdentifierQuoteChar='""';

If all looks well - then please open a case with Qlik Support - preferably with your Qlik Support credentials.

If you don't have Qlik Support contract - you can still open and report the problem as a guest:

https://community.qlik.com/t5/New-to-Qlik-Sense/Open-a-Support-Case-as-a-Guest/td-p/1669051

Hope this help.

Regards,
Mike