Enrichment the QlikSense lineage functionality

[nicolasGutierrezGarcia1970]

We seem to see a lack of detail in the lineage of QlikSense reports.

For example, if the query of a Qlik report datamodel is as follows:
-- EELL Local Entities
EELL_RESPONSIBLE:
SELECT
e.te_eell “Local Entity”,
er.te_responsible “Responsible”,
'https://example.com/documento/' ||
lpad(e.co_ine, 3, '0') ||
'/document/' |||
lpad(e.co_ine, 3, '0') ||
'.pdf' AS “url_Document”
FROM schema.eell e
JOIN schema.eell_responsible er
ON er.id_eell = e.id_eell
;
STORE EELL_RESPONSIBLE INTO [lib://Address/eell_responsable.qvd] (qvd);
DROP TABLE EELL_RESPONSIBLE;
[EELL_RESPONSIBLE]:
LOAD
“Local Entity”,
“Responsible”,
“url_Document”
FROM [lib://Direccion/eell_responsable.qvd]
(qvd);

Only the lineage of the report is built with the table: [EELL_Responsible] which is the one returned by websocket, instead of building the lineage against the tables that appears in the join: schema.eell and squema.eell_responsible which would be from our point of view the correct thing to do.

Can you please review it and in case you think it is correct, enrich the lineage functionality to take into account the tables used in the query and not only the tables returned by the websocket?

Thank you very much.