Create Your Own Custom Triggers Without Any Code in D365 Marketing

*** NOTE: ALL INFORMATION IS ACCURATE AT DATE OF PUBLISHING ***

If you’re on at least version 1.84.2011.0 of D365 Marketing, and you’ve tried to create a Trigger, you might have already noticed there is now a second option available. The ability to create a trigger that can be used in conjunction with a custom app or website, or tied to a flow in Power Automate, will still be there. The new option is the ability to create a trigger that will be activated based on a record within Dataverse (D365) such as a new record created, or an existing record being updated. Let’s take a look at how to create and then use a trigger based on an existing record being updated.

To get started, add a new trigger and give it a name. Make sure the first option is selected, and then click Create.

Next, look for the table you want to link the Trigger to. In this example we are going to use the Contact table.

Now we need to select the audience. You might be tempted to pick the first Contact option from the list, but that one would then prompt you to pick a type of Contact (based on a lookup) such as a Parent or Guardian field, or a Manager field on the Contact. Instead, we pick the one that shows via self, meaning directly from the Contact record.

Now we need to set when the trigger gets activated. This can be when a new record (Contact) is created, or when an existing record (Contact) is updated, or either of those two things.

In this example we will use when an existing record is updated. Then we need to pick one or more columns (fields) that will cause the trigger. I am going to have a Trigger that is fired when the Subscriber field on an existing Contact record is updated.

Now we have all of the fields complete and can go ahead and mark it as Ready to use (blue button at the top right of the screen).

Once it’s ready to use, you will see the details of the Trigger like this.

From the top right, you can now Stop or Delete it. You can Edit it AFTER clicking Stop and taking it out of the Ready to use state. We also have the option to create a journey from the Trigger. Note, this is not the only way to create a Journey and use the trigger, you can still do that by going to the Journey area and start a new Journey from there, then pick the Trigger.

Now we can see the New Subscriber Trigger is being used. This is where you need to think a little bit about the Trigger and what column(s) you set that would actually fire the Trigger. Mine is based on a change to the Subscriber field. However, I DO NOT want an email to be sent to someone if the field was changed from a Yes to a No, or was previously empty and then changed to a No. This is where adding conditions is vital. I have added a condition that the value of the Subscriber column must equal Yes in order for the Contact to be sent through this Journey. If I leave out the Condition, I will be sending emails out to people that potentially shouldn’t even be on the Journey. Once you have your conditions added, click Create.

From here, I can then just build my Journey, knowing that only Contacts who have had the Subscriber column on their record changed to Yes will go through the Journey and get an email thanking them for being a subscriber.

This new feature is awesome! The Trigger can be created by someone who isn’t technical and used immediately. Again, I stress the importance of using conditions when creating your Journeys to make sure you are still filtering to make sure you don’t send the wrong people through Journeys. Once you have that point down, you are ready to go!

---

Check out the latest post:
Send Unique Event Registration Response Emails For Each Event Using No Code

---

This is just 1 of 448 articles. You can browse through all of them by going to the main blog page, or navigate through different categories to find more content you are interested in. You can also subscribe and get new blog posts emailed to you directly.

---