Forum Discussion

msturzen's avatar
msturzen
Frequent Visitor
4 months ago
Solved

SQL Operator with multiple destinations

Hi all,  a few weeks back I was happy to read the SQL Operator for Eventstream is GA AND supports multiple destinations.  I tried to add a second destination to an existing SQL Operator. That doe...
Eventstream
  • msturzen's avatar
    msturzen
    3 months ago

    As of today 2026-05-11, it works. 
    I wasn't able to get my client to raise a support ticket, so out of curiosity I just retried --> voila, it works perfectly fine. 

    I guess I will never know what the root cause was: feature not rolled out yet, or some kind of defect. 

    Thank you Anonymous  for your help, your ideas and your support. 

    Best

    Martin

Anonymous's avatar
Anonymous
Not applicable
4 months ago

Hi msturzen ,

Looking at your query, one thing stands out inside MappedEvents you reference FilteredEvents but the CTE is defined as FilterEvents (no d). That typo could be causing the backend validation to fail and surface as an output binding error. Worth fixing that first and republishing.

If it still fails after that, it may be a tenant rollout issue. You can check by raising a support ticket by using this link
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn  they can confirm whether multi-destination SQL Operator is fully enabled in your tenant.

Thanks,
Akhil.

 

msturzen's avatar
msturzen
Frequent Visitor
4 months ago

Hi Akhil, 
good find! I double checked with the prod code. --> It's a typo that must have sneaked in when I prepared the snippet. 
Will try the support ticket next....

Best

Martin