Paginated Reports with PowerQuery - Cloud connections for Snowflake connector
Current situation: Power BI report builder used to build a report using Power Query dataset. Report builder picked the right cloud snowflake DB connection (created in Power BI service portal - app.powerbi.com) However, once we deployed / published the report into power bi service portal (workspace), we are not able to see the connection it uses in the background. We only see the disabled connection settings. Refer the screenshot. It would be great if we display the cloud connection information just like how we display for semantic models. Otherwise, we have to download the rdl file from the portal and check the connection ID from the report file and fetch the connection detail from the "Manage Connections and Gateways" page from the portal settings.📉 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
Can we support Workspace ID authentication when using a gateway connection?
Currently, Workspace ID authentication is only available for cloud connections. We would like to request support for Workspace ID authentication when using gateway connections as well. <document :Authenticate with workspace identity> ---- ・You can create connections with workspace-identity-based authentication in the Manage Gateways and Connections experience for a cloud connection. ・Workspace-Identity-based authentication is currently not supported for gateway connections. ----Add Reliable Change Data Capture With Delete Detection to SAP ABAP Add-On for Copy Job
The SAP ABAP Add-On provides an important option for moving SAP data into Microsoft Fabric, but watermark-based incremental extraction is not sufficient for many production SAP scenarios. SAP tables do not always update a standard timestamp or change-date field for every business change. Deleted source records are also difficult to detect reliably through a watermark column. Please add a native change data capture option for the SAP ABAP Add-On that can reliably identify inserts, updates, and deletes without depending only on a user-selected timestamp field. The capability should maintain a restartable change checkpoint, preserve the operation type, support recovery after interrupted extraction, and expose the current change position and replication lag in monitoring. It should also allow teams to identify tables where native change capture is available and automatically recommend CDC instead of watermark processing. This would make the SAP ABAP Add-On much more suitable for production replication of large SAP ECC and S/4HANA estates and reduce the need for custom reconciliation and delete-detection logic.
Improve Oracle Mirroring Health Monitoring and Data Validation Visibility in Microsoft Fabric
Problem Statement The current Oracle Mirroring monitoring experience in Microsoft Fabric primarily focuses on replication status and operational state. While tables may display a status such as "Running", users have limited visibility into whether replication is actively processing changes, whether replication has stalled, or whether mirrored data remains synchronized with the source system. Users Impact Customers face several operational challenges: A table may continue to show a "Running" status despite concerns that replication is no longer progressing. It can be difficult to distinguish between: No source-side changes occurring. Replication actively processing changes. Replication being stalled or unhealthy. There is no built-in source-versus-target validation capability. Customers must build their own custom monitoring solutions to validate synchronization health. Data discrepancies may remain undetected until reports or analytics results are questioned by end users. Proposed Enhancements 1. Mirroring Health Dashboard Extend the monitoring experience to include: Replication health status Last successful change processed timestamp Last successful CDC transaction processed Replication activity trends Mirroring latency indicators Synchronization confidence indicators 2. Source vs Target Validation Metrics Provide optional validation metrics such as: Source row count Mirrored row count Row count variance Validation status Validation timestamp This would allow customers to quickly assess synchronization health without implementing separate tooling. 3. Replication Stall Detection Introduce proactive detection of scenarios where: Tables remain in a Running state. No data has been processed for an unexpected duration. Source activity exists but replicated activity is not progressing. Provide warning indicators and configurable alerts. 4. Enhanced Alerting Allow customers to create alerts for: Excessive replication latency Replication inactivity Validation failures Synchronization drift exceeding configured thresholds Repeated replication retries Replication health degradation
