Manage Metada - Key business

[YEL]

Bonjour, 

Lors de l'ajout d'un nouveau attribut, si je sélectionne la ligne pour ajouter une expression et défini cette ligne avec la clé primaire si elle est activé l'expression disparait. 

PJ 

Quand je sélectionne la colonne key busines l'expression disparait : 

Merci. 

[sureshkumar · Accepted solution]

Hello @YEL 

Unfortunately, Compose does not allow adding expressions for primary key columns when defining the schema. Here are some key points about this limitation:

• Primary key columns in Compose can only be single columns from the source tables. Expressions and concatenated keys are not supported.
• This is a current product limitation, likely because primary keys are critical for record identification and using expressions could make things overly complex.
• You can add expressions to non-primary key columns in the schema definition. It is only primary keys that cannot have expressions.
• As a workaround, you could create a separate column in your schema that has the expression, then unique index that column instead of making it the primary key.
• Primary keys are still useful in Compose even with this limitation - they allow deduplication, record identification, and improve join performance. So defining them is still recommended on appropriate columns.
• This has been a common feature request that Qlik is likely aware of, so support for primary key expressions could be added in a future release.

In summary, Compose does not currently support expressions when defining primary keys in the schema due to product limitations. Using a regular column indexed as unique is the best workaround for now. But you can still leverage primary keys on individual source columns as normal.

Hope the above information helps.

Regards,
Suresh