topic Re: Deployment Pipelines - Dataset is different after a "Successful" Promotion from DEV to TEST in Service

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

Kwarren35 — Wed, 28 Oct 2020 13:53:47 GMT

Hello,

We have been using Deployment Pipelines fairly successfully for 2 months now and working through issues. We need some ideas on how to best troubleshoot what is causing the dataset to be different, after a successful deployment from DEV to TEST.

What we did:

1. Downloaded Power BI Desktop Oct 2020 version

2. Implemented RLS into our dataset

3. Published "Sales" PBIX file into Deployment Pipeline DEV workspace

4. Had an administrator "Take Over" dataset ownership from publisher developer, made sure credentials to our 1 data source was valid and refreshed dataset successfully

5. In Deployment Pipelines interface, Administrator selected "Sales" report and dataset from DEV and promoted to TEST workspace "Successfully", however after deployment, the dataset was not equivalent, but the report was.

6. While troubleshooting, we had our BI "Sales" report developer rename the "Sales" report to "Sales_Test" and do the deployment of the report and dataset together from DEV to TEST, and the dataset was equivalent.

We dont want the Developer doing the deployments, so do you have any troubleshooting ideas on why things are different?

We are not using any of the following Unsupported items:

Unsupported items

Deployment pipelines doesn't support the following items:

Datasets that do not originate from a .pbix
Reports based on unsupported datasets
Template app workspaces
Paginated reports
Dataflows
PUSH datasets
Workbooks

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

Nimrod_Shalit — Thu, 29 Oct 2020 09:23:58 GMT

Kwarren35,

Few questions to better understand:

1. did you configure rules on the 'Sales' dataset? if so, were they already applied?

2. when you said 'different', did you mean that they were labeled as 'different', or you actually spotted a difference between the datasets?

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

Kwarren35 — Mon, 02 Nov 2020 13:02:58 GMT

Nimrod_Shalit

1. The BI developer applied the Role Level Security rules to the dataset before publishing to DEV workspace.

2. The deployment pipelines interface shows the "sales" dataset as non-equivalent between DEV and TEST, but I cannot spot a differences when comparing files

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

eligr — Tue, 03 Nov 2020 07:49:11 GMT

Hi Kwarren35 !

Sorry to hear about that.

We have a bug in that area, working on fix right now.

Eli.

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

PoshLegs — Thu, 05 Nov 2020 22:58:03 GMT

Thank you for this update. I see the same as Kwarren35, I first noticed this after the upgrade from the Sept to the Oct build.

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

Anonymous — Wed, 24 Feb 2021 14:00:34 GMT

Hello. I think I have the same error here. There is already a fix ?
If in dev I make an update that changes my dataset, when deployed to test it will keep saying that there is differences between the two datasets. Then, if I download the dataset .pbix from the test workspace, i can see that is is all messed up (tables names and fields) . I can only get this ok if I delete everything from test and deploy again from the beginning what is not good.

There is any solution ?

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

Nimrod_Shalit — Mon, 01 Mar 2021 08:30:43 GMT

Anonymous , few questions:

Is it happening on other items in your pipeline, or just datasets?
Is it happening on other datasets, or just this particular one?
Did it happen several times on that dataset, or just once?
What change did you made, that caused it to happen? or any change ends up with same result.

Also note that downloading a PBIX that been created/ updated through deployment isn't supported, so you might get corrupted files. We will block the option to download in the near future.

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

Anonymous — Mon, 01 Mar 2021 08:49:18 GMT

Hello ,
For now I am just working with a single dataset that feed a report. So, it is just happening to the dataset, what has then an effect in the report.
It was more than one time and to fix it I had to delete the content of the workspace and deploy again.
The changes that I made that lead to this were changes in the model in PowerQuery. One time was the adding of a new table and the other time was the change on a step in a query.
How I manage the process : I made the changes in the PowerBi desktop and then I publish to the dev workspace, overwriting the existing content. Automatically the comparison in the deployment pipeline detects that there are differences in both objects : report and dataset. I select both and deploy to test environment. Then no differences are detected between the report, but the dataset still detects differences. When I said that I download the .pbix is not from the deployment is from the test workspace view.

I am not saying that it happens everytime I did changes in the model, but at least in these times it happen.

Thanks a lot.

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

Nimrod_Shalit — Tue, 09 Mar 2021 09:55:05 GMT

Please open a support ticket, sounds like a specific bug.

Add screenshots and the details of all the relevant items, so we can track down the problem.

Thanks,

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

karo — Tue, 01 Jun 2021 07:01:45 GMT

Hi,

Anonymous do you have any updates? It seems that I am experiencing similar issue.

Nimrod_Shalit any known issues from Microsoft regarding this case?

Regards,

Karo

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

Anonymous — Wed, 02 Jun 2021 08:07:54 GMT

Hello,
I stopped to have this strange behavior after separating dataset and report in two different .pbix files as recommended in the good practices of deployment pipelines:
https://docs.microsoft.com/en-us/power-bi/create-reports/deployment-pipelines-best-practices#separate-modeling-development-from-report-and-dashboard-development

To split it, check the following link :
https://www.havensconsulting.net/blog-and-media/splitting-a-power-bi-pbix-file-into-a-dataset-and-lean-report-file

With that, the changes done in the report or in the dataset become more independent what is better for deployment.

I hope it can help,
Regards,

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

KNP — Mon, 29 Nov 2021 19:23:49 GMT

I've had a similar issue and after a bit of testing, I've found a workaround for my scenario. Posting here in case it helps others.

The change that broke it

My dataset is separate from my report.

Deployment pipelines were previously working without issue.

The only change I made was to rename the only security role in the dataset and deploy to dev.

Confirming the issue

To check that my assumption was correct, I changed the name of the security role back to what it was and redeployed to dev. Deployment pipelines worked again.

The workaround

I needed the security role renamed so to try and get dev and test to align, I deployed my PBIX with the renamed security role back to dev and then also manually deployed my PBIX directly to test. No need to delete first.

Pipelines now works again.

Like I say, might not be suitable for all cases, but hopefully it is helpful to some.

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

Kurbanc — Wed, 18 May 2022 07:52:54 GMT

Hello I have exactly the same issue now.

After deployment process from dev to test piepline shows the datasets are different. What's more if the dataset is published directly to the PROD then after deployment from Test to PROD we have 2 datasets with the same name.

I've already remove all datasets from DEV and TEST workspaces and try to deloy everything once again, but it still not working.

Any idea what can I do?

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

Data-Rainer — Tue, 13 Dec 2022 03:06:42 GMT

It has been two years since this thread was posted and I am experiencing the exact same issue with our deployment pipeline. We have successfully operated our dataset promotion for over a year without any issue ever. Suddenly since last week our TEST & PROD pipeline show our main dataset as "Different", even though they are identical as they always have been and have been successfully deployed from DEV to TEST to PROD.

Nimrod_Shalit
Is there any progress on identifying possible causes?

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

LeeBenjamin — Wed, 14 Dec 2022 07:53:19 GMT

Hi Data-Rainer ,

Status of "Different" for a deployed item shouldn't be expected right after a successful deployment (could be though after a failed deployment). Therefore, it could be one of the two:

A bug - Please open a ticket and provide the deployment id (can be copied from the deployment's record on 'Deployment History')
A change was done next to the deployment completion. The dataset could be changed by several users on several places (not just through pipeline) so it could be someone else made a change.

In general, there could be several reasons for deployment pipeline to tag the "Different" label to an item, which can be ruoghly categorized as follow:

Setting change: renaming an item, changing an item's sensitivity label.
Code change: which means content/schema changes.
Deployment rule was set and deployment is required to apply it - The rule will be considered for the compare action, but since deployment wasn't executed yet, a difference will be identified for the item.

we're working these days on adding indication for 'Different' items, saying which of the above two reasoning categories is the reasone for the DIFF label. moreover, in case item got indication of code change, it would be possible for users to review the code changes (Read-only. Could be for only some item types at the begining).

Best regards,

Lee

Deployment pipeline PM

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

Data-Rainer — Wed, 14 Dec 2022 20:08:20 GMT

Thank you LeeBenjamin ,

To the best of my knowledge, none of your possible explaination could be a cause in our case.
We have not made any changes to any settings of the dataset for the last couple of weeks, other than some role edits for row level security.

The deployment pipeline is always successful.
How do I log a support ticket please?

Cheers,
Rainer

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

karo — Thu, 15 Dec 2022 07:27:42 GMT

Data-Rainer

How to create a Power BI Support Ticket:

If you are a Power BI Pro customer, support is included at no additional charge. Create a support ticket via GET SUPPORT
If you are an administrator of your Power BI tenant, open a support ticket in the admin center support portal.

After creating a ticket someone from Microsoft will contact you to get more details and investigate the issue.

Regards,

Karo

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

Eliasaki92 — Fri, 16 Dec 2022 08:08:37 GMT

I am having the exact same issue since the beginning of the week and would be super interested why this happening and how to resolve

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

Anonymous — Fri, 16 Dec 2022 08:48:56 GMT

Exact same issue since this week, here too.

A few tests that I have done :

* Publish the dataset with a diferent name to force te creation of a new object, push to test --> says the files are different.

* I recover versions from setembre and octobre that worked fine at the time, push to test --> keeps saying the are different.

* I started removing content from the dataset to check if it is any part of the dataset that is broken and even with a simple single table connected to the source it keeps saying the files are different.

* When I test a new file with a dummy manual source it works fine.

It seems to me a bug on the deployment pipelines ?

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

apratt2003 — Fri, 16 Dec 2022 19:02:47 GMT

I am also having the same problem with the addition of the dataset not updating the schema changes.