Looking for something in particular?
Categories
- AI Builder 3
- Azure 10
- Canvas Power Apps 4
- Custom Pages 4
- Customer Voice 6
- Dataverse 21
- Dynamics 365 36
- Dynamics 365 Marketing 81
- Dynamics 365 Portals 11
- Dynamics 365 for Outlook 3
- JavaScript 9
- Marketing (Non Dynamics 365) 7
- Micro Enterprise Financials 2
- Microsoft Excel 2
- Microsoft Forms 2
- Microsoft PowerPoint 2
- Microsoft Teams 2
- Model-driven Power Apps 35
- Office 365 3
- OneDrive 1
- Outlook 2
- PCF & Custom Controls 14
- Power Automate 67
- Power BI 3
- Power Platform 5
- SharePoint 4
Include specific row (entity) references and all the data in Real-time marketing custom triggers
Custom triggers in Dynamics 365 Marketing (Customer Insights - Journeys) have recently became 1000 times better with the ability to include ‘Entity references’ - a way of making an entire record and all its associated records (up to 5 levels ‘deep’) available through a single trigger attribute. It works exactly the same as the ‘Contact‘ or ‘Lead’ in a trigger works, but for any table/row you choose.
This make all the data available in the trigger journeys for branching and emails for conditional content and personalisation. And you can have lots of these!
Restrict Access to Publish Journeys in Dynamics 365 Marketing
Publishing a journey sends emails out and starts all sorts of magical automations in Dynamics 365 Marketing. technical checks are built into the system but business checks are not. This post will show you how to restrict who can or cannot publish a journey without review and approval from authorised user.
Why? To give users confidence usinf Dynamics 365 Marketing and other vested parties (technical support teams, marketing & business relationship managers, leadership personnel etc.) reassurance that things are less likely to go wrong.
Hopefully this can help more customers success with Dynamics 365 Marketing!