Dynamics Community Forum Thread Details

Event "Registration Count" - Innacurate

Hello All,
I'm having problems with the registration count field in our events table, as well as the session count field in our sessions table. In both cases we are getting inaccurate counts, and I am unable to find the logic behind how that count is updated.

The field is listed as a whole number, with no roll-up or calculating logic in it. I'm not seeing any plug-ins running when registrations are added or deleted, and we don't have any power automations running when registrations are created or removed.
I have verified that the count is not incrementing as registrations are added/removed (if the count was 8, I manually set the field to 0, then add a new registration it will increase to 9). I've also confirmed on a number of events, that the number of existing registrations (active and inactive) does not match the number given. And if I add or remove an event, it changes the count, but is still inaccurate.

From research online, it looks like there is logic to automatically fill in those fields, but I'm not able to find any specifics that may help me narrow down. If anyone knows what is setting the value on the registration count field or how to find the specifics that would be greatly appreciated.

Categories:

Dynamics 365 Customer Insights - Journeys

The behavior you described—where manually changing the count is overwritten with an incorrect value after creating a new registration—strongly indicates that the count is maintained by Microsoft's internal Event Management logic, which recalculates or synchronizes the value independently of custom automation.

I recommend first confirming whether these are out-of-the-box fields used by Dynamics 365 Event Management or Customer Insights – Journeys. Then review asynchronous system jobs, Microsoft plug-in registrations, and the exact criteria used to calculate the count. Also test the behavior on a newly created event to determine whether the issue is limited to existing data.

If the fields are standard Microsoft-managed columns and the count continues to be inaccurate despite the underlying registrations being correct, this is likely a product issue or data inconsistency. In that case, gather the following before opening a Microsoft Support ticket.

Quick Links

Subscribe to this forum!