Deployment Pipelines - Dataset is different after a "Successful" Promotion from DEV to TEST

My pipes are finaly "clean" (there are now "Different" elements). Thank you 

I can confirm that the bug fix from Microsoft has worked for us. All our datasets show "equal" (not different) again after promoting them through the pipeline. Thanks LeeBenjamin & the MS team for listening and fixing.

I can confirm that our GOV site is now functioning correctly.  Thank you.

Anyone expereincing this deployment pipeline issue again?  I just promoted from DEV to TEST and its showing differences, even though there are none. 

I published a dataset to DEV using PBI desktop and then used deployment pipeline to deploy to TEST and it says differences.

Hi wjkolesar,

In some (not so common) cases the comparison process of an item cannot be completed so its sync status is unknown. Deployment pipeline tagged such items as 'Different'. You can open a ticket for support to check whether it is this case or other and get further assitance. 
In addition, we're about to release a new feature in a few weeks, which provides more details on the 'Different' label: name change, schema change (with the option to view the changed lines highlighted in the schema) or unknown (the above scenario). At first, the supported item types are just dataset and dataflow, we'll soon have paginated report and we hope to quicky add other textual item types. stay tuned! 

BR,

Lee

I did experience the same issue again too last week.
It went away, when I let the dataset fully refresh first in DEV before promoting it to TEST and PROD. 
Interestingly it never showed a difference between TEST and PROD, no matter what the refresh status was.
Maybe this helps.

I am having same issue.  I just setup a new Deployment Pipeline..

I published three datasets to the [Test] stage. then deployed the datasets and their associated reports to [Production].  Two out of three datasets compare as equal, but one does not.  Can't be because of any changes as all I did was publish to [Test] then straightaway publish to [Production]...

So the issue resolved itself... I turned off the scheduled refreshes.. then used the REST API calls to cancel any outstanding refreshes.  In our case it seems things got messed up when more than one refresh was executing or attempting to execute.  I turned off the scheduled refreshes for about an hour or two then turned them back on.  and within the next hour the scheduled refreshes started working...

Was the fix applied to gov sites?  I am still having the issue.

Hi apratt2003 , 
The release for GOV sites takes a bit longer and so it is expected to be released by end of January.
Thank you,

Lee

Ok, thank you for the response.

No, My pipeline is acting as expected.