Thank you THANK YOU for implementing shared and certified datasets in the Power BI service! Since any new workspace can potentially be used to store promoted and certified datasets, once a user starts publishing reports from those datasets in other workspaces, it seems difficult to see in which workspace the dataset actually resides. When looking at the "View Related" information for the published report, it would be very helpful if the workspace for the dataset were referenced in the Datasets section of that window. For example: If I publish a report called "Awesome Report" and its source is a certified dataset called "True Source" in a separate workspace called "Amazing Workspace", when I click the "View Related" icon for the report, I would like to see under DATASETS "True Source (Amazing Workspace)" This would tell me not only what the name of the dataset is, but the workspace in which it lives.
1 Comment
- fbcideas_migusrNew MemberStatus added:Needs Votes
Recent ideas
Allow us to rename fabric data agents published to m365
If we use deployment pipelines to promote fabric data agents between dev, test/UAT, and prod fabric workspaces, we need to keep the name of the fabric agent the same in each workspace. If we want to ...PeterDaniels40 minutes agoAdvocate IIINew176Views0likes2CommentsMake workspace and item session persistence optional
Description The new persistent session behavior in Microsoft Fabric should be optional rather than forced. Currently, Fabric remembers the workspaces and items that were open in my previous session...TeemuMultanen1 hour agoAdvocate INew292Views47likes2CommentsSupport Encrypted Sensitivity-Labeled Excel Files in Power Query
Description Currently, Power Query Online and Power Query in Excel are unable to access encrypted Excel files. Excel files with sensitivity types other than Public or Non-Business can be encrypted a...ewarstdhyjugkhi2 hours agoMicrosoft EmployeeNew16Views6likes0CommentsAuto-propagate Lakehouse (Direct Lake) permissions to users assigned to a Power BI App audience
Problem When a Power BI report uses a Live Connection to a Direct Lake Semantic Model, end users must have explicit ReadAll / ReadData permissions on the underlying Lakehouse (or its SQL analytics e...majofv4 hours agoNew MemberNew5Views1like0Comments