Dynamics 365 Journeys Create a Record Tile: Setup, Permissions and Dataverse Limits

Before this, one Dynamics community answer to a "create a custom record from a journey" question suggested a workaround. It was to add a custom trigger at the right point in the journey, which starts a Power Automate flow in the background to create the record. The new tile replaces that detour for eligible tables.

What the tile does​

Authors can create phone calls, tasks, leads, opportunities and custom entities directly from the journey canvas. Microsoft says the aim is timely follow-up and better conversion. Its documentation example is a high-value lead who downloads a whitepaper. That lead triggers a phone-call activity for a sales rep, with the relevant context attached.

The roadmap scenario goes cross-team. A contact clicks a "Request Support" link in an email, and the journey creates a prepopulated case in Dynamics 365 Customer Service. That is a roadmap scenario. Whether a given table is available still depends on the eligibility and permission rules below.

Field configuration​

• Required fields appear by default, and you must fill them in before you can save and publish the journey.
• Optional fields come from a searchable list via + Add optional fields. The list includes writable custom fields. It leaves out system-managed fields such as Created On and calculated fields.
• Each field can take a static value or dynamic content pulled from Dataverse data about the contact, lead, trigger or related records.
• If dynamic content can't be resolved at runtime, for example a contact with no phone number, the field is left empty.
• Optional-field selections are saved per user, per session, not globally.
• During the preview, Microsoft noted that choosing the lead record type prefills standard attributes such as name, email and address from the journey audience.

Ownership​

For tables that support ownership, the new record's owner can be set in four ways:

1. The contact or lead owner.
2. The parent account owner.
3. A specific user or team.
4. A dynamic value.

If the parent-account owner or dynamic value can't be resolved, the contact or lead owner is used instead. For leads and opportunities, Dynamics 365 Sales assignment rules take precedence over the owner set in the journey. Territory and distribution logic therefore still wins.

Limits: "any record" has conditions​

The roadmap's "any record or activity" wording needs qualifying:

• It works only for journeys on contacts and leads. Customer Insights – Data profiles are not supported.
• The target table must have a relationship to the contact or lead.
• Event-planning entities (prefix msevtmgt_) and entities with the prefix msdyncrm_ are not supported.
• The picker lists only tables where the publisher and the service role both have the needed permissions.

Admin checklist​

Turn it on​

Go to Settings > Overview > Feature switches and find the Record creation toggle in the Journey section. During the preview, the toggle was off by default. If you had already enabled the older "Lead and opportunity creation" toggle, that setting was still respected. I haven't verified what the default is now that the feature is generally available, so check your tenant.

Permissions​

Dataverse requires two principals to pass the checks: the journey publisher and the dedicated Create Record Role Extensible service role. Creation succeeds only if both pass.

• Built-in tables (Lead, Task, Opportunity, Phone Call): the service role already has what it needs. The publisher needs Create, Append, AppendTo and Assign on the target table. The publisher also needs AppendTo on entities referenced by lookup fields, such as account or contact.
• Custom tables: these are not in the default role. Add Create, Append, AppendTo and Assign, at least at business-unit level, to both the publisher's role and the service role. Do this under Settings > Security > Security Roles, on the Custom Entities tab. Also add AppendTo on every table a lookup field points to.
• Custom lookup on a built-in table: if it points to a table the default role doesn't cover, both roles need AppendTo on that table.
• Older role: Marketing Service User Extensible still works. To get the new visibility behavior, migrate any custom-table privileges to Create Record Role Extensible.

Microsoft explains the Append/AppendTo pair this way. Setting a lookup creates a link between two records, so Dataverse needs Append on the child and AppendTo on the parent. Without both, record creation fails at runtime.

Default record-creation settings​

Settings > Customer engagement > Create record settings lets admins predefine field mappings so authors don't rebuild them each time. Each setting is tied to a table and a target audience (Contact or Lead).

• The Lead table ships with two defaults: one for a Contact audience and one for a Lead audience.
• Every other table needs a manually created setting.
• You can edit a setting's name and mappings later, but not its table or audience.
• Each business unit can have only one enabled setting per table-and-audience combination.

Where it can still fail​

Publishing a journey does not guarantee the records get created. Microsoft says validation catches many common configuration issues but cannot check every runtime business rule or customer-specific customization. That includes plug-ins and workflows. Failures can also come from missing permissions, required data or unresolved dynamic values.

Troubleshooting​

• Table missing from the picker. Check for a relationship to the contact or lead, and for an unsupported prefix. Then check Create permission at business-unit level or higher on both the publisher's role and the service role.
• Lookup field missing. Both roles need Append on the source table and AppendTo on the target table.
• Records not created. Review the journey execution details and logs for the Create a record step. Confirm that required fields and the runtime data behind dynamic content exist.
• Dynamic fields empty. Re-check the selected field and relationship path. Test with a contact or lead known to have a value. Add default values or branches for missing data.

After go-live, journey analytics show the created records, link to them, and expose failure details.

Analysis​

This is a useful simplification for organizations that already run Dataverse-centric marketing and sales. It removes a class of "glue" flows that often become fragile and undocumented. The tradeoff is that the work moves into security-role design. A tile that quietly hides tables because the service role lacks a privilege will confuse authors until someone checks the roles.

My practical advice is to pilot one scenario, such as a pricing-request lead creating a phone call. Check the ownership and assignment-rule behavior. Run it with a small sample audience, and confirm the records appear before you widen the audience. That advice is my own reading of Microsoft's guidance, not a vendor requirement.

Also note that Microsoft's release-plan page for this feature carries an archived notice from October 2026. It says to use Microsoft Learn for authoritative product guidance and the roadmap for current plans.