Qlik Compose relationship with hard-coded value

Pierre_G — Fri, 14 Mar 2025 20:49:07 GMT

Source system has 1 status table that contains all statuses for multiple tables. How can this be implemented in Qlik Compose ?

Example:

Select * from Incident
join Status on incident.status_cde = status.status_cde and status.object_type_cde='Incident'

Select * from webform
join Status on webform.status_cde = status.status_cde and status.object_type_cde='Webform'

A hard-coded value cannot be specified in the Model relationship...

Re: Qlik Compose relationship with hard-coded value

TimGarrod — Wed, 13 Jul 2022 21:22:29 GMT

There are 2 ways to handle this in Compose.

Option 1 -

Model specific "LOOKUP" tables that represent each type of lookup. In your simplified scenario, that would mean having a "Incident_Status" and "Webform_Status" - and in the mapping for the 2 status tables, add the filter for "incident" and "webform" types.
Benefit of this, is any dimension etc. you create in the data mart has a well defined set of initial data and the universal lookup table is broken into its specific domain parts. Con - you have to manage multiple tables in the DWH Model.

Option 2 - Have 1 "Status" table. The "hard-coded"value would be handled in the ETL. e.g. the Status table PK would need to include "status_cde" and "object_type_cde". In the mapping for "Incident" - you would have status_cde mapped, and would hard code 'Incident' for the object_type_cde. Likewsie for 'Webform'

topic Qlik Compose relationship with hard-coded value in Qlik Compose

Qlik Compose relationship with hard-coded value

Re: Qlik Compose relationship with hard-coded value