Share options for a Linked Dataflow

[PowerAuto82]

Hi,

I want to share a Data Flow from another Workspace, so I did the following:

• Went to the new Workspace
• Clicked on New >Dataflow >Link tables from other dataflows 
• Signed in using the Organizational account authentication
• Selected the Dataflow from the folder (I can see multiple Dataflows at this stage) and clicked Transform Data and then clicked on Save & close and then gave it a name for the pop up box Save your dataflow

One of the users who has access to the new Workspace wanted to connect to this Data Flow.

They opened Power BI Desktop > Get Data > Dataflows > On the Navigator page but unable to see the dataflow, they can see the Workspace and other Dataflows in this Workspace but not the linked one?

I am assuming it is because they do not have access to the Workspace that I am using the Linked Service to?

The reason I cannot give them access to the original Workspace because there is secured data on there, the dataflow I wanted them to have accss to is a trimmed down version which excludes some of the secured fields.

What is the best option now?

Thanks

[blopez11 · Accepted solution]

You are correct in that for linked tables, they need access to the source.  What you can do in the same dataflow with the linked tables, is create a reference to the linked table (right click on the linked table and select reference).  This creates a computed table.  You can then add additional transformations in the computed table or leave as is.  Save the changes, and make sure you refresh and setup a schedued refresh for this dataflow.  Your users should now see the computed tables in the dataflow.

[PowerAuto82]

Hi @blopez11 Thanks for this.

This seems to have done the trick, just to confirm there is no way the user can amend the dataflow and somehow add fields if they manage to amend this dataflow; we have tried to at our end and users are unable to Take over the Dataflow well they can Takeover but they cannot sign in as their Authentication fails.

But trying to look at different scenarios if there is posibilities of a user extracting fields they shouldn't be allowed to see.

Thanks 

[blopez11]

If you just give your consumers the viewer role on the workspace where the dataflow exists, they should not be able to modify anything in the workspace.  Glad to hear it worked.

[PowerAuto82]

@blopez11 I haven't given them any role to the workspace where the original Dataflow exisits, and it still works; so good work!