Has anyone figured out how to do custom Event Fields in CI-J? In Outbound it was part of the standard Event Management functionality. But in Realtime, you are limited to selecting the fields that are available for a marketing form. And in the Event screens, there is no longer a list view for adding custom fields for the event. Most customers would like to capture things like food type/allergies, need for disability service etc when their potential attendees are registering for an event.
Any idea on how to solve this without having to customize?
thanks Eline. The problem with this workaround is it doesn't put the data in a useful place, most of time when collecting things like dietaries it is so the event team can send over a list to the caterers, not to send some special vegan version of an email in a subsequent flow step.
Although that form fill data does live in the dataverse I'm not aware of anyway to tie it back to the event registration record to create a unified event registration list with any dietaries/accessibility requirements, unless you either created a separate form per event (really not ideal) or captured an event id on the form fill (perhaps via a url parameter, but wouldn't 100% reliable).
All of these solutions feel like clunky workarounds to what should be a simple task of capturing some custom info for an event registration. TBH, I'm not even sure if the upcoming release will solve it as it still sounds like the data won't in any way be linked to the event registration.
As Jwcpc has mentioned below, this feature has been announced for Real-time marketing as part of the Wave 2 release for 2024, and is scheduled to be available in Public Preview from February 2025.
With June 2025 and decommisoning of Outbound coming up, what is the plan to deliver it in RTM? I do not see it in any of the announced Waves. (Same goes for Event Payments btw).
It is a massive missing feature from CI-J and part of the reason we're still using OB forms for our events currently. I'm guessing the only workaround would be collecting it on the contact and then passing to the Event Reg via a Power Automate flow - but aware that's customisation
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.