Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi.
I'm working on an app to navigate the lineage data from our apps.
Everything went well until I've noticed the lineage is blank when precedent load is used.
Example:
Load field1 From [lib://SomeDataSpace:SomeDataConn/SomeTable.qvd (qvd);
The API request for that app will return:
[
{
"discriminator": "lib://SomeDataSpace:SomeDataConn/SomeTable.qvd;",
"statement": ""
}
]
If you add a precedent load:
Load *, 1 as counter;
Load field1 From [lib://SomeDataSpace:SomeDataConn/SomeTable.qvd (qvd);
The new request will return
[
{
"discriminator": "",
"statement": ""
}
]
This happens in Saas and in QSEoW (tested on Nov/23 and Feb/24). On QSEoW you can test this on the Qlik Engine Explorer, calling the GetLineage doc method.
Hey, I forgot about this post. I reported it as a bug, and it has been fixed on SaaS, but they won’t be fixing it in QSEoW since the API endpoint for that platform is going to be deprecated soon.
This is fixed from Nov 24 release onwards as well in the on premise QSEoW product.
Best regards,
Thomas