Forum Discussion

philcharbonneau's avatar
philcharbonneau
Regular Visitor
3 years ago

GIT integration within deployment pipeline

There appears to be a bug with the GIT integration within the deployment pipeline.  I get the error 'Something went wrong' followed by the Cluster URI, Activity ID,Request ID and Time when trying to sync changes from a DevOps repository to a Power BI workspace with GIT integration enabled:

 

Current setup:

 

I have set up a separate deployment pipeline in Power BI called ‘CI/CD Dashboard Pipeline’ and assigned three new premium workspaces to it (CI/CD - DEVELOPMENT, CI/CD - STAGING and CI/CD - PRODUCTION).  I added our Power BI Service account as an administrator to each of these workspaces and as an Admin account for the deployment pipeline.

I created a new DevOps repository called ‘Dashboards’ and set up the GIT integration to it within the CI/CD - DEVELOPMENT workspace.  I added our Power BI Service account as a Build Administrator.  

 

When trying to push a report (saved as a project) from DEVOPS to the ‘CI/CD - DEVELOPMENT’ workspace, I get the error 'Something went wrong' followed by the Cluster URI, Activity ID,Request ID and Time when I try to sync using our Power BI Service account (please note that this report points to a dataset in another Power BI workspace). 

 

If I manually publish a pbix report to the workspace ‘CI/CD - DEVELOPMENT’ then the report appears and can be opened within the ‘CI/CD - DEVELOPMENT’ workspace.  When I sync with GIT, it is successful, however, the ‘report.pbip’ file does not get added to the GIT repository (I thought this was strange).  Therefore, I don’t have a way to modify the report.

 

The dataset for the sample report existed in a different workspace, so I tried placing the dataset into the ‘CI/CD - DEVELOPMENT’ workspace and re-pointing the report to the dataset in ‘CI/CD - DEVELOPMENT workspace’.  This did not fix the issue either with synchronizing with the GIT repository. 

 

Any idea how I can get this to work for our environment?  Is it because my dataset doesn't exist inside of the report?

 

Thank you

No RepliesBe the first to reply