web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Customer experience | Sales, Customer Insights,...
Suggested Answer

Event "Registration Count" - Innacurate

(1) ShareShare
ReportReport
Posted on by 4

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.

  • Suggested answer
    11manish Profile Picture
    1,459 Super User 2026 Season 2 on at

    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.

  • rajeshjamrodh Profile Picture
    64 on at

    Hi Dear as per the details share by you……if you are reporting an actual Dynamics 365 Customer Insights – Journeys issue, I would first verify the exact table/field being displayed as "Registration Count", because Microsoft has changed the event/registration data model between the older outbound marketing experience and the newer real-time journeys experience.

    Common reasons for an inaccurate count

    Cancelled registrations are included

    Duplicate registrations

    Session registrations

  • Suggested answer
    ParthPatel249 Profile Picture
    220 on at


    Interesting one, this behavior is actually by design, though Microsoft doesn't document it well at all.

    Those registration count fields in the Events module are updated by backend system logic built into the Customer Insights Journeys solution itself, not by a visible plugin, rollup field, or Power Automate flow. That's why you can't find anything in your customization layer. It's essentially a black-box internal process.

    The reason your counts are drifting is most likely because that backend logic only counts active registrations in a specific status, it doesn't necessarily count all records you'd expect it to. Cancelled, inactive, or certain transitional statuses may be excluded from the count depending on your configuration.

    The fact that manually resetting to 0 and adding a registration jumps to 9 tells me the system is recalculating from its own criteria on each update, just not matching what you're seeing in the grid.

    A few things worth checking:

    • Which registration statuses are actually being counted vs what you're filtering in your view
    • Whether any solution updates recently changed the underlying counting logic
    • Raising this with Microsoft Support, since it's internal solution logic, they can see exactly what's triggering the recalculation

    You're not doing anything wrong here, it's just frustratingly opaque. Hope that points you in the right direction! 😊

     
     


     

  • Suggested answer
    Syed Aqib Raza Profile Picture
    210 on at

    The fact that the Registration Count field is a Whole Number and isn't a rollup/calculated field doesn't necessarily mean that it is only updated by a plugin or Power Automate flow.

    In Customer Insights – Journeys, Event Management has internal logic that maintains event/session registration information. Microsoft documents the Registration Count as the number of people registered for an event, while session-level registrations are maintained separately.

    One important test here is that manually changing the Registration Count from 8 to 0 and then creating a registration causes it to become 9. This suggests the value isn't being recalculated from the current Event Registration records. Instead, the event-management logic appears to be applying an increment/decrement to the existing value.

    I would therefore avoid manually correcting the field and instead investigate the registration/cancellation processing and the current state of the related Event Registration records.

    You can also compare the count against the registrations shown under Event → Registration and attendance → Event registration, rather than simply counting all registration rows in Dataverse.

    If the value is consistently incorrect, I'd recommend opening a Microsoft support case with the Event ID and several Registration IDs where the discrepancy can be reproduced. This is likely inside the Customer Insights – Journeys event-management processing rather than something visible as a standard Dataverse plugin or Power Automate flow.
     

  • MN-01121504-0 Profile Picture
    6 on at

    Hi, 

     

    Did you ever find a solution to this? We're seeing exactly the same behaviour on our side. 

    We've had a ticket open with Microsoft on this previously, but it was closed without any concrete solution, so if you got anywhere, I'd be very interested to hear it! 

     

  • Suggested answer
    ParthPatel249 Profile Picture
    220 on at

    What you observed, setting 0 then next registration making it 9, confirms it is using internal recalculation or delta logic and not your manual value as source of truth.
    In practice the mismatch is often from status handling, where only specific registration states are counted, while your view may include inactive, canceled, duplicate, or session linked records differently.
    Best path is to stop manual edits on that count, validate using a controlled test event with known registration states, and raise a Microsoft support ticket with Event ID, several Registration IDs, and timestamps so engineering can trace the backend job.
    Also ask support explicitly for a recount or data repair for affected events because this is usually not fixable from standard customization tools.

  • Fleisada Profile Picture
    4 on at

    Thank you everyone for your responses.  I was able to work with Microsoft on this issue, and we were able to find the cause of the count issues, though I am still working with their support on some of the specifics.

    The process that updates the registration count is the plugin is  “Microsoft.Dynamics.EventManagement.CrmPlugins.EventMgmtPlugin.Plugins.UpdateRegistrationCountAsyncPlugin” and it compares the count of both event registrations and “tickets” that exist on an event.  “Tickets” refer to Event Registration Tickets, which are a related table to the Event, and I believe they are supposed to represent failed event registration submissions, however that is what we are still working with Microsoft to clarify.

    To clear up the bad count, we are able to delete the Event Registration Tickets that exist, or we can go into the tickets to look at the submission information and choose what to do with that information from that point.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Women in Power Builds Momentum

Expanding mentorship, skilling, and AI innovation

Congratulations to the August Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Customer experience | Sales, Customer Insights, CRM

#1
Syed Aqib Raza Profile Picture

Syed Aqib Raza 125

#2
ParthPatel249 Profile Picture

ParthPatel249 87

#3
11manish Profile Picture

11manish 85 Super User 2026 Season 2

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans