Forum Discussion
Obtain lineage for nested semantic models
I have several semantic models that are based on other semantic models. Is it possible to programmatically obtain a lineage? My goal is to get an overview of all reports and semantic models that are based on a given semantic model. This way, I can easily see what reports and semantic models are impacted by changes in a certain semantic model.
So far I have used the Get Reports API to obtain the semantic models on which the reports are based, but this is not enough in my case.
Thank you!
wiskundenerd I believe it is possible to programatically get the lineage from a Semantic Model. You can start by exploring the below API calls on your child or lowest semantic model (ID) in your model hierarchy and go upwards to the other semantic model. Try the below APIs
https://learn.microsoft.com/en-us/rest/api/fabric/core/items/list-item-connections
GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}/connectionshttps://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-datasources-in-group
GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/datasets/{datasetId}/datasourcesThanks,
Jai
3 Replies
- Jai-RathinavelSuper User
wiskundenerd I believe it is possible to programatically get the lineage from a Semantic Model. You can start by exploring the below API calls on your child or lowest semantic model (ID) in your model hierarchy and go upwards to the other semantic model. Try the below APIs
https://learn.microsoft.com/en-us/rest/api/fabric/core/items/list-item-connections
GET https://api.fabric.microsoft.com/v1/workspaces/{workspaceId}/items/{itemId}/connectionshttps://learn.microsoft.com/en-us/rest/api/power-bi/datasets/get-datasources-in-group
GET https://api.powerbi.com/v1.0/myorg/groups/{groupId}/datasets/{datasetId}/datasourcesThanks,
Jai
- AnonymousNot applicable
- AnonymousNot applicable
Hi wiskundenerd ,
Any update on this? Did the above suggestions help with your scenario? if that is the case, you can consider Kudo or Accept the helpful suggestions to help others who faced similar requirements.
Regards,
Xiaoxin Sheng