Dynamics Community Forum Thread Details

Read-only toggle on forms when field is not prefilled in Customer Insights Journeys

I wanted to share a challenging scenario I’m currently facing with a client using Microsoft Customer Insights – Journeys for event management, and I’m curious if others have experienced something similar or found a solid workaround.

Context

The client organizes events using event registration forms and marketing forms. Their key requirements are very strict:

No contact data should be overwritten
No new contacts should be created via forms
Only contacts that are explicitly invited should be able to register

At the same time, they do want to capture new information for existing contacts (e.g. preferred language, which they don’t currently store but need for email personalization).

Setup

All known contact data is prefilled on the form
The email address field is set to:
- Prefill = ON
- Required = ON
- Read-only = ON

The issue
What we’re seeing is quite problematic:

Some invited contacts open the form via the invitation email
The email field is NOT prefilled for them
Despite the field being required, they are still able to submit the form
Result:
- A new contact is created without an email address
- No confirmation email / QR code is sent
- The registration is not linked to the originally invited contact

If we remove the read-only setting, users often enter a private email address, which again:

Creates a new contact
Leaves the originally invited contact without a registration

So we end up breaking both identity matching and event reporting.

Has anyone experienced similar issues with prefill behavior or required + read-only fields on event / marketing forms in CI Journeys?

How did you solve this while:

Preventing new contact creation
Ensuring only invited contacts can register
Still capturing additional data points safely?

Any insights, patterns, or even “this is a known limitation” confirmations would be hugely appreciated 🙏

Categories:

Dynamics 365 Customer Insights - Journeys

I do not have the solution, but we have something similar, and I would probably use a combination of approaches:

* there is a way how to validate & reject form submission on the backend (and still inform the Contact by showing him "error" message), so Contact knows that the submission wasn't successful. Some guidance is here: How to Prevent Duplicate Event Registrations in Dynamics 365 Customer Insights (with Form Submission Validation)s - Martin P Lopez | Power Platform Consultant so assuming that you can read from somewhere list of people who were invited, you can prevent anybody else (any other email address) so submit the form.

* to prevent overwriting your main data (name, ...), you can create a pre-validation plug-in on the contact, and whenever something attemps to modify a Contact (and something is because of form submission), then you can revert the values back to previous ones, effectively not-updating them.

Quick Links

Subscribe to this forum!