Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and a 50 percent discount on exams.
Get startedEarn a 50% discount on the DP-600 certification exam by completing the Fabric 30 Days to Learn It challenge.
I am running into an issue where after deploying an update to a dataset and pushing it from DEV to Test, our deployment pipeline is showing the datasets as being different. I used the ALM Toolkit to compare the datasets and they come back as identical. Any thoughts on why this would be happening?
Let me know if I can provide more information.
Solved! Go to Solution.
For safety you can save the model as a BIM file using Tabular Editor, then just promote through the pipeline so they get back in sync. It could be some insignificant metadata that the pipeline is seeing that ALM Toolkit isn't looking at.
You might also compare the two BIM files in NotePad++ using the Comparer 2.0.2 addin. The BIM files are just JSON.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI ReportingFor safety you can save the model as a BIM file using Tabular Editor, then just promote through the pipeline so they get back in sync. It could be some insignificant metadata that the pipeline is seeing that ALM Toolkit isn't looking at.
You might also compare the two BIM files in NotePad++ using the Comparer 2.0.2 addin. The BIM files are just JSON.
DAX is for Analysis. Power Query is for Data Modeling
Proud to be a Super User!
MCSA: BI Reporting@edhans appreciate the information. I use TE3 enterprise and have these stored as .bim files so I will investigate.
That said, I did hear back from MSFT support engineers and was told the differences shown is a bug and a fix is currently being worked on by the product team.