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

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:

1. Setting change: renaming an item, changing an item's sensitivity label.
2. Code change: which means content/schema changes.
3. 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