Qlik Community

Ask a Question

Suggest an Idea

Vote for your favorite Qlik product ideas and add your own suggestions.

Announcements
QlikWorld Online 2021, May 10-12: Our Free, Virtual, Global Event REGISTER TODAY

Compose FDW - Make Datamart validation not force a drop and recreate for every fact/dim structure change

QDI_Manuel
Employee
Employee

Compose FDW - Make Datamart validation not force a drop and recreate for every fact/dim structure change

Currently, when making any structure changes (E.g. add a column, drop a column) to a data mart fact or dimension, a subsequent validate of the changes results in dropping and recreating the entire data mart, even if only one object should have been modified.  This causes a usability and data availability issue, particularly when you have a large data mart (300+) facts, because both the drop and create and reload operation of the entire mart could take many hours.

The idea is to potentially add more elaborate logic to the validation so that it can detect a minor change to one table and just operate on that table rather than the entire data mart.

Qlik Compose for Data Warehouses @TimGarrod @Tzachi_Nissim 

3 Comments
paulstevens
Partner
Partner

We also experience this behaviour in the data mart and would like changes to be applied to the data mart without requiring 'drop and recreate'.

jtompkins
Contributor III
Contributor III

YES! This is such a hurdle for us, especially because dropping/recreating dims breaks the referential integrity of our historical fact tables.

Tzachi_Nissim
Employee
Employee

Hi Manuel,

Thanks for your input and thanks to others that commented. This is on the roadmap, but I would be interested in what you consider the most painful "minor change" that should be addressed first. 

Thanks,

Tzachi

Status changed to: Open - On Roadmap