Create Data Activator triggers in design mode


Data Activator is currently in preview.

Once you have assigned data to objects, you can create triggers to act on your data. You do this in Design Mode, which you can access from the tab at the bottom of your screen.

Define a trigger condition and action

Triggers are where you specify the values you want to select from events, the conditions you want to detect, and the actions you want Data Activator to take.

Step 1: Make a new trigger

You use the New trigger button in the ribbon to create a new trigger. You can give it a name by clicking the name of the trigger and editing it.

Screenshot of creating a new trigger.

Step 2: Select your data

The next step is to select the value for the trigger. You can either choose from a column from an event, or from a property you’ve already defined. See create Properties later in this article for information on properties.

Screenshot of selecting the data for the trigger.

Once you select a column or property, you see a preview of the values for a sample of the instances of the object.

Screenshot of a preview of the trigger values.

Step 3: Define the condition to detect

Next, you choose the type of condition that you want to detect. You can use conditions that check when a numeric value goes above/below a threshold (for example, Temperature is greater than 30), when a logical true/false value changes (for example, HasFault becomes True), or when a string value changes (for example, Status changes from InCompliance).

Screenshot of a choosing the trigger condition.

The Detect card then shows two charts:

Screenshot of a detect card showing two charts.

The first shows, for the five sampled instances, when the condition was detected. In the previous screenshot the instance labeled in yellow, RFX-9461367, crossed the threshold of 45 degrees four times.

The second chart show the total number of times the trigger would have fired, for all instances that Data Activator is tracking. There are two spikes, around 5am and 7am, where the alert was fired four times. These might not be from the 5 instances sampled in the other charts.

Step 4: Define the action to take

Finally, the act card lets you choose what to do when the condition is detected.

Screenshot of selecting an action when a condition is detected.

Different action types have different parameters, such as the email address you want to send to, the workflow you want to start, subject line or additional information etc.

Screenshot of sending a message when a condition is detected.

Test your trigger

After you have created a trigger, you can test it by selecting Send me a test alert. This finds a past event for which the trigger activation is true, then send you an alert so that you can see what the alert would have looked like for that event. Note that:

  • The test alert will always go to you, regardless of the recipient field in the Act card
  • The Send me a test alert option is only enabled if you have had at least one past event for which the trigger condition is true.

Screenshot of testing a trigger.

Start and stop your trigger

Triggers are created in a 'Stopped' state. This means they're not being evaluated as data flows into the system, and won't take any actions as a result. You also need to select Start from the toolbar for Data Activator to start running the trigger and taking action.

Screenshot of starting a trigger.

Once started, you'll see Running appears in the title area of the property.

The toolbar changes to allow you to Stop the trigger. If you make changes to the trigger (for example changing the condition it looks for), you need to select Update in the toolbar to make sure that the running trigger uses the new values.

When you delete a trigger (or Object), it can take up to 5 minutes for any back-end processing of data to complete. This means your trigger may continue to monitor data, and take actions accordingly, for a few minutes after it has been deleted.

Create properties

Sometimes, you need to reuse trigger logic across multiple triggers. This is where properties come in. You can create a property that defines a reusable condition or measure, then reference that property from multiple triggers.

To create a property, select New Property from the ribbon, then define your property logic. Here, we define a property called Maximum Temp last hour on a package object:

Screenshot of creating a property for a trigger.

Once you have defined a property, you can reference it from one or more triggers, using the select card. In the following image, we reference the property we made earlier in a Package too warm trigger:

Screenshot of package too warm property for a trigger.

You can also learn more about Microsoft Fabric: