Qlik Replicate: Missing Primary Key on Target Table

[Alan_Wang]

Tables with too many columns (approximately 15 or more) can end up with a Unique Index instead of a Primary Key when Qlik Replicate builds the table. This is caused by a defect, leading to the key column transformation feature being automatically applied as the default setting.

The default Use target definition setting gets switched to Use transformation definition, which reorders the key columns and builds a Unique Index instead of a Primary Key.

Resolution

Workaround

Manually switch the option back to Use target definition. This will avoid the Unique Index instead of the Primary Key. 

Fix Version

Qlik Replicate November 2025.

Cause

SUPPORT-4339

Internal Investigation ID(s)

SUPPORT-4339

Environment

• Qlik Replicate version before November 2025