Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
7 years ago

How to deploy dataflow from UAT workspace to production workspace

Hi Experts,

 

As I have built DataFlow in Workspace UAT and now it is the time to deploy to Workspace PRD. How can I achieve it? If it is not possible, what is the best possible solution or methodology to separate two different environments for testing and production with the use of DataFlow.

 

Thanks in advance.

 

Dataflow
Need Help

8 Replies

  • v-diye-msft's avatar
    v-diye-msft
    Icon for Community Support rankCommunity Support
    7 years ago

    Hi Anonymous ,

     

    Sorry not very clear from you post what you are looking for.  what's your datasource? Do you want to migrate the dataflow from one workspace to another?I'm afraid it's not accessible currently.

     

    • Anonymous's avatar
      Anonymous
      Not applicable
      7 years ago

      Hi v-diye-msft 

       

      Thanks for your replay.

       

      " Do you want to migrate the dataflow from one workspace to another?"

      You are right, that is what I would like to do. After some time looking for the possible options, I found export to JSON which I can export from one workspace but I cannot find a way to import to another workspace.

      Is this possible to create an entity from the exported JSON file?

       

  • Anonymous's avatar
    Anonymous
    Not applicable
    5 years ago

    Hi All

     

    Anyone have an update on this?

     

    I have found you can import the exported json file:

     

    However that only works on the first deployment.

     

    If you subsequently alter the dataflow in non-production, export the json and re-import it, PBI does not overwrite existing, it creates a new version in the target workspace e.g.

     

    First import = My Dataflow

    Second import = My Dataflow (1)

     

    Hence dependent dataset/dataflow does not pick-up the changes.

     

    If I delete the original before importing, that does not help either as dependent objects do not reference the name, they reference the GUID which changes upon re-importing.

     

    Is there a better way than having to modify dependent downstream datasets and dataflows to point to altered source dataflows?


    Deployment Pipelines are useful for reports and datasets. What about dataflows Microsoft?

     

    Thanks