Basically, there is no good way for someone building a data model in Power Query (or dataflows) to provide downstream documentation of column and table intent to consumers/users of those data models in a Semantic model context. Meta data can be attached to columns in Power Query, but there is no way to expose that meta data in the Semantic model context. Therefore, even if I document what the columns are, while building my model, I have to go back and 're-document' in the Semantic model in the description field for the column(s).
For more detals see this thread: Can I dyanmically set Column Description in Power Query
No CommentsBe the first to comment
Recent ideas
Custom visuals: allow same-tab navigation & reduce confirm-navigation friction for trusted links
Description: Custom visuals (e.g. Deneb) that trigger navigation via href currently have two limitations that create friction for legitimate, author-controlled use cases: Links always open in a ne...AlexSenEON6 minutes agoNew MemberNew2Views0likes0CommentsSeparate Download and Publish Permissions for Power BI Workspaces
Idea / Feature Request Introduce more granular permissions in Power BI to independently control report download and report publishing permissions at the workspace level. Business Scenario We have ...ewarstdhyjugkhi1 hour agoMicrosoft EmployeeNew18Views8likes0CommentsSupport Fabric SQL Database with workspace-level inbound Private Link
Fabric SQL Database supports tenant-level Private Link but not workspace-level Private Link. Securing a small number of databases therefore requires enabling Private Link across the entire tenant, in...WorkFull222 hours agoAdvocate INew30Views1like1Comment