QVW LineageInfo missing

[blaise]

Hello fellow Qv'ers

Im trying to retrieve the qvw data lineage info from all my QVW but for some reason this data isn't present in the QVW when loading into QV as XML.

The lineage info resides in (XmlSimple, Table is [DocumentSummary/LineageInfo]).

Does anyone know why some qvw's doesn't have this info? I also have a lot of QVW's that also miss the DocumentSummary/FieldDescription and DocumentSummary/TableDescription.

Br Johan

[ashfaq_haseeb]

Hi,

you need to look at QlikView Governance

Regards

ASHFAQ

[blaise]

I would like to build my own app, Governance Dashboard includes way more info than i need for this particular project.

I have however asked the same question in the governance forum now.

Will also see if Governance dashboard can retreive the LineageInfo from my QVW but Im pretty sure It can't.

[ashfaq_haseeb]

Hi,

rwunderlich can help you here.

Regards

ASHFAQ

[blaise · Accepted solution]

It looks like the dataLineage info is missing if the QVW doesn't include at least one (internal) table.

If I add a table to the qvw's that lacked LineageInfo and performed a reload the data becomes available.

Think I'll file a bug-report...

[Tyler_Waterfall]

Johan Hessler - good observation - if there is no data stored in the qvw, then the LineageInfo element in the QVW xml footer (the 'metadata') is not present, at least not in 11.20 SR 4.  So the QVW only stores lineageInfo for internal tables.

Am I correct in assuming that you have a 'layer' of QVWs which load/transform data and store out to QVDs and the drop the tables?

[blaise]

Yes, most of my bigger implementations include a lot of "collect and store qvd" qvws. At least one per source system. After that I have the "transformation" step (sometimes one layer for each source system) and most likely a tranformation step per application before i actually consume and keep information in a qvw.

I solved my requirement by adding a dummy table to each "collect and store qvd" qvw but have today also started retreiving the "source files" info from the document log (so I can verify that the lineageInfo is reliable)

. Have a few implementations where the Qvw does different things based on weekday and day of month so i need to find a good to solve that.

Im thinking about running the LineageInfo collect for a month and based on history retrieve all source files or make use of the document logs in the publisher log directory (30 days history as a standard setting).

[rwunderlich]

"most of my bigger implementations include a lot of "collect and store qvd" qvws"

The lineage info for a QVD can be found in the QVD itself.

-Rob

http://masterssummit.com

http://robwunderlich.com

[Tyler_Waterfall]

Thanks Rob Wunderlich for the reminder!

[Anonymous]

Hello twa‌,

Within the previous version of the Governance Dashboard if I wanted to know "loaders" that connect to the database I could filter TableLineage qvd file by Source_Type = "Database". As it was mentioned earlier in this conversation "empty QVW loaders" are usually used to extract and save data as qvd files. Taking into consideration that the newest version of QVGD (v2.0.1) is skipping "an empty" QVW files, would you advice how to filter "loaders" that connect to databases only, please?

Many thanks in advance for your help.

Best regards,

Janusz