How to ensure complete and accurate view of QV Lineage when some QVWs have had their data reduced?

[Cmurphy55]

I am trying to help my coworkers gain an insight into our QlikView environment's lineage. We have had the most recent version of Governance Dashboard for awhile now, but we have noticed that if a QVW has had its data reduced or doesn't store any internal tables, it possesses no XML metadata (and by extension no LineageInfo).

Is there a way to get around this? Or are we just out of luck?

Related to this thread:

https://community.qlik.com/t5/QlikView-App-Development/QVW-LineageInfo-missing/td-p/672700

[Cmurphy55 · Accepted solution]

After opening a case with QV Support, their Data Governance team came back with the following information:

If no data remains in the QVW, the lineage can be limited, this is working as designed. The workaround would be to modify the load script of the apps to retain a simple table with one line of data.

It will be necessary to customize the Governance Dashboard in order to get the desired output.

Therefore there is no way to perform data reduction for storage concerns without breaking QV Lineage.

[v_petrenko]

There are at least two workarounds for ensuring that lineage metadata is kept in a QVW even if tables are dropped in the end of a script (which is a frequent case for extractor applications that do only data transformations that are stored in QVDs and have no GUI). 1) create empty dummy table and keep it in app's data model. Now all lineage metadata including one of dropped tables would be saved. Dummy_table: Load Null() as Dummy_field Autogenerate (0); 2) remove all rows from data tables in the end of the script, thus keeping table structure intact. Inner Join ([{Table to Truncate}]) LOAD * Inline [ %truncate ] ; DROP Field [%truncate] ; But be aware when using it inside iteration constructs like FOR...NEXT or DO...WHILE with loading-dropping! Unwanted concatenations may occur, so debug twice before making changes.