Microsoft Power Platform & Dynamics CE Blog

Lead Scoring has always been a great unknown to me in Dynamics 365 Customer Insights - Journeys. I’ve known about it since the days of outbound marketing, but I never had the chance to see it implemented in a real customer project or help customers adopt it.

This article gets its inspiration from the session “The chaos of Customer Insights projects - The mistakes we keep making (and pretending we don’t)” by Vivian Voss in ColorCloud 2026. She asked the public if in their projects of Customer Insights Journeys, their clients could define what a lead is. I think only one person raised a hand. Vivian highlighted that one of the biggest bottlenecks is that marketing and sales teams often don’t collaborate closely enough.

Waitlists can be a powerful tool, but they can become difficult to manage, especially when manual processes are involved.

Handling waitlisted registrations can be straightforward, but once we involve companions, it can quickly become tricky.

Because what can we do with 2 registrations? how do we communicate the client that we have only place for one? Do we allow them to cancel one of the registrations?

In my experience, we should give as much control to attendees as possible. Luckily, this is achievable by setting up journeys and informing them via email about the status of their registration.

Events are rarely a solo experience.

In many scenarios, attendees want to bring a guest — a colleague, a partner, or a friend. But in Dynamics 365 Customer Insights – Journeys, handling “plus one” scenarios is not supported out-of-the-box.

This creates a real problem:

• Your event shows 1 registration
• But 2 people actually show up

Multiply that across dozens of attendees… and suddenly your event is over capacity.

In this article, I’ll show you how to solve this using:

Customer Insights - Journeys offers a powerful set of features: emails, journeys, segments, triggers, events, and forms.

But for many marketing teams, the challenge isn’t the lack of functionality - it’s navigating all those features efficiently.

New users often ask questions like:

Where do I start? What should I configure first? Did I miss a step?

Training sessions and documentation help, but they require users to leave the application to find answers.

A few weeks after delivering a Power Automate process that generates and stores PDFs in a Dataverse file column, my client asked for something simple:

“Can we make this process run on demand?”

That’s when I hit an unexpected limitation:

You cannot clear a Dataverse File column using “Update a row”.

I assumed it would be straightforward. But when I tried to use the Update a Row action, the file column didn’t even appear 😐

When I was a kid, I remember spending hours preparing Christmas cards by hand - paper, crayons, glitter, and a lot of patience. Writing a thoughtful message, waiting for the glue to dry, finding a stamp, and finally dropping the envelope into the school mailbox was all part of the ritual.

Today, very few people send physical Christmas cards anymore. But the intention behind them hasn’t changed: letting people know we’re thinking of them and that they matter.