Microsoft Power Platform & Dynamics CE Blog

Have you ever had a journey that suddenly stops triggering? You could swear it worked yesterday, but now it isn’t firing when it should. Maybe you experienced trying to publish a form or a journey and it’s taking forever until it gives you an error that doesn’t give you much information…

I have to admit, I was once (or twice) where you were (or are) and invested time to debug what was happening. Luckily, I got help from Microsoft engineers who recommended this solution—so I’m sharing it with as many people as possible. 😊

A long time ago in a database far, far away… 😁

It is a time of chaos. The mighty Dataverse is under siege by an overwhelming army of duplicate records. Accounts and contacts have been cloned endlessly, threatening to destabilize the CRM galaxy.

Armed only with an SSIS (SQL Server Integration Services) package, a brave data engineer rises to bring balance to the system. Their mission: to bulk merge duplicates, unify scattered data, and restore peace to the Dataverse.

Some months ago, I got the question if there was a way to limit the Registrations for an event to one Registration per person in Dynamics 365 Customer Insights Journeys. I thought then, that there is no setting for this, so I decided to investigate, and after some research I stumbled into this documentation of Microsoft: Customize form submission validation

Then I thought that if there is a way of validating a form before the submission, we could avoid it altogether. So I set my mind on it and after some testing and validation, I developed a Plugin that will validate the event registration by running on form Submission and will prevent the submission to be sent in case there is already an event registration.