Forum Discussion
Impactful IndividualDeployment Pipeline Error - Changes made to the source dataset are preventing the deployment.
Hi,
The dataset that caused the issue was an SQL Server (On-Prem) database table. We had made many changes (add, remove, modify fields) and successfully deployed multiple times. Not sure what it was that broke the Pipeline.
The model itself has several SQL server data tables, dataflows from within the workspace and dataflows from a separate workspace.
I think I have solved the issue (still testing). I used ALM toolkit to sync the two datasets and it has just let me deploy to test, I had to then use ALM toolkit again as I got the same error Test --> Dev
I have just kicked off the PowerAutomate process that refreshes everything, hopefully will work!
Impactful IndividualHi all,
Additional update in case anyone finds it useful as I hit another deployment error today 😞
Again terrible error messages with no clue on what the issue was or how to resolve. This time ALM toolkit did not manage to solve the problem (although it pointed me in the right direction)
The issue occurred when I modified an import process to remove a format function from the underlying SQL (it was resulting in invalid dates) then converted the resulting text field to date, I was able to deploy the revised model to test as that dataset was empty, deployment to prod then failed, I'm assuming this was because the values already in the dataset could not be converted to date as they were invalid. As I couldn't modify or clear the contents of the prod dataset directly I was stuck.
The fix was:
- format the field back to text in dev version
- redeploy (all stages)
- refresh the data (all stages) (to remove the invalid dates)
- Format the field back to date in dev version
-redeploy (all stages)
- Refresh the data.
It feels like the pipeline process needs an option to clear existing data before applying schema changes (and better error warnings!)
- Nimrod_Shalit
Power BI Team
For the scenario you described we provided, on the error message, the ability to continue deployment while removing data, or stop the deployment.
I'm interested to understand why this didn't happen in your case.
It would be very helpful if you can try and repro what you described and provide screenshots and technical details in a support ticket so we can take a look internally and investigate.
- itchyeyeballs
Hi, I will try to replicate the issue.
Is there any available documentation that describes this deployment behavior? I have looked here but can't see anything.
