tutorial requests
1295 Topics
Is creating an Azure Key Vault reference supported through REST API?
I'm trying to automate the creation of an Azure Key Vault reference I can list existing key vault connncections created through the portal using: GET https://api.fabric.microsoft.com/v1/connections However, I have not been able to create one using: POST https://api.fabric.microsoft.com/v1/connections The supported connection types response lists AzureKeyVault with OAuth2 and service-principal authentication, but I cannot find a documented working example. OAuth2 creation appears to use undocumented Power BI endpoints through the portal, while service-principal creation returns an invalid credentials error (valid credentials, rbac assigned, public open key vault..). is creating an Azure Key Vault connection/reference currently supported through a public API? If so, could someone share a working request example? Or must these connections currently be created manually through the portal?69Views1like5Comments
How are teams automating Power BI development workflows using AI agents?
I am exploring how AI agents can help automate repetitive tasks in Power BI development and data workflows. Some possible use cases: Automatically generating reports from business requirements Triggering data preparation workflows through APIs Validating datasets before publishing dashboards Detecting anomalies and suggesting improvements Automating documentation for datasets and reports I am interested in learning how developers are currently combining Microsoft Fabric, Power BI APIs, notebooks, and AI agents. What architecture patterns or best practices are you using for AI-driven BI automation?40Views0likes1Comment
Dynamic Refresh Period Per Firm - Date Slicer Shows Global Range Instead of Firm-Specific Range
Hey all, I have a transactions dataset with multiple firms where each firm needs a different data retention period. Firm A needs 12 months of history, while Firm B needs 15 months. Users are scoped to one firm at a time via RLS. The issue: Even though the fact table correctly loads firm-specific months from Snowflake, the date slicer shows the same global date range (15 months) for both firms. Current Setup: Parameters: RefreshPeriod = "12" (default months) RefreshPeriodOverrides = "FirmB:15" (firm-specific overrides) FirmRefreshCaseSQL = generates CASE WHEN FIRM_KEY = [FirmB] THEN -15 ELSE -12 END MaxRefreshPeriod = "15" (max across all firms) Data Loading: Transaction fact table: Uses FirmRefreshCaseSQL in WHERE clause, correctly loads 12 months for Firm A and 15 months for Firm B Calendar dimension: Uses MaxRefreshPeriod, loads 15 months globally Relationships: Transaction[Transaction Date] → Calendar[Transaction Date] (many-to-one, single direction) Transaction[FIRM_KEY] → Firm[Firm ID] (many-to-one) Date Slicer: Bound to Calendar[Transaction Date] Expected Behavior: When Firm A is selected: slicer shows last 12 months When Firm B is selected: slicer shows last 15 months Actual Behavior: Both firms show last 15 months because the calendar dimension is global and doesn't know which dates belong to which firm What I've Tried: ✗ Setting parameter overrides at the report level - didn't propagate to semantic model ✗ Testing with measures - confirmed fact data is correct per firm, but slicer uses calendar dimension 🔄 Current approach: Adding a "Firm-Date Availability Bridge" table with distinct (FIRM_KEY, Transaction Date) combinations to enable filter propagation: Firm → Bridge → Calendar Questions: Is a bridge table the right approach for this scenario, or is there a simpler pattern? Should I consider making the Date↔Transaction relationship bidirectional instead? (Concerned about RLS implications) Are there any DAX-only solutions that don't require model changes? Has anyone solved firm-specific date filtering without loading separate datasets per firm? Any guidance would be appreciated! Thank you!Solved106Views0likes4Comments
exportToFile: reportLevelFilters AND a single-select slicer's default value → empty page
**Setup:** Power BI Service, workspace on Fabric capacity (not PPU). Export via `exportToFile` (PPTX) from Power Automate. Server-side only — no JavaScript embedding, so `bookmarksManager.capture()` and `report.reset()` are not available to me. Report-level filters work correctly on pages without slicers on the filtered column. **Problem:** on a page with a slicer that has **Require single selection** enabled, the slicer keeps its saved default value, and my filter is applied on top of it. Since both conditions target the same column and the values differ, the intersection is empty and the page exports blank. "powerBIReportConfiguration": { "pages": [ { "pageName": "ReportSectionXXXX" } ], "reportLevelFilters": [ { "filter": "MyTable/MyColumn eq 'A'" } ] } Slicer default is `'B'`. Result: empty page. The only value that exports correctly is `'B'` —the one the slicer already holds. I understand *why* this happens: a report-level filter narrows the values available to a slicer but never changes the slicer's selection, and preexisting filters combine with the new filter using AND. With single selection enabled, the slicer can never be cleared, so the conflict is unavoidable from the report's default state. **What I'm asking:** is there anything on the API side that resolves this without editing the report? Can `defaultBookmark` or `pages[].bookmark` override the slicer's selection during export, or is single selection a formatting property of the visual that a bookmark cannot affect? 2. Is the precedence between a bookmark and `reportLevelFilters` documented anywhere? The only statement I've found is that export filters are applied *in addition to* the current report state, which reads as AND. 3. Is there any payload option that exports a page as if the slicer weren't there — a server-side equivalent of `report.reset()`? 4. Would moving the field into the "Filters on this report" pane change how the export resolves the conflict? If the answer is "no API-side option exists", a confirmation I can point to would already help — the remaining path is a report-side change (disabling single selection, or an export-only copy of ,the page without the slicer)Solved109Views0likes7Comments
Consolidation of Data from existing reports
I've created about 20 Power BI reports for 20 different customers. Because the data provided by the 20 customers is different, or provided in different formats, each is it's own report with it's own semantic model. Each one of these reports does carry some common datasets. I now need to consolidate all 20 into one report so that I can pull all the data into a Matrix by Customer and Product are in rows and Month & Year as well as Quarter & Year are in columns, like the individual reports. I started by importing the semantic models one at a time into a new Power BI report. These imported fine, but it also brought in the Common data for each report as well, Like the Date table, and the Product table. I don't need these in there multiple times, just once and I can pull these in separately. I just need the base data, the customers' data, and it won't let me delete the Common tables.Solved58Views0likes3Comments
Power BI Design Best Practices
Hello fellow developers and data enthusiasts, I've put together a comprehensive set of 12 Power BI design best practices based on my insights and explorations in the data realm. I'd love to get your thoughts and feedback on these principles! 1.Understand Your Target Audience Design a dedicated view for each sort of audience. Example: Leaders should have an executive view on what they are concerned about, whereas customers should have a low-level perspective on what they are engaging in. Before designing a view, consider the employee's kind of job; for example, providing a financial balance sheet to a non-financial employee is pointless. 2.Define Clear Objectives Always begin with an understanding of your dashboard's primary goal and the problem that needs to be solved. Example: If you're developing a sales performance dashboard, your goal may be to deliver real-time insights on revenue, sales trends, and product performance to assist sales teams in making data-driven decisions. 3.Choose the Appropriate Visualizations Choose relevant data visualizations. Example: Use a bar chart to demonstrate how different product categories contribute to overall income. Show the progression of revenue over time with a bar/line chart. A map visualization may be more successful than a pie chart for showing geographical sales data. 4.Break the problem and solve by visual Break the problem into numerous questions that address the problem, then construct each visual such that it answers at least one of the questions/doubts presented in the analysis. Example: Each visual on the Sales Dashboard should address or resolve each issue or doubt raised through the sales analysis. 5.Design with consistency Maintain consistency in design, layout, and formatting throughout every component of the dashboard for a consistent user experience. Example: Make ensure that all charts and graphs use the same color scheme or pattern of similar data points across several visuals (i.e., Profit – Green color, Loss – Red color) and maintain organizational design standards all over the dashboard. 6.Use Reports/Dashboard in the appropriate place. Develop reports when an in-depth and comprehensive examination is required, and dashboards when quick overview, executive summaries, and real-time monitoring is required. Example: Report: (Descriptive & Diagnostic Analysis) In Sales Report, what has happened in the past two years and why it has happened should be addressed. Dashboard: (Predictive & Prescriptive Analysis) In Sales Dashboard, with minimal information about what has happened and prescribing what to do in future to solve this can be addressed. 7.Ensure visibility. Maintain users informed of ongoing activities, such as data loading or refreshing. Example: Using icons or a progress bar to illustrate the state of a data refresh process, as well as indications to identify when they were last updated (to demonstrate how old the data is). 8.Design with freedom. Allow users to quickly customize data with filters, slicers, and interactive components. Allow users to rollback or undo actions. Example: Providing filter choices for date ranges (e.g., particular dates, quarters, or years) to enable different data analysis, giving drill-down charts for exploring data, and allowing users to reverse changes by providing Back navigation and clear slicers options where necessary to undo an operation. 9.Use Meaningful and Contextual Labels. To provide context and improve understanding, use clear and descriptive labels for charts, graphs, and filters etc. Example: Use terms like "Monthly Revenue Trends" or "Sales by Region" rather than "Revenue Data" or "Sales Information" instead of generic labels. 10.Use white space effectively. Make thoughtful use of white space to improve readability and identify important details. Example: To avoid congestion and promote understanding, space out graphics and text sections. 11.Improve user Engagement. To increase user involvement and study, use interactive components like as filters, slicers, and tooltips. Example: Include data slicers that allow users to filter data by date ranges or category of products, allowing for customized analysis. 12.Help the user. With pop-ups and documents, assist the user in understanding the action they are performing. Example: Including help icons with precise documentation, as well as providing tooltips to visualizations that explain the relevance of individual data points or trends. I believe these practices are crucial for creating impactful and user-friendly reports. However, I'm eager to hear about your journeys. Have you found similar principles effective? Do you have additional tips to enhance Power BI design? Your feedback is invaluable! Feel free to share your thoughts or suggest any other practices you've discovered during your expeditions in the realm of Power BI. Let's collaborate and further enrich our data voyages together!Solved21KViews2likes4Comments
Can I Create or Modify Power BI Report Visuals from React?
Hello Microsoft Team, I have integrated a Power BI Embeded report into my React application using the Powerbi-client-react package. Currently, if I need to: Add a new visual Delete a visual Change chart type Change visual properties (colors, titles, formatting) Modify the report layout I must open Power BI Desktop or Power BI Service, make the changes, publish the report, and then embeded the report in React reflects those changes. My requirement is different. I want users (or developers) to make these report UI changes directly from the React application, without opening Power BI Desktop or Power BI Service. My questions are: 1. Is it possible to create new Power BI visuals directly from a React application using powerbi-client-react or any other Microsoft-supported SDK/API? 2. Is there any Microsoft API or SDK that allows modifying report layouts, visual formatting, or adding/removing visuals from React and saving those changes back to the Power BI report? 3. If this is not supported, what is the recommended Microsoft approach for implementing this requirement? Thankyou.Solved276Views0likes5Comments
Missing "Show data point as a table" in Power BI Service for a map visual
I have a report created in Power BI Desktop and published to the Power BI Service. The report contains a Bing map visual with bubbles sized by the number of wagons at various stations. Issue: In Power BI Desktop, when I right-click on a bubble, I see and can use the option "Show data point as a table." However, in the Power BI Service (web version), this same right-click option is missing. The context menu does not show it at all. Steps to Replicate: Publish the report with the map visual to Power BI Service. Open the report in a web browser. Right-click on a bubble on the map. Observe that the option "Show data point as a table" is absent. Additional Context: I have confirmed that this is not a report structure issue. When I download the same report from the service and open it in Power BI Desktop, the right-click option works correctly. I've also been told that this option was available in the service for this report in the past. Question: What could be the cause of this discrepancy, and is there a solution or a workaround to provide this functionality to web users? Is this a known limitation or a recent change in the service?Solved269Views1like4CommentsFree ways for students to try AI + MCP + Power BI development (semantic models & reports)
A group of students wants to experiment with “vibe coding” Power BI files — editing semantic models (TMDL/PBIP) and reports using some IA terminal or directly in Visual Studio Code using AI agents. They don’t have any paid AI subscriptions (no Claude, no Copilot Pro, etc.) and we’re looking for completely free (or generous free-tier) solutions. Tools like pbi-cli (by Mina Saad) and pbir-cli (by Kurt Buhler) look excellent for letting AI directly manage semantic models and PBIR reports, but they seem to work best with a Claude Code subscription. Are there good ways to run these tools for free, or better zero-cost stacks? What the students want to do: Open Power BI projects in VS Code or using some free agents using the terminal Use AI to create/edit DAX measures, relationships, tables, and report visuals Connect AI agents via MCP or similar Experiment with Git version control on Power BI work Any recommendations for free resources or setups? Tutorials / YouTube playlists Microsoft Learn modules GitHub repos with examples Free AI options (Gemini CLI, GitHub Copilot free tier + MCP, Cline, Ollama + local models, etc.) Classroom-friendly stacks that have worked with students This could be a great hands-on opportunity for them to explore modern Power BI development. Any help or shared experiences would be awesome!Solved1.8KViews0likes8Comments
Copilot in embedded Power BI reports via iframe
Hello collegues, We are looking into enabling Copilot for Power BI reports embedded in our web application via iframe, but we want to make sure we test it safely before enabling anything in production. Our embedded reports are customer-facing and use Row-Level Security to keep each customer’s data separate. Some reports may also contain business data and PII. Our intended approach is to use a dedicated demo workspace, create two demo customer accounts, configure RLS so each account can only access its own customer data, and then test Copilot inside the embedded iframe report. We want to confirm that Copilot only uses data available to the signed-in user and cannot return data from another customer’s scope. We would like to understand: 1. What settings are required to enable Copilot inside embedded Power BI reports via iframe? 2. Can Copilot be enabled only for the demo workspace, selected reports, and selected demo users? 3. If we enable the required tenant/capacity data processing setting, could Copilot become available to other embedded reports or users outside the demo workspace? 4. Does Copilot fully respect RLS and Azure AD identity when the report is accessed through an embedded iframe? 5. Is this demo workspace + two demo accounts + RLS test a valid approach to verify customer data isolation? 6. Are there any additional security checks or limitations we should consider before moving to production? What is the best approach for such task? I would appreciate any help! Thanks!Solved649Views1like5Comments
