topic Re: Need Interactivity between Two Data Model in Single App in QlikView

Need Interactivity between Two Data Model in Single App

mhmmd_srf — Wed, 25 Nov 2020 16:16:04 GMT

Hi All,

I have one single App but have two data model with Same set of Tables. Only difference is Fact Table join condition with Date table.

Date.Date_Key = Fact.OrderCreatedDate_Key

Date.Date_Key = Fact.OrderChangedDate_Key.

But the requirement is If I select any Year from 1st Tab, it should reflect into 2nd Tab.

Similar to other Filter Criteria also.

I am attaching the App.

Could you please help me to implement that.

Thanks,

Sarif

Re: Need Interactivity between Two Data Model in Single App

RSvebeck — Tue, 09 May 2017 11:44:16 GMT

The easiest solution for you is to create two date tables. "Change Dates" and "Created dates".

There is also a way to keep just one date table but instead make a new field called "Date type", that has the value "Change" or "Create", depending on the date field name.

Robert

Re: Need Interactivity between Two Data Model in Single App

mhmmd_srf — Tue, 09 May 2017 11:51:42 GMT

Hello Robert,

I already have two different Date Tables.

Thanks,

Sarif

Re: Need Interactivity between Two Data Model in Single App

RSvebeck — Tue, 09 May 2017 16:24:54 GMT

Ok I see, I was not looking at the attachment.

I would advice you to make just one transaction table and one date table, and one Suppliers table, etc etc..

So I would first concatenate the two transaction tables ORD_CHANGED_FACT_PURCHASEORDERAUDIT and ORD_CREATED_FACT_PURCHASEORDERAUDIT or I would OUTER JOIN those tables into one table, depending on how closely related they are, like if it is 1=1 match, one purchase order is represented only once in each table. If not, then I would concatenate.

Then also remove all duplicate dimension tables (supplier, items) and keep only on date table..

Remove all QUALIFY coding.

That way you will be able to see the connection easily.

Re: Need Interactivity between Two Data Model in Single App

Peter_Cammaert — Tue, 09 May 2017 17:57:37 GMT

Why not use a single data model and add a setup for Canonical Dates? Makes life way easier...

See: Qlik Design Blog : Canonical Date | Qlik Community