topic Re: GET /v1/apps/{appId}/data/lineage not working well when using precedent loads in Integration, Extension & APIs

GET /v1/apps/{appId}/data/lineage not working well when using precedent loads

mgbaldoma — Wed, 17 Jul 2024 18:12:02 GMT

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.

Re: GET /v1/apps/{appId}/data/lineage not working well when using precedent loads

mgbaldoma — Thu, 17 Oct 2024 14:20:21 GMT

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.

Re: GET /v1/apps/{appId}/data/lineage not working well when using precedent loads

Thomas_Hopp — Thu, 27 Mar 2025 15:30:33 GMT

This is fixed from Nov 24 release onwards as well in the on premise QSEoW product.

Best regards,

Thomas