<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>rss.livelink.threads-in-node</title>
    <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence-forums/ct-p/dataactivator</link>
    <description>rss.livelink.threads-in-node</description>
    <pubDate>Mon, 16 Nov 2026 10:13:13 GMT</pubDate>
    <dc:creator>dataactivator</dc:creator>
    <dc:date>2026-11-16T10:13:13Z</dc:date>
    <item>
      <title>Latest value per device in KQL: arg_max, materialized view or a state table?</title>
      <link>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Latest-value-per-device-in-KQL-arg-max-materialized-view-or-a/m-p/5421038#M676</link>
      <description>&lt;P&gt;I need the latest reading per DeviceId from a large table, and arg_max(Timestamp, *) by DeviceId takes several seconds on a big dataset. A materialized view using arg_max is much faster, but I am not sure about its ongoing cost. The other option I considered is a separate latest-state table maintained by an update policy. Which approach do you use for latest value per key, and have you run into problems with either one?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 07:16:41 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Latest-value-per-device-in-KQL-arg-max-materialized-view-or-a/m-p/5421038#M676</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-16T07:16:41Z</dc:date>
    </item>
    <item>
      <title>What happens to events when an Eventstream destination is down or throttled?</title>
      <link>https://community.fabric.microsoft.com/t5/Eventstream/What-happens-to-events-when-an-Eventstream-destination-is-down/m-p/5421036#M843</link>
      <description>&lt;P&gt;I have an Eventstream reading from Event Hubs with a filter and a manage fields step before an Eventhouse destination. If the Eventhouse is slow or unavailable for a while, what happens to the events in between? Are they buffered, retried or dropped? I could not find a clear statement in the docs. How do you monitor lag and detect data loss in a setup like this?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 07:16:20 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventstream/What-happens-to-events-when-an-Eventstream-destination-is-down/m-p/5421036#M843</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-16T07:16:20Z</dc:date>
    </item>
    <item>
      <title>Activator rule keeps firing on every refresh while the value stays low</title>
      <link>https://community.fabric.microsoft.com/t5/Activator/Activator-rule-keeps-firing-on-every-refresh-while-the-value/m-p/5421032#M1077</link>
      <description>&lt;P&gt;I set up an Activator rule on a Power BI visual that sends a Teams message when a measure drops below a threshold. It fires again on every data refresh for as long as the value stays below the threshold, so the channel gets flooded. I assumed the condition would only trigger once when the value crosses the threshold, but that is not what I see. Is there a setting to alert only once until the value recovers, or is it better to use a different condition type?&lt;/P&gt;</description>
      <pubDate>Mon, 16 Nov 2026 07:16:06 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Activator/Activator-rule-keeps-firing-on-every-refresh-while-the-value/m-p/5421032#M1077</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-16T07:16:06Z</dc:date>
    </item>
    <item>
      <title>Eventhouse: update policy or materialized view for aggregates?</title>
      <link>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Eventhouse-update-policy-or-materialized-view-for-aggregates/m-p/5414353#M673</link>
      <description>&lt;P&gt;I tried two ways to get per-minute aggregates from a raw events table in an Eventhouse: an update policy that writes summarized rows into a second table at ingestion, and a materialized view using summarize by bin(Timestamp, 1m). Both feed the dashboard fine, but late-arriving events and backfills seem to behave differently. Which one do you use, and why?&lt;/P&gt;</description>
      <pubDate>Fri, 13 Nov 2026 00:51:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Eventhouse-update-policy-or-materialized-view-for-aggregates/m-p/5414353#M673</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-13T00:51:35Z</dc:date>
    </item>
    <item>
      <title>What are the best practices for processing and analyzing real-time data in Microsoft Fabric?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/What-are-the-best-practices-for-processing-and-analyzing-real/m-p/5410469#M253</link>
      <description>&lt;P&gt;I'm exploring Microsoft Fabric Real-Time Intelligence and would like to learn how other professionals handle real-time data processing and analytics.&lt;/P&gt;&lt;P&gt;When working with continuously arriving data from multiple sources, choosing the right architecture is important for maintaining low latency, reliable processing, and efficient analytics.&lt;/P&gt;&lt;P&gt;I'd appreciate practical insights on the following:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;When should we use Eventstream versus other data ingestion approaches in Microsoft Fabric?&lt;/LI&gt;&lt;LI&gt;What are the best practices for processing high-volume streaming data?&lt;/LI&gt;&lt;LI&gt;How can Eventhouse and KQL databases help with real-time analytics?&lt;/LI&gt;&lt;LI&gt;What strategies do you recommend for handling late-arriving events and duplicate records?&lt;/LI&gt;&lt;LI&gt;How do you monitor streaming pipelines and troubleshoot processing delays?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I'd love to hear about your real-world experiences, recommended architectures, and lessons learned when implementing real-time analytics solutions.&lt;/P&gt;</description>
      <pubDate>Wed, 11 Nov 2026 17:58:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/What-are-the-best-practices-for-processing-and-analyzing-real/m-p/5410469#M253</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-11-11T17:58:53Z</dc:date>
    </item>
    <item>
      <title>Eventhouse caching and retention: how do you size the hot cache for dashboards?</title>
      <link>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Eventhouse-caching-and-retention-how-do-you-size-the-hot-cache/m-p/5408112#M669</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;We ingest several million events a day into an Eventhouse and have dashboards that mostly look at the last seven days, with occasional investigations going back a year. Our current policy settings are:&lt;/P&gt;&lt;LI-CODE lang="kusto"&gt;.alter table Events policy caching hotdata = 14d
.alter table Events policy retention softdelete = 365d&lt;/LI-CODE&gt;&lt;P&gt;Dashboards are fast, but cost has grown faster than we expected.&lt;/P&gt;&lt;H4&gt;What I would like to hear about&lt;/H4&gt;&lt;UL&gt;&lt;LI&gt;How do you choose the hot cache window: by looking at actual query ranges, or by a fixed rule?&lt;/LI&gt;&lt;LI&gt;Do you keep long-term history in the same table, or move older data to OneLake and query it through a shortcut?&lt;/LI&gt;&lt;LI&gt;How do you check which queries are touching cold data and how much that costs you in latency?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;If you have numbers from before and after changing the cache window, those would be especially useful. Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2026 17:28:53 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Eventhouse-caching-and-retention-how-do-you-size-the-hot-cache/m-p/5408112#M669</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-11-10T17:28:53Z</dc:date>
    </item>
    <item>
      <title>Struggling to get alerts working as needed</title>
      <link>https://community.fabric.microsoft.com/t5/Activator/Struggling-to-get-alerts-working-as-needed/m-p/5406874#M1070</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;This is my first time using activator for alerting using a power bi dashboard and im struggling to get it to work.&lt;/P&gt;&lt;P&gt;For context the alert is set up to look at a column in a matrix table and if a row is greater or equal to 5 then to trigger an alert email, I need it to alert me to every new row hitting 5 or more AND every time it increases thereafter.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ive set it up so that the condition is "increases by 0" as this&amp;nbsp;&lt;EM&gt;apparently&lt;/EM&gt; captures all increases (i cant set a rule like increases by 1 as some rows will increase by more than 1 per reload)&amp;nbsp; and ive set a property filter for greater than or equal to 5 to limit the alert to only look at 5 or above.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried setting the main alert condition to greater than or equal to 5 and above first but this triggered once when the value met the criteria but did not trigger if the value then increased again and I need that visability.&amp;nbsp;&lt;/P&gt;&lt;P&gt;what am I doing wrong? and what is the correct way to achieve what I need?&lt;/P&gt;&lt;P&gt;thanks in advance&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 10 Nov 2026 09:42:28 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Activator/Struggling-to-get-alerts-working-as-needed/m-p/5406874#M1070</guid>
      <dc:creator>heather96</dc:creator>
      <dc:date>2026-11-10T09:42:28Z</dc:date>
    </item>
    <item>
      <title>How Do You Optimize KQL Queries for High-Volume Real-Time Analytics?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Do-You-Optimize-KQL-Queries-for-High-Volume-Real-Time/m-p/5405120#M249</link>
      <description>&lt;P&gt;As real-time data volumes grow, keeping analytics queries responsive while maintaining low-latency insights can become challenging in Microsoft Fabric Real-Time Intelligence.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'm interested in learning how teams optimize KQL queries when handling continuous streams of high-volume events.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A few areas I'd like to explore:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Which KQL optimization techniques have the biggest impact on query performance?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How do you manage high-cardinality columns and large event datasets?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;When should you use materialized views instead of querying raw event data?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;What strategies help maintain responsive dashboards during heavy ingestion workloads?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I'd love to hear practical experiences, optimization techniques, and recommendations from teams working with Microsoft Fabric Real-Time Intelligence.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Nov 2026 17:41:00 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Do-You-Optimize-KQL-Queries-for-High-Volume-Real-Time/m-p/5405120#M249</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-11-09T17:41:00Z</dc:date>
    </item>
    <item>
      <title>How Do You Handle Duplicate and Late Events in Microsoft Fabric Real-Time Intelligence?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Do-You-Handle-Duplicate-and-Late-Events-in-Microsoft-Fabric/m-p/5395752#M244</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm exploring how teams handle duplicate, delayed, and out-of-order events when building production streaming solutions with Microsoft Fabric Real-Time Intelligence.&lt;/P&gt;&lt;P&gt;For example, an application might send order updates, payment events, or IoT telemetry through Azure Event Hubs or Fabric Eventstreams into Eventhouse.&lt;/P&gt;&lt;P&gt;Under normal conditions, the pipeline may work as expected. However, network interruptions, retries, and delayed messages can introduce duplicate or out-of-order events, potentially affecting real-time dashboards and operational reporting.&lt;/P&gt;&lt;P&gt;I'm interested in how other teams are addressing these challenges.&lt;/P&gt;&lt;P&gt;A few questions:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Event Deduplication:&lt;/STRONG&gt; Are you handling duplicate events before ingestion, during stream processing, or through KQL queries after data reaches Eventhouse?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Late-Arriving Events:&lt;/STRONG&gt; How do you manage events that arrive after their expected processing window? Do you use event-time windows, allowed lateness, or downstream reconciliation?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Event Ordering:&lt;/STRONG&gt; When events arrive out of sequence, how do you ensure that dashboards reflect the latest valid business state rather than simply the most recently received event?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Monitoring:&lt;/STRONG&gt; Which metrics do you monitor to identify ingestion delays, duplicate processing, or unexpected gaps in streaming data?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Recovery:&lt;/STRONG&gt; How do you handle replayed events or source reconnections without producing inaccurate analytics?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Architecture:&lt;/STRONG&gt; Where should these reliability controls live—in Eventstreams, Eventhouse/KQL, or the downstream applications consuming the results?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I'm particularly interested in practical implementations involving transaction monitoring, IoT telemetry, application logs, and real-time operational dashboards.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;For production workloads, is it better to preserve raw events and deduplicate during querying, or perform deduplication as early as possible in the ingestion pipeline?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Would appreciate any architecture examples, KQL approaches, or lessons learned from real-world deployments.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 05 Nov 2026 09:56:10 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Do-You-Handle-Duplicate-and-Late-Events-in-Microsoft-Fabric/m-p/5395752#M244</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-11-05T09:56:10Z</dc:date>
    </item>
    <item>
      <title>How Are Teams Turning Real-Time Data into Automated Business Actions?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Are-Teams-Turning-Real-Time-Data-into-Automated-Business/m-p/5389377#M242</link>
      <description>&lt;P&gt;Real-time data is valuable, but its real impact comes from how quickly organizations can turn incoming events into meaningful business actions.&lt;/P&gt;&lt;P&gt;With platforms like Microsoft Fabric Real-Time Intelligence, teams can monitor streaming data, identify important events, configure alerts, and respond to changing conditions. However, connecting these insights with actual business workflows remains a challenge.&lt;/P&gt;&lt;P&gt;For example, organizations could automate operational notifications, trigger follow-up processes, route tasks to the right teams, and use AI-driven workflows to reduce manual intervention.&lt;/P&gt;&lt;P&gt;I'm interested in understanding how different teams are approaching this.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;How are you using real-time events to trigger automated workflows?&lt;/LI&gt;&lt;LI&gt;What challenges do you face with event detection, alert reliability, and downstream integrations?&lt;/LI&gt;&lt;LI&gt;Are you combining real-time analytics with AI agents to support faster business decisions?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;For organizations exploring this broader approach, AI business automation solutions can help connect intelligent automation with everyday business operations.&lt;/P&gt;&lt;P&gt;Would love to hear about practical implementations and lessons learned.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Nov 2026 20:01:07 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-Are-Teams-Turning-Real-Time-Data-into-Automated-Business/m-p/5389377#M242</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-11-03T20:01:07Z</dc:date>
    </item>
    <item>
      <title>Deduplicating streaming events in Eventhouse: materialized view or update policy?</title>
      <link>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Deduplicating-streaming-events-in-Eventhouse-materialized-view/m-p/5377659#M664</link>
      <description>&lt;P&gt;Hi everyone,&lt;/P&gt;&lt;P&gt;I'm looking at how to handle duplicate events in an Eventhouse table that is fed from an Eventstream. The source can resend the same event (same EventId) after retries, so the raw table will contain duplicates.&lt;/P&gt;&lt;P&gt;The two options I keep coming back to are:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1. A materialized view that keeps the latest record per key&lt;/STRONG&gt;&lt;/P&gt;&lt;LI-CODE lang="none"&gt;.create materialized-view with (backfill=true) EventsDedup on table RawEvents
{
    RawEvents
    | summarize arg_max(IngestionTime, *) by EventId
}&lt;/LI-CODE&gt;&lt;P&gt;&lt;STRONG&gt;2. An update policy into a clean table&lt;/STRONG&gt;, filtering out EventIds that already exist, combined with a short retention on the raw table.&lt;/P&gt;&lt;P&gt;What I'm unsure about:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;At high ingestion rates, does the materialized view keep up reliably, and how do you monitor how far behind it is?&lt;/LI&gt;&lt;LI&gt;Update policies only see the newly ingested batch, so duplicates arriving in different batches can still get through. Is there a common pattern to handle that, or is option 1 generally the safer choice?&lt;/LI&gt;&lt;LI&gt;For downstream Power BI reports in DirectQuery, is it better to query the materialized view directly, or wrap it in a stored function?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;I'd be interested in how others approach this in practice, especially at higher volumes.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Tue, 27 Oct 2026 19:38:15 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Deduplicating-streaming-events-in-Eventhouse-materialized-view/m-p/5377659#M664</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-10-27T19:38:15Z</dc:date>
    </item>
    <item>
      <title>Edge device detections into Fabric: Eventstream + Eventhouse, or Lakehouse?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Edge-device-detections-into-Fabric-Eventstream-Eventhouse-or/m-p/5375115#M233</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;While working on a computer vision project at DataToBiz, we built the edge side of a real-time system, and I’d like to compare notes with people here on how the data side would work in Fabric.&lt;/P&gt;&lt;P&gt;On the edge, the detection runs on a Raspberry Pi. We used YOLOv8n with ByteTrack to track vehicles across frames, plus Depth-Anything-v2 for depth estimation from a single camera so we could apply spacing rules. The model was converted to ONNX, TFLite and NCNN, and we used quantization and threading to get the speed we needed without heavy hardware. A camera, GPS and compass were synced by timestamp, so every detection comes out tagged with its time, location and direction. Post-processing smooths the detections to reduce flickering.&lt;/P&gt;&lt;P&gt;That leaves a stream of time-stamped, geo-tagged detection events from many devices, and that’s the part I’d like your input on in Fabric.&lt;/P&gt;&lt;P&gt;Would you ingest it through Eventstreams into an Eventhouse and query it with KQL, or land it in a Lakehouse and process it in batches? Where does that line sit for you when the end goal is near real-time dashboards?&lt;/P&gt;&lt;P&gt;How do you handle devices that go offline and send their events late or out of order? Do you rely on event time in the Eventhouse, or clean it up downstream?&lt;/P&gt;&lt;P&gt;For the geo side, with coordinates and direction on every event, how have you handled spatial queries and map visuals in Real-Time Intelligence or Power BI? Is it good enough, or do you still end up pre-processing the coordinates?&lt;/P&gt;&lt;P&gt;And with raw detections arriving continuously, how do you decide what to keep as raw events, and what to aggregate into something like per-location availability for reporting?&lt;/P&gt;&lt;P&gt;Would love to hear how you’d approach it.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Oct 2026 12:37:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Edge-device-detections-into-Fabric-Eventstream-Eventhouse-or/m-p/5375115#M233</guid>
      <dc:creator>kiara-mehra35</dc:creator>
      <dc:date>2026-10-16T12:37:39Z</dc:date>
    </item>
    <item>
      <title>Allow multi-column conditions/output in Power BI Activator rules (Power BI visual-based alerts)</title>
      <link>https://community.fabric.microsoft.com/t5/Activator/Allow-multi-column-conditions-output-in-Power-BI-Activator-rules/m-p/5374497#M1061</link>
      <description>&lt;P&gt;&lt;STRONG&gt;Description:&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Example scenario:&lt;/STRONG&gt;&lt;BR /&gt;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.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Limitations:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;A condition can use only one column or measure, with no AND/OR across several attributes.&lt;/LI&gt;&lt;LI&gt;The alert message or action can include only that same column. I can’t add related details like workspace name, dataset link, or owner.&lt;/LI&gt;&lt;LI&gt;There’s no way to run a DAX query as the rule logic.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Requested improvements:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Conditions across multiple columns/measures (AND/OR).&lt;/LI&gt;&lt;LI&gt;Selectable output fields, so the Teams or email action can include several columns, and dynamic links.&lt;/LI&gt;&lt;LI&gt;Optionally, the ability to define the trigger with a DAX query, as the Power Automate “Run a query against a dataset” action does.&lt;/LI&gt;&lt;/UL&gt;</description>
      <pubDate>Wed, 14 Oct 2026 09:12:57 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Activator/Allow-multi-column-conditions-output-in-Power-BI-Activator-rules/m-p/5374497#M1061</guid>
      <dc:creator>AdityaPrasad</dc:creator>
      <dc:date>2026-10-14T09:12:57Z</dc:date>
    </item>
    <item>
      <title>Fabric Activator was unable to activate your rule</title>
      <link>https://community.fabric.microsoft.com/t5/Activator/Fabric-Activator-was-unable-to-activate-your-rule/m-p/5374483#M1060</link>
      <description>&lt;P&gt;Activator encountered a problem and was unable to activate your rule.&amp;nbsp;look for the notification type listed below.&lt;/P&gt;</description>
      <pubDate>Wed, 14 Oct 2026 08:18:13 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Activator/Fabric-Activator-was-unable-to-activate-your-rule/m-p/5374483#M1060</guid>
      <dc:creator>mtimoulal</dc:creator>
      <dc:date>2026-10-14T08:18:13Z</dc:date>
    </item>
    <item>
      <title>New Power BI alert in a new Activator item shows “version not supported”</title>
      <link>https://community.fabric.microsoft.com/t5/Activator/New-Power-BI-alert-in-a-new-Activator-item-shows-version-not/m-p/5372770#M1050</link>
      <description>&lt;P&gt;I’m seeing an unsupported-version warning on an alert I created today from a Power BI report visual. I created a &lt;STRONG&gt;new Activator item&lt;/STRONG&gt; for it, selected a field as the row identifier, chose email notification, and applied the alert. When I open the new Activator item, the event says: “This event is in a version that is currently not supported. Displaying it in a view only mode.” The alert rule showed the same warning.&lt;/P&gt;&lt;P&gt;This is not an old rule I’m trying to edit. Three alerts I created last week do not show this warning. Is this a known issue or recent change? Does the rule still run in view-only mode, and is there a supported fix? I can share redacted screenshots if helpful.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;img /&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 06 Oct 2026 22:11:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Activator/New-Power-BI-alert-in-a-new-Activator-item-shows-version-not/m-p/5372770#M1050</guid>
      <dc:creator>jmars808</dc:creator>
      <dc:date>2026-10-06T22:11:46Z</dc:date>
    </item>
    <item>
      <title>Handling late and out-of-order events in Eventstream windows and Eventhouse aggregations?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Handling-late-and-out-of-order-events-in-Eventstream-windows-and/m-p/5372047#M223</link>
      <description>&lt;P&gt;I'm coming from Apache Flink, where late and out-of-order events are handled with event-time watermarks and allowed lateness. I'm trying to understand the equivalent approach in Fabric Real-Time Intelligence.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Scenario:&lt;/STRONG&gt; IoT devices send telemetry with an event timestamp. Because of network delays, some events arrive several minutes late, and occasionally out of order. I need accurate 5-minute aggregates (average and max per device) for dashboards and Activator rules.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;&lt;STRONG&gt;Eventstream:&lt;/STRONG&gt; when using windowed aggregations (tumbling or hopping), are windows based on event time or arrival time? Is there a setting for out-of-order tolerance or late-arrival handling, and what happens to events that arrive after a window has closed: are they dropped, or do they produce a corrected result?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Eventhouse:&lt;/STRONG&gt; if I aggregate in Eventhouse instead, for example with a materialized view using bin(EventTime, 5m), are late events included automatically when they arrive? Any caveats with materialized views and late data?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Which layer is better&lt;/STRONG&gt; for aggregations when correctness under late data matters more than lowest latency?&lt;/LI&gt;&lt;LI&gt;&lt;STRONG&gt;Activator:&lt;/STRONG&gt; if a rule has already fired on an aggregate that later gets corrected by late data, is there a pattern for handling that, or should rules only run on finalized windows?&lt;/LI&gt;&lt;/OL&gt;</description>
      <pubDate>Sat, 03 Oct 2026 00:04:39 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Handling-late-and-out-of-order-events-in-Eventstream-windows-and/m-p/5372047#M223</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-10-03T00:04:39Z</dc:date>
    </item>
    <item>
      <title>Best pattern for keeping a current-state table in Eventhouse from Eventstream CDC?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Best-pattern-for-keeping-a-current-state-table-in-Eventhouse/m-p/5372029#M222</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;I'm streaming change data from Azure SQL Database into Eventhouse using an Eventstream CDC source. Ingesting the raw change events works fine. The question is how best to turn them into a queryable &lt;STRONG&gt;current-state&lt;/STRONG&gt; table, the way you would with a Flink CDC or Debezium pipeline.&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Setup:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Source: Azure SQL Database (CDC enabled), about 20 tables, mostly updates with occasional deletes&lt;/LI&gt;&lt;LI&gt;Eventstream → Eventhouse, raw change events land in one table per source table&lt;/LI&gt;&lt;LI&gt;Consumers: Real-Time Dashboards and some Activator rules that need the latest row per key&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;STRONG&gt;What I'm considering:&lt;/STRONG&gt;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;A materialized view using arg_max(timestamp, *) by key over the raw table&lt;/LI&gt;&lt;LI&gt;An update policy that flattens the change envelope into a typed table, with the materialized view on top of that&lt;/LI&gt;&lt;LI&gt;Handling deletes by keeping a delete flag, then filtering it out in the view or a stored function&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;STRONG&gt;Questions:&lt;/STRONG&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Is option 2 (update policy, then materialized view) the recommended pattern, or is there a simpler built-in approach?&lt;/LI&gt;&lt;LI&gt;How are people handling &lt;STRONG&gt;deletes&lt;/STRONG&gt;? Filtering the latest row by a delete flag works, but deleted keys keep taking up space. Is there a good retention or cleanup pattern?&lt;/LI&gt;&lt;LI&gt;What should I use as the ordering column so out-of-order events don't produce a stale "latest" row: the source LSN/commit timestamp, or ingestion time?&lt;/LI&gt;&lt;LI&gt;Any gotchas when the source schema changes (for example, a new column)?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Fri, 02 Oct 2026 23:07:49 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Best-pattern-for-keeping-a-current-state-table-in-Eventhouse/m-p/5372029#M222</guid>
      <dc:creator>jubinsoni</dc:creator>
      <dc:date>2026-10-02T23:07:49Z</dc:date>
    </item>
    <item>
      <title>How are teams combining AI agents with Microsoft Fabric Activator for intelligent automation?</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-are-teams-combining-AI-agents-with-Microsoft-Fabric/m-p/5369603#M217</link>
      <description>&lt;P&gt;I am exploring how AI agents can work together with Microsoft Fabric Activator to create more intelligent event-driven workflows.&lt;/P&gt;&lt;P&gt;Traditional automation usually depends on predefined rules and thresholds, but AI agents could add more context and decision-making capabilities.&lt;/P&gt;&lt;P&gt;Some possible scenarios:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Detecting business events from real-time data streams&lt;/LI&gt;&lt;LI&gt;Using AI to analyze the context behind an event&lt;/LI&gt;&lt;LI&gt;Triggering workflows based on intelligent decisions&lt;/LI&gt;&lt;LI&gt;Sending recommendations instead of only alerts&lt;/LI&gt;&lt;LI&gt;Connecting Fabric data workflows with external APIs and business systems&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;I would like to understand how developers are approaching this:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Are you using Fabric Activator with Power Automate, APIs, or custom AI agents?&lt;/LI&gt;&lt;LI&gt;What are the best patterns for handling complex event conditions?&lt;/LI&gt;&lt;LI&gt;How do you manage accuracy and avoid unnecessary automation triggers?&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Would love to hear practical examples or architecture approaches from the community.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2026 20:35:35 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/How-are-teams-combining-AI-agents-with-Microsoft-Fabric/m-p/5369603#M217</guid>
      <dc:creator>codeautomation</dc:creator>
      <dc:date>2026-09-28T20:35:35Z</dc:date>
    </item>
    <item>
      <title>Date slicer</title>
      <link>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Date-slicer/m-p/5368920#M213</link>
      <description>&lt;P&gt;Hi, I need some help with Power BI.&lt;/P&gt;&lt;P&gt;I want to use a &lt;STRONG&gt;Between Date Slicer&lt;/STRONG&gt; and display the dates in this format:&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;DD-MMM-YYYY&lt;/STRONG&gt;&lt;BR /&gt;Example: &lt;STRONG&gt;01-Jan-2020&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;I don’t want to use the default dropdown/date format. I specifically want the &lt;STRONG&gt;Between slicer&lt;/STRONG&gt; with two date inputs (From Date and To Date), but I need the displayed dates to appear as &lt;STRONG&gt;01-Jan-2020&lt;/STRONG&gt; instead of the default format.&lt;/P&gt;&lt;P&gt;Could you please guide me on how to achieve this? If the standard Power BI slicer does not support this format, is there any custom visual or alternative solution that can provide the same Between Date functionality with the &lt;STRONG&gt;DD-MMM-YYYY&lt;/STRONG&gt; format?&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 24 Sep 2026 19:34:23 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Real-Time-Intelligence/Date-slicer/m-p/5368920#M213</guid>
      <dc:creator>pradipir</dc:creator>
      <dc:date>2026-09-24T19:34:23Z</dc:date>
    </item>
    <item>
      <title>Fabric Eventstream MySQL CDC scans all databases and does not emit row-level events</title>
      <link>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Fabric-Eventstream-MySQL-CDC-scans-all-databases-and-does-not/m-p/5366400#M651</link>
      <description>&lt;P&gt;Hello Fabric Team,&lt;/P&gt;&lt;P&gt;We are testing the Microsoft Fabric Eventstream MySQL CDC connector with an AWS RDS MySQL database.&lt;/P&gt;&lt;P&gt;The MySQL instance is accessible through a private IP, and Fabric connects through a VNet data gateway/private network connection. Connectivity is successful, and the connector remains Active without reporting processing errors.&lt;/P&gt;&lt;P&gt;Our MySQL environment contains the same table structure across multiple databases, following a pattern similar to:&lt;/P&gt;&lt;P&gt;application_&amp;lt;tenant&amp;gt;.sample_table&lt;/P&gt;&lt;P&gt;We configured the source to capture only one fully qualified table:&lt;/P&gt;&lt;P&gt;application_tenant1.sample_table&lt;/P&gt;&lt;P&gt;The MySQL configuration is:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;log_bin = ON&lt;/LI&gt;&lt;LI&gt;binlog_format = ROW&lt;/LI&gt;&lt;LI&gt;binlog_row_image = FULL&lt;/LI&gt;&lt;LI&gt;The connection user has SELECT, SHOW DATABASES, REPLICATION CLIENT, REPLICATION SLAVE/REPLICA, and the required snapshot permissions.&lt;/LI&gt;&lt;LI&gt;Each Fabric source uses a unique Server ID.&lt;/LI&gt;&lt;LI&gt;CDC from the same RDS instance has previously worked successfully through another CDC platform.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;However, we are seeing the following behavior:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Although only one fully qualified table is selected, Fabric/Debezium scans schema metadata for every accessible database and table on the MySQL server.&lt;/LI&gt;&lt;LI&gt;More than 45,000 schema events were generated across the tenant and history databases.&lt;/LI&gt;&lt;LI&gt;The schema events contain DDL such as DROP TABLE IF EXISTS and CREATE TABLE.&lt;/LI&gt;&lt;LI&gt;Snapshot mode is configured as Initial.&lt;/LI&gt;&lt;LI&gt;The selected table contains approximately 16,000 records, but Fabric emitted zero snapshot r events.&lt;/LI&gt;&lt;LI&gt;We committed a new insert into the selected table after schema discovery finished, but no c event was emitted.&lt;/LI&gt;&lt;LI&gt;Eventhouse receives the schema events successfully, confirming that the source-to-Eventhouse path is operational.&lt;/LI&gt;&lt;LI&gt;The Eventhouse destination stores the Debezium payload in a dynamic column using a mapper from payload to RawEvent.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Could you please confirm the following?&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Is it expected for the Fabric-managed MySQL CDC connector to scan and publish schema events for every database when only one fully qualified table is selected?&lt;/LI&gt;&lt;LI&gt;Does Fabric expose or support settings equivalent to:&lt;UL&gt;&lt;LI&gt;database.include.list&lt;/LI&gt;&lt;LI&gt;table.include.list&lt;/LI&gt;&lt;LI&gt;schema.history.internal.store.only.captured.databases.ddl&lt;/LI&gt;&lt;LI&gt;schema.history.internal.store.only.captured.tables.ddl&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;Why would the connector finish schema discovery but not emit existing rows from the selected table when Snapshot mode is Initial?&lt;/LI&gt;&lt;LI&gt;Why are committed inserts not emitted after the schema phase appears to finish?&lt;/LI&gt;&lt;LI&gt;Is there a known limitation involving AWS RDS MySQL accessed through a private IP and VNet data gateway?&lt;/LI&gt;&lt;LI&gt;What is the recommended supported destination pattern for this CDC stream?&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;Our main objective is reliable ongoing CDC capture. We are flexible about the landing destination and can use:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Eventhouse&lt;/LI&gt;&lt;LI&gt;ADLS Gen2 in JSON or Parquet&lt;/LI&gt;&lt;LI&gt;Fabric Lakehouse/OneLake&lt;/LI&gt;&lt;LI&gt;Snowflake as the final destination&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Please let us know which logs, connector identifiers, timestamps, or additional configuration details would help investigate this behavior.&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Sat, 12 Sep 2026 09:17:46 GMT</pubDate>
      <guid>https://community.fabric.microsoft.com/t5/Eventhouse-and-KQL/Fabric-Eventstream-MySQL-CDC-scans-all-databases-and-does-not/m-p/5366400#M651</guid>
      <dc:creator>girishtharwani2</dc:creator>
      <dc:date>2026-09-12T09:17:46Z</dc:date>
    </item>
  </channel>
</rss>

