Forum Discussion
Deployment Pipeline compare using Fabric REST API
- 6 months ago
Hi SanderTK
You don’t need the complete UI comparison logic. If an artifact in DEV has a modified time that’s later than its last deployment time in the pipeline, it means there are changes in DEV that haven’t been deployed yet. This is enough to identify possible missed deployments.While it won’t show the specific changes, it effectively addresses the issue of missed deployments without adding unnecessary complexity.
If you have any further questions, feel free to reach out and we'll be glad to assist.Regards,
Microsoft Fabric Community Support Team.
Hello SanderTK
There isn’t a public “Compare” API that gives you the same green or orange “identical” or “different” result as you see in the Deployment Pipelines screen.
What you can do for now is use the Pipelines REST APIs to get a list of items in each stage and spot the differences yourself, based on things like IDs, names, paths, and when they were last deployed. If you want to dig deeper, especially with Reports and Dataflows, you can use Git-integrated PBIR for a better check on how similar they are.
GET /v1.0/myorg/pipelines/{pipelineId}/stages/{stageOrder}/artifacts will show you the supported items (datasets, reports, dataflows, dashboards, and so on) with details like:
- artifactId, artifactName (or artifactDisplayName)
- sourceArtifactId, targetArtifactId (if paired)
- lastDeploymentTime
For Power BI Reports, if you’re using Git integration with PBIR (Power BI Project), the report is defined in JSON. You can create a standard JSON hash, ignoring fields like timestamps that change every time.
For Dataflows, you can pull their JSON definitions using the Dataflow APIs and create a hash as well.