
I’m working with Real-time Journeys and have a question regarding custom registration fields on events.
1. Editing submitted registration data
When participants register through our event form (using Real-time Journeys), I’m not seeing any way to update or change the submitted values afterwards. However, I do see that it is possible through custom unmapped fields for registration fields (outbound)..
Example:
A participant calls in and says they no longer need accommodation.
What I’m seeing is that I basically have to create a new registration with the updated value, because I cannot edit the original submission.
Is this expected behavior in Real-time events, or am I missing a place where submitted responses can be edited.
2. Migration of historical event data
We also need to migrate historical registrations from another system. However, since the custom registration fields are unmapped, it makes it difficult to map during migration. Has anyone successfully migrated historical data in a way that includes these custom registration fields per event?
Any recommended strategy for this scenario?
3. View customization issues - Auto generated "search results" view:
Inside the event record, the registration list shows an auto generated view under "Search results".
We're seeing to issues:
If we switch to a different view in the subgrid, the search result option disappears and only comes back if we refresh the entire event record.
This also makes it difficult to customize the view, and it looks like the system only allows adjusting it per event, not globally.
Ideally we need a way to set a standard view with the custom unmapped fields for all events (dream scenario would be to include columns from related tables as well..), but currently it seems lik each event has its own genereated view and manual updates per event are not practical. Microsoft support recommended to create two subgrids showing two different views, not this is not very user-friendly.
Has anyone found a way to:
1. stabilize the "search results" view so it doesnt disappear when switching views?
2. customize the default view for registrations globally across all events?
Any tips, recommendations to how to approach either of the cases would be much appreciated!!