Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
AWS Degraded - You may experience Community slowness, timeouts, or trouble accessing: LATEST HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
mgbaldoma
Partner - Contributor
Partner - Contributor

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

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.

Labels (3)
2 Replies
mgbaldoma
Partner - Contributor
Partner - Contributor
Author

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.

Thomas_Hopp
Employee
Employee

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

Best regards,

Thomas

Thomas Hopp
Director - Product Management