Find Customer Insights – Data datasource dependencies before replacement
Diesen Beitrag auf Deutsch lesen
Use the Customer Insights – Data API testing tool to locate measure and segment dependencies before replacing or removing a datasource.
TL;DR
In Customer Insights – Data, use Permissions > API, choose Customer insights – v1, and call ListAllMeasuresMetadata with implicit authorization and the instance ID. Search the JSON by display or schema name, reroute measures to a replacement Delta datasource, refresh, then repeat with ListAllSegments. External API consumers can still break after removal.
Original on Powerplatform.se. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
Admins/CoE should inventory dependencies with ListAllMeasuresMetadata and ListAllSegments before deleting a datasource, then refresh the datasource and rerun the queries to confirm removal. Makers should review measures and segments that reference the datasource, choosing whether to remove unused items or redirect active dependencies to the replacement. Admins/CoE should also identify external consumers of the table because the API may not block deletion even though those integrations will stop working.
Frequently asked questions
Why check dependencies before replacing a Power Query datasource in Customer Insights Data?
Measures and segments may still depend on the datasource, and the article warns that dependencies from things externally using the table can remain.
How do I open the API list that exposes datasource dependencies?
In Customer Insights Data go to Permissions and open the API tab, then choose the only available API, Customer insights v1. Search for ListAll and select ListAllMeasuresMetadata, later ListAllSegments.
What are the options for a measure that still uses the old datasource?
You can either remove the measure, or change all its dependencies to another datasource, a Delta one in the article, and refresh it.