Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago

Deployment Pipelines - Why is dataset different?

Hello, 

 

I just created the deployment pipeline and added some basic content to it (dataset and reporting sourced from the dataset). 
I deployed content to test, but the dataset is different. I don't know why. Any troubleshooting leads?

Here are some more details. 

1. Dynamic RLS is in place, using 1 role

2. Server & Database Parameters are currently pointed to PRD Server and Database for both environments

 

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Anonymous ,

    Please check the deployment steps to see if you forgot to synchronize. If not, please remove the newly added content from the pipeline test workspace first to see what happens.

     

    Did the above screenshot happen to the same user? 

    • When an item is removed or deleted, its rules are deleted too. These rules cannot be restored.

    • When you unassign and reassign a workspace to reestablish connections, rules for that workspace are not kept. To use these rules, you'll need to reconfigure them.

    • Rules for dataflows that have other dataflows as sources, are not supported.

    • Data source rules for common data model (CDM) folders in a dataflow, are not supported.

    • Rules for datasets that use dataflows as their source, are not supported.

    • If the data source defined in a rule is changed or removed from the item it points to in the source stage, the rule will not be valid and the deployment will fail.

    • If the parameter defined in a rule is changed or removed from the item it points to in the source stage, the rule will not be valid and the deployment will fail.

    • After deploying a paginated report with a data source rule, opening the report using the Power BI Report Builder isn't supported.

    More details: Get started with deployment pipelines 

     

    If it doesn't help, please provide a simple sample with the same issue.

     

    Best Regards

    Community Support Team _ Polly

     

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

     

     

     

  • Anonymous one more option worth checking- if you configured rules after deploymen, they will only be effective after the next deployment, and not immediately.

    if that's the case, it might be that the reason you are seeing the 'different' is because of those unapllied rules that are waiting for the next deployment.