Allow personal bookmarks to be displayed on the report canvas
Please add a visual or extend the bookmark navigator to display the signed-in user’s personal bookmarks as a clickable list directly on the report canvas. Report viewers should be able to create and access their own saved views without needing report editing permissions or opening the Bookmarks pane. This would make it easier for customers to switch between their saved filter selections directly within the report.
Allow multi-column conditions /output in Power BI Activator rules (Power BI visual-based alerts)
Description: When I create an Activator alert from a Power BI report visual, the rule can only evaluate the single column or measure it was created from, and the alert can only reference that same value. This blocks common governance and monitoring scenarios. Example scenario: I wanted an alert for Dev workspaces that sit on a billable (Premium/Fabric) capacity. That needs a condition on both Workspace Name (contains “Dev”) and Capacity/Billing type (not blank). Activator can’t combine the two in one rule, so I had to build the alert in Power Automate with a DAX query instead. Limitations: A condition can use only one column or measure, with no AND/OR across several attributes. The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner. There’s no way to run a DAX query as the rule logic. Requested improvements: Conditions across multiple columns/measures (AND/OR). Selectable output fields, so the Teams or email action can include several columns, and dynamic links. Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does. Impact: Without this, governance and monitoring alerts need a separate Power Automate flow, which is harder to build and maintain than a native Activator rule.
Allow monitoring DAX queries in Activator
Please allow viewing and editing the DAX query that powers PBI alerts in Activator! This would make Activator much easier to use. It would allow for much more flexibility if Activator allowed directly viewing, setting and editing the DAX query that produces the data object to be monitored. This would allow us to include more than one column in the dataset to use in Activator (which would make it 10x more useful). It would also make it much easier to understand what data is actually being monitored, make it clearer to the user that the alert is independent of the visual, and make it possible to update alerts to target different data. We have many tools for creating effective DAX queries, including the view in PBI desktop.📉 How Would You Investigate a 20% Drop in Revenue?
A data analyst shouldn’t stop at identifying what happened. The real questions are: Where did the decline occur? → Why did it happen? → What caused it? → What should we do next? By analyzing regions, products, customers, time periods, and key business metrics, raw data can reveal the root cause behind the numbers. Good data analysis turns numbers into decisions. 📊 #DataAnalysis #BusinessIntelligence #PowerBI #MicrosoftFabric #DataAnalytics
Provide Exactly-Once Triggering for OneLake File Events
Currently, a single completed OneLake file can generate duplicate events and trigger the downstream Fabric pipeline multiple times. Filtering on data.api = FlushWithClose helps identify completed file writes, but it does not guarantee exactly-once delivery. The recommended workaround requires every pipeline to implement event claiming, deduplication, status tracking, concurrency handling, and idempotent processing. This creates significant complexity for a basic event-driven ingestion scenario, particularly when many files or pipelines are involved. Expected behavior: One completed file → One valid event → One pipeline execution Please provide one of the following: A built-in deduplication option for OneLake events An exactly-once trigger mode A unique, stable deduplication key with native pipeline support A configurable option to trigger only once for each finalized file This enhancement would simplify event-driven ingestion, reduce unnecessary pipeline executions, and improve scalability. Duplicate Event-Based Triggers for Same OneLake File Despite Filtering on data.api = FlushWithClose | Microsoft Fabric CommunityAdd Dry-Run Simulation and Historical Event Replay for Fabric Activator Rules
Fabric Activator should provide a dry-run simulation mode that allows developers to test rules against historical or sample event data without executing real downstream actions. Activator rules can trigger operational actions such as notifications, pipelines, workflows, and other automated processes. Before deploying or modifying these rules in production, teams need a safe way to understand exactly how the rule would have behaved against real data. Activator should allow users to select a historical time range, Eventstream data, or sample event set and replay those events through a rule in simulation mode. During simulation, Fabric should evaluate the complete rule logic but suppress external actions. The simulation experience should show: Which events would have matched the rule Which events would not have matched Why each condition evaluated to true or false The exact time each activation would have occurred Which downstream action would have been invoked The parameters that would have been passed to the action Duplicate or repeated activations Suppression, cooldown, and timing behavior Errors or missing fields encountered during evaluation Total simulated activations for the selected period Users should also be able to compare the behavior of the current rule with a modified version before publishing the change. For example, an operations team may change an equipment-temperature rule from 90 degrees to 85 degrees. Before deploying the change, they should be able to replay the previous seven days of telemetry and see how many additional alerts and actions the new rule would have generated. This would make it possible to regression-test Activator rules before production deployment and reduce the risk of alert storms, incorrect pipeline execution, excessive notifications, and unintended automation. A reusable simulation API would also allow teams to include Activator rule validation in automated CI/CD testing.
Allow Bookmarks to Affect Multiple Report Pages
Description: I would like to request the ability for a single Power BI bookmark to affect and maintain a state across multiple report pages, rather than being limited to a single page. For example, a bookmark could simultaneously apply filters, slicers, visual visibility, or other supported bookmark states across several pages of the same report. This would be particularly useful when creating different report views or user scenarios. For example, selecting an "Executive View" bookmark could automatically apply the predefined state across the Overview, Sales, Operations, and Finance pages. This functionality would make bookmarks more powerful for multi-page report navigation and scenario-based reporting, while reducing the need to create and maintain separate bookmarks for each page. Requested enhancement: Allow a single bookmark to store and apply supported bookmark states across multiple report pages within the same Power BI report.
Gestión. Visión artificial. Biometría. Automatización. Datos. Integración.
Estamos empezando a mostrar algo mucho más grande: una plataforma construida para llevar la Inteligencia Artificial al mundo real. Gestión. Visión artificial. Biometría. Automatización. Datos. Integración. Desde capturar una imagen y convertirla en información, hasta utilizar ese dato para ejecutar, controlar, auditar y mejorar un proceso real. Desde crear un dataset y entrenar un modelo, hasta desplegarlo dentro de una operación. Desde una pequeña empresa que necesita resolver un problema concreto, hasta una industria que necesita integrar IA sobre su infraestructura existente. Ese es el concepto detrás de Origen Ingenio: IA que observa. IA que entiende. IA que se integra. IA que actúa. Y algo que para nosotros es fundamental: la tecnología no debería determinar quién puede innovar. Una persona. Una necesidad real. Una idea. Y hoy, una capacidad tecnológica que hace pocos años requería estructuras enormes. Esto recién empieza. 🌐 origeningenio.com ORIGEN INGENIO De la imagen al dato. Del dato a la decisión. De la decisión a la acción.Add an End-to-End Production Reference Architecture for Microsoft Fabric Real-Time Intelligence
I would like to see a complete end-to-end Microsoft Fabric Real-Time Intelligence reference architecture that demonstrates how the individual RTI capabilities work together in a production-oriented solution. A manufacturing or operational telemetry scenario could show the complete flow from Eventstream through Eventhouse and KQL, Real-Time Dashboards, Activator, Power BI, Fabric Data Agents, and other applicable Microsoft Fabric capabilities. The guidance should explain architectural responsibilities, latency and retention choices, schema evolution, replay, security, governance, monitoring, CI/CD, environment promotion, connection management, and troubleshooting. It would also be valuable to explain when deterministic KQL queries, rules, or Activator actions should be used before introducing AI or agent-based processing. This would help architects, developers, students, and community learners understand how to move from individual Fabric RTI features to a governed and production-ready real-time solution.RLS mismatch when assigning multiple regions in semantic model live connection.
Hello Community, I am facing an issue with Row-Level Security (RLS) in a Power BI report connected to a semantic model (live connection). I created RLS roles based on region-wise access. When I assign a user access to a single region (e.g., Brazil), the data displays correctly. However, when I assign the same user access to an additional region, the data for the first region starts showing mismatches. The formulas are correct, and the user has all required data permissions. Interestingly, if I give the user Contributor or Admin access at the workspace level, they can see all regions correctly. But the requirement is that the user should only have Viewer access, not workspace-level permissions. Has anyone faced this issue before? Is there a way to fix this so that users with Viewer access can see multiple regions correctly without needing workspace-level roles? Thanks in advance for your guidance!
