Forum Discussion
Shortcut to dataflow possible?
- Anonymous1 year ago
Hi KaterinaB ,
Thank you for your interest in this case.
Dataflow does not have a manage permission option.
You can give feedback on Home .
Here is an workaround, if you want to use the dataflow processed table, you can use the destination option of dataflow Gen2 to store the data in lakehouse or warehouse, and then set separate access rights to lakehouse or warehouse.
Example steps are as follows:
Import data into Dataflow Gen2 in a workspace named FabricTest2 and process it.
Set Destination to warehouseTest1 and the data after publish will be stored in this warehouse.
Now you can share this warehouse with others and set permissions.
Another user who is not in the FabricTest2 workspace sees the following page:
Although you can not share dataflow directly with others, you can share dataflow processed data for others to use in this way.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
Hi KaterinaB ,
Thanks for the reply from FabianSchut .
I did a test:
I created a data flow in the FabricTest1 workspace, and then created another data flow in the FabricTest2 workspace. When "Get Data", select the Power Platform Dataflows connector, and you can use the processed table in the data flow of the FabricTest1 workspace.
For specific information, please refer to this official document:
Link tables between dataflows - Power Query | Microsoft Learn
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support Team
If there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!
- KaterinaB1 year ago
Helper II
Hi,
thanks for your tests. However in this scenario, you probably have access to both the workspaces, FabricTest1 and FabricTest2. What we are looking for is (we do have currently Fabric capacity running) - I create the dataflows in my workspace, another person wants to use one of the dataflow tables in their dataflow or directly in their semantic model, however they do not have access to my workspace where the dataflows are located. We are looking into the option to give access to only one dataflow and NOT to the entire workspace with all other dataflows
- Anonymous1 year agoNot applicable
Hi KaterinaB ,
Thank you for your interest in this case.
Dataflow does not have a manage permission option.
You can give feedback on Home .
Here is an workaround, if you want to use the dataflow processed table, you can use the destination option of dataflow Gen2 to store the data in lakehouse or warehouse, and then set separate access rights to lakehouse or warehouse.
Example steps are as follows:
Import data into Dataflow Gen2 in a workspace named FabricTest2 and process it.
Set Destination to warehouseTest1 and the data after publish will be stored in this warehouse.
Now you can share this warehouse with others and set permissions.
Another user who is not in the FabricTest2 workspace sees the following page:
Although you can not share dataflow directly with others, you can share dataflow processed data for others to use in this way.
If you have any other questions please feel free to contact me.
Best Regards,
Yang
Community Support TeamIf there is any post helps, then please consider Accept it as the solution to help the other members find it more quickly.
If I misunderstand your needs or you still have problems on it, please feel free to let us know. Thanks a lot!- KaterinaB1 year ago
Helper II
Thanks a lot! We had a call with Microsoft yesterday and they also recommended this solution. They said we should preferably only use the dataflows to ingest the data and store in lakehouse and share from there, not sharing the dataflow directly