Large Dataset Pointing to Production workspace in dev pipeline

[CourtneyMcG]

Is there an easy way to change the source settings for a dataset that is pointing to production sources in the production workspaces of a deployment pipeline to point back to development workspace sources? We use a large dataset and previously managed copies on desktop. We recently implemented pipelines and realized when you publish in dev over the copy - that copy is then pointing to production sources. Trying to find an easy work around.

Thanks! 

[aj1973]

Hi @CourtneyMcG 

Create a Dev Workspace, Publish the pbix and its report into it(Sources Dev enviroment) then create the Pipeline. Deploy to a new Test Workspace and change the rule to point the dataset to Test environment source. From there deploy to Production but choose the Workspace Prod that is already in place(Created).

[CourtneyMcG]

@aj1973 The dev workspace is already created unfortunately where this report lives as well as it's sources, as we pushed the deployment backwards from prod. Are you stating to recreate the dev workspace? The report/dataset exists in dev, but it is pointing to production workspaces because we saved over it before we realized the desktop version is pointing to production sources since we never utilized pipelines before. This is a massive dataset with multiple dataflows that exist in mutliple workspaces that we need to change from it pointing to production to it pointing to the development sources in the development workspaces.

[aj1973]

So the dataset's source are Dataflows that are located in different WS!!!

It sounds like you to need reorganize because Piplines doesn't work cross workspaces.

[CourtneyMcG]

@aj1973 they do work across different WS. When sources are deployed backwards first, then you deploy the workspace with the dataset backwards, they will connect across different WS correctly to DEV sources/TEST/production accordingly. The issue is we saved over the dev copy with a production desktop file and now need to get it back to those DEV workspaces. This was organized in 2019 before the soon to be folder functionality and audiences that prevented us from storing all in one WS.