Submitted on07-01-202208:12 AMSubmitted byBelieveron07-01-202208:12 AM
If I edit a dataflow and save it, there's currently no way to go back and see previous versions of that dataflow. At a minimum it would be nice to be able to retrieve eaerlier copies of the dataflow, e.g. the source code not the data. This may look/work similar to OneDrive where I can see historical versions of a file, restore them, etc. Beyond the basic ability to view/restore old dataflow versions, other common version control features would be nice such as comparing the code, etc.
... View more
Submitted on01-11-202309:56 AMSubmitted bytrt18-sistemason01-11-202309:56 AM
If you implement a dataset that uses a dataflow as datasource and they are in differente workspaces, lineage will show all dependecies between them only if you set lineage view from dataset >> dataflow. If you set lineage view from dataflow, it will not show the datasets that denpends on this dataflow if dataset is in different workspace. My idea is no matter if dataset/dataflow are at the same or at different workspaces, lineage would show all dependencies. Motivation If you follow Power BI best practices for Workspace, Dataflow and Dataset you will end up having datasets allocated in different workspace as its dataflow source. In this situation it is important to know which are the datasets that use some specific dataflow as datasource, specially to manage update schedule, access permissions.
... View more