interesting links
7402 TopicsPower BI Report Usage Metrics – Workspace-Level and Organization-Level Usage
Power BI Report Usage Metrics – Workspace-Level and Organization-Level Usage Hi everyone, I am working on a Power BI governance requirement around report usage metrics, and I am trying to understand the recommended approach at both the workspace level and organization/tenant level. I have some initial understanding of the available options, but I would like to get confirmation from the community and understand if there are better/native approaches. Workspace-Level Report Usage If I have multiple reports within a single workspace, I would like to see the usage metrics for ALL reports in that workspace in one place. For example: Workspace A Report 1 → Views / Unique Viewers / Last Viewed Report 2 → Views / Unique Viewers / Last Viewed Report 3 → Views / Unique Viewers / Last Viewed Instead of opening Usage Metrics separately for each report. My understanding is that the Usage Metrics semantic model can potentially be used to create a custom usage report for the workspace. However, I would like to confirm: How exactly can we get usage metrics for all reports within a single workspace? Is there a supported way to remove/modify the report-level filtering so that the Usage Metrics semantic model covers all reports in that workspace? Is this the recommended approach for workspace-level usage reporting? Are there any limitations with this approach? Organization-Level Report Usage The next requirement is to go beyond a single workspace. I would like to build a centralized view such as: Organization → Workspace → Report → Views → Unique Viewers → Last Viewed → Other Usage Metrics For example: Organization Workspace A Report 1 Report 2 Report 3 Workspace B Report 4 Report 5 Workspace C Report 6 Report 7 All of this should ideally be available in one centralized Power BI governance report. For this requirement, I know there are some possible approaches, such as: Using Power BI/Fabric Admin Portal capabilities with the required admin access Using Power BI Admin APIs Using Power BI Activity Log APIs Building a custom data collection process and storing the information in a Fabric Lakehouse/Warehouse/SQL database But my questions are: Are these the only practical/supported ways to achieve organization-wide report usage? Is there any native Power BI/Fabric feature that already provides tenant-level usage metrics across all workspaces? Can the standard Usage Metrics semantic model be consolidated across multiple workspaces? Is there another Microsoft-supported API or Fabric capability that is better suited for this requirement? What permissions/admin roles are actually required for the different approaches? Workspace-Level vs Organization-Level I am particularly interested in understanding whether the recommended architecture is different for these two scenarios: Scenario A: Single Workspace → All Reports → Usage Metrics Scenario B: Entire Organization → All Workspaces → All Reports → Usage Metrics Would we use the Usage Metrics semantic model for Scenario A and Admin APIs/Activity Logs or another centralized source for Scenario B? Or is there a common approach that can handle both? Historical Usage Another concern is data retention. My understanding is that the current Usage Metrics experience has a limited historical window, with the new Usage Metrics experience retaining 30 days of data. If we need to retain usage information for: 6 months 1 year Multiple years what is the recommended approach? Would this be the appropriate architecture? Power BI / Fabric Usage Data → API / Activity Log / Other Source → Fabric Lakehouse / Warehouse → Historical Usage Table → Centralized Governance Dashboard Or is there a Microsoft-native approach that can retain this historical information without building our own storage layer? Final Architecture Question Ultimately, I am trying to determine the recommended approach for: Organization ↓ Workspace ↓ Report ↓ Usage Metrics ↓ Historical Usage I would appreciate guidance on: How to achieve workspace-level usage for all reports How to achieve organization-wide usage across all workspaces Whether Admin Portal/API/Activity Log approaches are the only options Whether there is a native Fabric/Power BI capability I may be missing How to handle the 30-day Usage Metrics retention limitation Recommended architecture for long-term Power BI governance and usage tracking Thanks in advance to anyone who can share their experience or recommended approach.68Views1like3Commentscopilot and power bi
Hi community, I currently have to test some reports vs excel; so in the excel software with copiltot its possible to summary the data (tables) while in power bi, the report have the same table (cloud) and if you have enable copillot in the service it's nice but this time no. is this posible to get the data from (cloud) and compare with the excel's data ? Do you know another way to test the data from different source with copilot or agent? is there AI agent to test data with power bi service and another source? Any other's ideas are welcome. Thanks in advance.53Views3likes4CommentsDeployment pipelines
Hi community , in this time, I would like to know if there is a way to rollback a deployment pipeline? I mean. I have a 1SM and 1 report A to deploy from devel to test enviroment, but I have to restoration a previous version en test. before the deploy pipeline it had made. e.g. Deploy devel -> test it going to previous version test -> devel thanks in advance.Solved4KViews0likes4CommentsPower BI Field Parameters with Paginated Reports – Looking for Guidance
Power BI Field Parameters with Paginated Reports – Looking for Guidance Hi everyone, I am trying to understand the best approach for using Power BI Field Parameters with Paginated Reports. I understand that Power BI Field Parameters allow users to dynamically switch between fields or measures in a Power BI report. My question is whether similar functionality can be achieved when working with Paginated Reports. For example, I am looking for something like: Power BI Report → Field Parameter → Paginated Report → Dynamically change the field/column displayed or used by the Paginated Report Specifically: Can a Power BI Field Parameter be passed to a Paginated Report? Can a Paginated Report consume a Power BI Field Parameter directly? Can a Field Parameter be used to dynamically determine which column/field is used in a Paginated Report query? If Power BI Field Parameters are not supported for this scenario, is there an equivalent out-of-the-box feature in Power BI Report Builder / Paginated Reports? Can this be achieved using standard Paginated Report Parameters, expressions, or dynamic query logic? Is the Paginated Report visual in Power BI the recommended way to achieve this type of interaction? For example, the desired experience would be: User selects: Customer Name OR Product Name OR Supplier Name and the Paginated Report dynamically uses the selected field/column. I understand that Power BI Field Parameters and Paginated Report Parameters are different concepts, so I am specifically trying to understand whether there is a supported way to achieve the same dynamic field-selection experience in Paginated Reports. If anyone has implemented this scenario, I would appreciate guidance on the supported approach and any limitations. Thanks!45Views1like2Commentspasting code
I have just asked a question, and used the code tags, as you would for 'forum', but on viewing it does not look very copy / paste friendly, which was the point of sharing, is there a better way or is there a way to view the entire code as it would appear in a formatter, not much point iin formatting before posting if it's just going to be converted to a single long line RichardSolved66Views2likes3CommentsDAX Navigator
Hi Community, It's sharing knowledge more than asking a question. Ever leave Power BI just to look up a DAX function? I built DAX Navigator, an interactive Power BI report that lets you discover, explore, and learn DAX functions without leaving Power BI. ✅ Browse by category or alphabet ✅ View descriptions, syntax, and examples ✅ Access official Microsoft documentation in one click ✅ Powered by Microsoft's DAX documentation The goal: make DAX learning faster, simpler, and more interactive. 🔗 Browse it live here: https://lnkd.in/eNv4hHGG Because sometimes the fastest way to learn DAX isn't searching for a function... It's discovering it. Is it thoughtful? 👍 A kudos would be appreciated 🟨 Mark it as a solution to help spread knowledge 💡 🟩 Let's connect on LinkedIn 🟧 Feel free to join this LinkedIn Group for Data Enthusiasts.72Views4likes4CommentsPower BI M-Query with TVF execution issue
Dear Team, I have designed a report in Power BI it is art of a Tableau to Power BI migration. I have separated the visuals among three pages with drill through option. It is working as expected but facing a slowness. So I think to use a benefit of M-Query with TVF passing parameter values to make pushdown query. parameter value is a single parameter and accept a comma separated values from 1st page visual. However I have created TVF. TVF is executing properly in DB side. But when I create a bind parameter and associated with my column make it text and enable multi option to get multiple values . Now I write a code snippet let VP=if P_param= null or P_param= "" or P_param= "XXXX" then "ALL" else if Value.Is(P_param, type list) then Text.Combine(List.Transform(P_param, Text.From), ",") else Text.From(P_param), SQL_Query = "SELECT * FROM MY_TVF('" & VP & "')", Source = #table({"Generated_SQL"}, {{SQL_Query}}) in Source This code has been written to check whether the selected parameter from visual VP=1001 is passing properly in TVF. Objective: 1. SELECT * FROM MY_TVF('1001,1002') (if multiple value selected from visual) 2. SELECT * FROM MY_TVF('1001') (if single value is sent) But when I click from visual using drill through feature the TVF is showing always SELECT * FROM MY_TVF('ALL') - The drill through fields when I put in the 2nd page then it is showing proper values . but it is not passing in the TVF so query is not executed it returns blank. My objective is from 1st page matrix visual when I select record one by one accordingly the value will pass and show the result. In matrix 1st column is A1 and A2 is the second column. A1 & A2 are also in drillthrough bucket. A1 can contain multiple A2. so when one A1 is selected then multiple comma separated A2 has been passed in TVF. A2 is an id field. and when A2 column it self selected then single value will pass. But value is not passing and I am not getting the benefit of query pushdown by M-Parameter. The A2 column is parameter binded. it is a text field. P_Param= A2. (bind to A2) . multiple accepted. could you please check and provide any assistance? I have tried all possible options but no results has been encountered. Regards Jishnu Bhattacharya73Views2likes3CommentsIssue with table visual on Power BI Desktop
I am having an issue with Power BI Desktop table visualization. This problem started last week and i did not face this issue during August 2026. The visual shows how clean the data looks which is from August 2026 on the left but the one I have is from September 2026 and the table visual looks super weird which is on the right. I want to fix my table visual so it looks like the one on left! Most of my visuals have been acting stramge as well Really need help as I need to create a report which is due by wednesday! thank you in advance70Views1like6CommentsHow do you usually troubleshoot slow Power BI reports?
I work as a Power BI Analyst at Edoxi, and through my work with Power BI reports and data visualisation, I’ve found that report performance is not always related to dataset size. Even a relatively small model can become slow because of complex DAX measures, inefficient relationships, too many visuals, or expensive Power Query transformations. When troubleshooting performance, I usually start by checking these areas: Data model — Check whether the model is structured appropriately, such as using a star schema where suitable. DAX measures — Review calculations and iterators that may be unnecessarily complex. Relationships — Check cardinality, filter direction, and any ambiguous relationships. Visuals — Look at the number of visuals and interactions on the report page. Performance Analyzer — Identify which visual or query is taking the most time. Power Query — Review expensive transformations and check whether query folding is maintained where applicable. I’ve found that identifying the actual bottleneck first is more effective than changing multiple parts of a report at the same time. For other Power BI professionals and analysts, what performance issue do you encounter most often: DAX, data modelling, Power Query, or report design?126Views0likes7Comments