Forum Discussion
Deployment Pipelines - Dataset is different after a "Successful" Promotion from DEV to TEST
Advocate IVIt 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?
- LeeBenjamin
Microsoft Employee
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
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 ?
Same here ... I agree ... it's very likely a system bug in the deployment pipeline.
- Data-Rainer
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
karoAdvocate V
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
Hi there,
I am facing the same problem recently as others, and to my knowledge, I think none of the things you mentioned addressed the issue.
