When a mirroing on sql server is created on Fabric. replication and cdc is automatically enabled on the source database. However when Mirroing is deleted on Fabric, it does not autoamtcially disable the replication and cdc on the source database. I had to manually disable them on the source database. It would be effective if this is taken care when the mirrored database is dropped in fabric. Before deleting it can prompt if cdc and replication on source system can be dropped as well.   ... View more

I was thinking to start a project to build a Cross-Platform Mobile App (iOS & Android) using Flutter, dedicated specifically to the Microsoft Fabric community. The goal is to provide a central hub for tracking updates, community discussions, and learning resources on the go. ​I am currently in the infrastructure planning phase and designing the data schema. Below is the technical roadmap I’ll be following to bring this from an idea to the app stores.   Phase 1: Architecture & Data Schema ​Schema Design: Defining entities for Users, Community Posts, Knowledge Base articles, and Certification tracks. ​Backend Selection: Using Firebase for real-time synchronization and authentication, integrated with Azure Functions to fetch official Fabric updates. ​Phase 2: UI/UX & Brand Identity ​3D Integration: Leveraging my background in 3D motion graphics to create a high-end, cinematic Splash Screen and interactive UI elements using Rive for Flutter. ​Design System: Adopting Microsoft’s Fluent Design System principles to ensure the app feels like a native part of the Fabric ecosystem. ​Phase 3: Flutter Development (The Core) ​State Management: Implementing BLoC (Business Logic Component) to ensure the app is scalable and testable. ​Clean Architecture: Separating the app into three layers: ​Data: Repositories and Data Sources (API/Firebase). ​Domain: Use Cases and Entities. ​Presentation: UI Widgets and ViewModels. ​Networking: Using the dio package for robust API handling and interceptors. ​Phase 4: Testing & Quality Assurance ​Unit & Widget Testing: Ensuring every button and logic flow works across different screen sizes. ​Integration Testing: Testing the end-to-end flow from login to data retrieval. ​Phase 5: CI/CD & Production ​Deployment Pipeline: Setting up GitHub Actions for Continuous Integration and Continuous Deployment. ​App Store Optimization (ASO): Preparing the Google Play Store and Apple App Store listings with high-quality visuals. ​Monitoring: Using Firebase Crashlytics and Google Analytics to monitor performance and user engagement post-launch. ​I’d love to hear your thoughts! What features would make your life as a Fabric professional easier? ​Looking forward to building this together! ... View more

In T-SQL, the IDENTITY property is a powerful feature for automatically generating unique values, often used for primary keys. This capability is currently missing in Fabric Lakehouse, and enabling it would be highly beneficial. I understand that IDENTITY has been introduced for Fabric Data Warehouse tables; however, the seed value cannot currently be reset or modified. It would be great to see these enhancements included in the coming months.   ... View more

It would be helpful if the slicer could pass-through NO data when nothing is selected so that downstream visuals don't return errors or consume resources trying to ingest all the data. Currently the slicer treats the "all selected" and the "none selected" states as identical, returning the full data. This is needed and desirable in many situations. The slicer could have an option where the behavior of the "none selected" state could be set to "same as all selected" or could be set to "no data selected". This would allow the report designer to match the behavior to the need. For example, if the full data breaks the limits of a downstream graph, leaving the slicer unselected would leave the graph empty instead of displaying an error. Then, once at least one selection is made in the slicer, the selected data would be passed as normal. There are some situations where this can be accomplished with measures, but they are clunky and not always possible. ... View more

We use fabric and have a workspace app containing fabric bi reports. We've noticed that the filters "remember" the user's last filters applied even if the BI reports are saved and published with a certain state. This is specifically a functionality of a workspace app and perhaps the browser's caching. Users have to click on the green "Reset filters" arrow icon to revert to the default state of the BI report. ... View more

Hi,   I think it is ridiculous that this has been requested since at least 2020, still there is no possibility to customize the messages users see when opening a Power BI report that they do not have access to (only works for workspace apps so far). It doesn't seem like such a complicated feature to add relative to its importance. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Custom-quot-Request-Access-quot-pop-up-button/idc-p/4451875  Pushing this once again..   Best Regards ... View more

Problem: Fabric notebooks don’t expose Created/Modified DateTime and User in the UI, making governance and audit difficult. Why it matters: Required for internal audit, incident analysis, CI/CD traceability. Current workaround: Admins must use Purview audit logs or APIs, which are not accessible to all developers. Proposed solution: Display Created On / Created By / Last Modified On / Last Modified By in: Notebook properties Workspace item list Impact: Improves governance, reduces admin dependency, aligns with Power BI behavior. ... View more

It is possible for an SVG canvas background to have no issues when imported in Desktop, display in the service the same, but then will fail when exported to PDF. I've encountered this with attr() which I use to make customisable background templates, but in theory this could also apply to any new development to the web platform. I tested the latest version of my template in desktop and on the service, but did not think to test with exporting as I'd assumed the background appearance was fixed at that point. The export error only came to my attention when a different export error was queried. I suspect that different versions of WebView are at play, but whatever the cause the capabilities should be matched where appropriate. This is also affected by the recent decision to change the default canvas size. The entire point of using attr() in the first place in my template is so I can change the dimensions of the SVG template to match the canvas, then attr() can read this and automatically place certain elements. Since SVG doesn't natively let you place elements relative to the bottom or right of the canvas, CSS that lets you keep elements in those places needs to know the canvas size. Hence the attr() trick. But this isn't about one capability in particular - no doubt things will advance and future capabilities will emerge that will prove useful. But report authors should be confident anything they have tested in one place will work everywhere. ... View more

When using Dataflow Gen2 in Microsoft Fabric, parameters behave differently depending on how the Dataflow is executed, even when the same parameters and values are used. After detailed investigation and confirmation with Microsoft Support, we observed the following inconsistent behavior: Direct Dataflow execution (via Dataflow UI): When a query or query-related logic is passed as a Dataflow parameter, the Dataflow correctly re-evaluates the query and adapts the schema accordingly. Pipeline-triggered Dataflow execution: When the same parameter is passed from a Pipeline to the Dataflow, the schema is not re-evaluated or adapted, even though the parameter values are identical. Internally, the Pipeline appears to execute the Dataflow using a different execution path / mashup handling mechanism than a direct Dataflow run. This leads to schema mismatches, mashup document errors, or an inability to support dynamic query logic when triggered via a Pipeline.   Why This Is a Problem From a user perspective, Dataflow parameters should behave consistently, regardless of whether the Dataflow is executed directly or via a Pipeline. Currently, solutions that work perfectly in a direct Dataflow run break when orchestrated via Pipelines, even though Pipelines are the recommended orchestration mechanism in Fabric. This limits the ability to build generic, parameter-driven Dataflows that are orchestrated by Pipelines. It also creates confusion, as there is no clear documentation explaining that schema changes are only supported in direct Dataflow runs but not in Pipeline-triggered runs. Expected Behavior Parameter handling and schema evaluation should be harmonized between: Direct Dataflow Gen2 runs Pipeline-triggered Dataflow Gen2 runs If a Dataflow supports schema adaptation based on parameters, this behavior should be identical regardless of the execution method. Alternatively, if there are technical limitations, these should be explicitly documented, including guidance on supported design patterns. ... View more

Problem In Power BI today, any custom visual that supports Advanced Edit Mode (for example Deneb, Charticulator, and other editor-style visuals) loses access to standard Focus Mode. Clicking the Focus Mode icon no longer performs the expected behaviour of zooming the visual to fill the canvas. Instead, it immediately opens the visual in Advanced Edit Mode. This behaviour is imposed by the Power BI host and cannot be controlled by the visual developer. As a result: Report consumers cannot use Focus Mode to inspect complex visuals Authors and viewers experience inconsistent UX compared to native visuals Visuals that are primarily analytical (not always being edited) pay a usability penalty simply because they support editing Why this matters Editor‑style custom visuals are increasingly used far beyond initial authoring: Deneb visuals are often parameter‑driven, interactive, and fully dynamic at run‑time Charticulator visuals are commonly consumed, not edited, by report viewers These visuals benefit more than native visuals from Focus Mode due to: Dense layouts Custom scales Fine typography Responsive rendering However, today users lose Focus Mode entirely for these visuals — even though an explicit Edit command already exists in the visual’s context menu (three dots). Requested change Please allow standard Focus Mode to remain available for custom visuals that support Advanced Edit Mode. Possible implementation options (any of these would work): Decouple Focus Mode from Advanced Edit Mode Introduce a capability flag that allows: Focus Mode = zoom only Edit Mode = editor lifecycle Allow visual developers to specify: “Advanced Edit via menu only” “Do not hijack Focus Mode” This would preserve: Expected Power BI UX Backwards compatibility Editor functionality for advanced visuals Who benefits Power BI report consumers (better analysis experience) Advanced report authors Custom visual developers Popular certified visuals such as: Deneb Charticulator Other authoring‑capable custom visuals This is a platform‑level improvement that enables more powerful visuals without reducing usability. @dm-p  ... View more

Hi,   We currently have a lot of dataflows gen1. We use 3 environments in our deployment pipelines (DEV - TST - PRD). Our company is investigating to upgrade our dataflows from gen1 to gen2.   However, we noticed we cannot use the deployment rules on dataflows gen2. Can you please fix this, or at least tell us how we can use dataflows gen2 such that the parameters are automatically adjusted on the TST and PRD environment like we have now for dataflows of gen1. We dont want to copy dataflows gen 2 to TST and PRD and manually adjust the parameters there, because it feels very stupid and we have a greater risk that somebody forgets and dataflows update with the wrong info from the wrong environment (or don't update at all) overnight. ... View more

Currently, Power BI Desktop supports display units such as Millions and Billions, but it does not provide Indian numeric units like Crores, Lakhs, and Thousands. These units are widely used in India for financial, business, and government reporting. Adding them would make Power BI more user-friendly for Indian users, improve localization. This feature would enhance adoption and usability in the Indian market, aligning Power BI with regional reporting standards. ... View more

For debugging and testing pipeline activities during development, allow us to select one or multiple activities and run only the selected pipeline activities.   For example, I'm working on editing a Notebook, and now I want to run the pipeline with that Notebook, but I don't want to run all the activities in the pipeline because that is time consuming.   I'm aware of the Deactivate activity option that already exists, but that requires Editing and Saving the pipeline as well. Instead, I just want to select which activities to run interactively by highlighting those activities and click Run, without needing to Edit/Save the pipeline.   An option to 'Run from selected activities' would also be great - select one or more activities, and run the selected activities and all subsequent activities. ... View more

Within the PowerBI Subscriptions I would like the message to be both longer, as well as rich text.  I would be nice to send a link (Approval letter, etc.) within the email blurb that gets sent out.  OR to add an additional bit of rich text information that can be added to below the snip screen of the Subscription Email. Also, it would be nice if you can copy and paste a group of emails from an email or distribution list in Outlook. ... View more

It's incredible that we still don't have the option to control the favorites buttons to actually determine which favorites we want to display in the button visual.   We need an update to this component to improve our DataViz.   Let's say, for example, that I have 12 Indicators, but in the button I only want to select 6 to be displayed/selected.     ... View more

Here's what’s happening with Word Wrap enabled in a column with a long name in the header: Columns 1–20: Header word wrap works as expected. Columns 21+: Header word wrap stops working as expected; ie header text wraps but the row height does not adjust, so the part of the title that's wrapped to the second line gets partly hidden.. Tested it by moving the column with long header to the range of the first 20 colums => all fine.  Move it back to where I want it (24th place) => issue as described (wrap ok, but row height of header not ok) Seems a good idea to have this fixed so all columns behave in the same way. Txs, Koen ... View more

I I've just began a subscription to have data from the UMHS patient care dashboard sent to me each morning. It would be much more helpful if all of the data showed on the screen, what I'm saying, only goes down to room 52 and I would like to see all the rooms on our unit without having to login. It is missing room 53 and 54 .  ... View more

The current narrative paragraph format relies heavily on dense text with bolded names and figures, which makes it difficult to quickly assess what is performing well versus where attention is required. Key insights are embedded within lengthy sentences, reducing their visibility and potentially diluting the intended message. Adopting a more structured, bullet‑based format would allow the most critical takeaways to stand out immediately, enabling trends, spend concentration, and potential risk areas to be identified at a glance.   Overall Spend Total FY‑2026 spend: £x.xxx Direct spend: £xxx.xM Indirect spend: £xxx.xM Regional Spend Distribution Spend primarily concentrated in: NAM: £xxx.xM Europe: £xxx.xM APAC: £xxx.xM Smaller shares within the top 10 company codes: LATAM: £xxx.xM MEA: £xxx.xM Spend by Division John Crane: £xxx.xM Smiths Detection: £xxx.xM Interconnect: £xxx.xM Smiths HQ: £xxx.xM Smiths BIS: £xxx.xM Supplier Concentration Top vendor groups include: Interroll Holding AG: £xxx.xM Federal Express (FedEx): £xxx.xM Smiths Group PLC: £xxx.xM UPS: £xxx.xM Top Spending Company Codes SD Germany GmbH: £xxx.xM Smiths Detection Inc: £xxx.xM John Crane – Czech Operations: £xxx.xM John Crane USA: £xxx.xM SIA: £xxx.xM ... View more

Bookmarks can currently be modified using a few checkboxes, the selection pane, and the filters pane. This can be an incredibly painful design experience, depending on what you are trying to do. Here are some of the current pain points: There is no way to automatically select all visuals that a bookmark affects when it is set to affect only selected visuals. If you are updating a bookmark and miss a visual, you have to start back at the beginning. There is no way to select a subset of filters for a report, page, or visual that the bookmark should affect. This is especially unhelpful for "reset" type bookmarks, where we might want to reset only a few fields but keep others that the user has set. Another application of this would be resetting all visual-level filters but keeping all page-level filters. Bookmarks interact with drill-through-applied filters differently in PBI Desktop than in PBI Service. In Desktop, creating a bookmark with the drill-through filters cleared will not re-clear them on navigation, whereas on publishing the same report to Service, that same bookmark will clear the drill-through filters. This difference makes it difficult to properly design the desired user experience in Desktop. I propose the following bookmark creation / editing experience: Add a "Select Affected Visuals" option to the bookmark menu. This would ease the first pain point above. Add a pair of options, "All Filters" and "Select Filters," underneath the "Data" menu option. "All Filters" would provide the current behavior, whereas "Select Filters" should bring up a dialog listing our the report-level filters, page-level filters, and visual-level filters for the bookmark to affect. This would allow the designer to affect one filter on a visual while keeping another, even for the same field and visual. This could be similar to the "Edit Interactions" experience, where checkboxes appear in the filters pane when the "Select Filters" option is selected, to allow the designer to use the familiar navigation tools for filters and have no question about which visual is being referred to. It would be nice if drill-through filters appeared on the filters pane between page-level and report-level filters to better match the PBI Service view. This would also be more intuitive; some designers I have interacted with (myself included) initially thought that drill-through filters needed to be set on the source visual, not the target page, since they appear on the visualizations pane. ... View more