Propoperties Issue - "Value" instead of list of columns

[MorenaBI]

Hi,

I'm trying to set up an alert on my power bi report based on a table. I generate the alert by clicking on the table. When I try to edit the activator object and add addtional properties, instead of list of columns I see "value". Any ideas?

When I try to create a new object based on the power bi report stream, I also see the same, so a new object can't be created.

[v-pnaroju-msft]

Hi MorenaBI,

We would like to follow up and see whether the details we shared have resolved your problem. If you need any more assistance, please feel free to connect with the Microsoft Fabric community.

Thank you.

[MorenaBI]

Hello, I acceted the last post as a solution. Thx!

[v-pnaroju-msft · Accepted solution]

Hi MorenaBI,

Thankyou for your followup.

Based on my understanding, although all table columns may appear in the Power BI event stream for inspection, Data Activator evaluates and triggers alerts using only a single bound scalar value produced by the visual. Any additional columns that may be added as properties are treated as contextual metadata and do not participate in rule evaluation. This is why the configuration may appear valid, yet the alert may not trigger. It also explains why the setup could be created once in the user interface but never fired, since only the evaluated value is considered by the rule engine.
If column values need to reliably trigger alerts or appear dynamically in alert messages, a possible approach is to create Activator objects from schema aware sources such as Event Streams, KQL Databases, or Fabric Warehouses, where properties are fully bound for both rule evaluation and messaging.

We hope the information provided assists in resolving the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.

[v-pnaroju-msft]

Hi MorenaBI,

Thank you for reaching out through the Microsoft Fabric Community Forum.

Based on my understanding, when an Activator object is created from a Power BI table or matrix visual, Power BI does not expose the underlying column schema. Instead, the visual emits only a single evaluated scalar output. This is why the Properties section displays a generic value field rather than individual columns. This behaviour applies both when editing an existing Activator object and when creating a new one from the report stream.

At present, column level alerting directly from table or matrix visuals is not supported. Only visuals that return a single numeric value, such as Card, KPI, and Gauge visuals, or structured sources such as Eventstreams, KQL databases, or Fabric Warehouses, can expose schema aware properties.

If column level properties are required, the supported alternatives are to convert the logic into explicit measures and trigger the Activator from a Card or KPI visual, or to route the data through Eventstreams or KQL, where the schema is preserved.

If exposing Power BI visual columns directly in Data Activator is important for your scenario, we recommend submitting a feature request on the Fabric Ideas portal using the link Fabric Ideas - Microsoft Fabric Community

Additionally, please refer to the links provided below for further information:
Create Power BI alerts and refine them in Fabric Activator - Microsoft Fabric | Microsoft Learn
Set data alerts in the Power BI service - Power BI | Microsoft Learn
Assign data to objects in Activator - Microsoft Fabric | Microsoft Learn
Create Activator rules - Microsoft Fabric | Microsoft Learn
What is Fabric Activator? - Microsoft Fabric | Microsoft Learn

We hope the information above helps to address your concern. Should you have any further queries, please feel free to reach out to the Microsoft Fabric Community.

Thank you.

[MorenaBI]

It seems that it works differently. I have all columns from the table chart in the stream. I wanted to add additional properties to the alert message, that's why I need this.

What is interesting, once while I was clicking and trying to set it up, I managed to add properties and set up a client column as an object with additional properties. But this settings do not triger the alert at all.