You’re not missing anything — this is a real functional gap in Real-time Marketing, and Microsoft has already acknowledged it internally.
You’re describing exactly what changed when Dynamics 365 Marketing moved from Outbound Marketing → Real-time Journeys.
✅ What actually happened
Outbound Marketing (legacy)
Outbound had:
You could literally:
Event Registration
├─ First Name
├─ Email
├─ Company
├─ Custom Question 1
├─ Custom Question 2
└─ ...
Everything was tabular.
Real-time Marketing (current)
Real-time registration uses a form engine, not Dataverse schema.
So instead of columns, it stores data like this:
Event Registration
↓
Form Submission
↓
Field Submissions
├─ FieldId
├─ FieldLabel
├─ Value
This is entity-attribute-value (EAV) storage.
That’s why:
This is by design — not a bug.
❌ Why Microsoft did this
Real-time Journeys uses the same engine as:
-
marketing forms
-
landing pages
-
preference centers
-
event registration
That engine supports:
-
dynamic fields
-
conditional questions
-
runtime personalization
-
anonymous submissions
Those features require schema-less storage, which is incompatible with flat Dataverse tables.
So Microsoft traded:
reporting simplicity
for
real-time flexibility
Unfortunately, events took the hit.
✅ Official Microsoft position (as of 2025)
-
❌ Custom registration fields are not flattened
-
❌ No built-in Excel export
-
❌ No Dataverse view support
-
❌ No roadmap commitment to reintroduce it
-
❌ Outbound feature parity is not planned
This is confirmed in the docs you linked.
✅ What you can do today (supported options)
Option 1 — Power Automate flattening (most common)
On registration submit:
-
Trigger flow on Form Submission created
-
Read related Field Submissions
-
Pivot values
-
Write to your own Dataverse table:
Event Registration Export
├─ Contact
├─ Event
├─ Question 1
├─ Question 2
├─ Question 3
Now you have:
-
clean views
-
Excel export
-
Power BI support
-
audit history
This is what most enterprise customers are doing.
Option 2 — Synapse Link + SQL pivot
If you use Fabric / Synapse:
Very powerful, but more technical.
Option 3 — Custom registration app
Some customers bypass Microsoft forms entirely:
Still integrate with Real-time journeys using triggers.
⚠️ What you cannot restore
There is no supported way to:
Those features were intentionally removed.
📌 Why your “bring it back” request is valid
Event management fundamentally requires:
EAV storage breaks all of that.
This is one of the most requested missing features in Real-time Marketing.
✅ Where to raise it (this actually matters)
If you want Microsoft to bring this back:
🔗 Power Platform Ideas portal
https://ideas.powerplatform.microsoft.com
Search for:
“Real-time marketing event registration export”
and upvote existing ideas.
Microsoft product team actively monitors these.
✅ Summary
You’re correct on every point.
-
Real-time events store data in EAV format
-
Custom fields are unmapped
-
No clean export exists
-
Outbound had this — Real-time does not
-
This is a known regression
Only workarounds today are:
Until Microsoft adds a flattened registration projection, there is no native fix.