2 versions · feature-create-a-record-tile.md
v2last monthmarkdown import
… 3 unchanged lines …## Key facts- Enabled per environment: **Settings** > **Overview** > **Feature switches** > **Journey** > **Record creation**. The old preview toggle was called **Lead and opportunity creation (preview)**; an environment that had it on keeps the feature on.- Works on **contact-based and lead-based journeys only**. Customer Insights – Data profiles aren't supported.- - You can only target tables that have a relationship to contact or lead. Event-planning tables (`msevtmgt` prefix) are excluded outright.- - Two principals must both hold the privileges: the **journey publisher's** security role, and a dedicated service role called **Create Record Role Extensible**. If either is missing the privilege, the table simply doesn't appear in the picker.+ - You can only target tables that have a relationship to contact or lead. Two prefixes are excluded outright: event-planning tables (`msevtmgt_`) and Customer Insights – Journeys' own tables (`msdyncrm_`). The second exclusion was added in September 2026 and rules out writing back to journeys' own configuration tables.+ - Two principals must both hold the privileges: the **journey publisher's** security role, and a dedicated service role called **Create Record Role Extensible**. The entity picker only lists tables and fields where **both** permission checks pass, so a missing table is a permissions symptom, not an unsupported-table one.- Required privileges on the target table are **Create**, **Append**, **AppendTo** and **Assign**, plus **AppendTo** on any table a configured lookup points at.- The built-in tables — lead, task, opportunity, phone call — are already covered by the service role. Custom tables are not; you add them by hand to both roles at business-unit level or higher.- **Marketing Service User Extensible** still works, but privileges configured there don't get the improved picker behaviour. Microsoft's guidance is to migrate custom-table privileges onto **Create Record Role Extensible**.… 29 unchanged lines …---- *Worth revisiting when Customer Insights – Data profiles become a supported audience, or if the Create Record Role Extensible migration gets a deadline*+ *Worth revisiting when Customer Insights – Data profiles become a supported audience, or if the Create Record Role Extensible migration gets a deadline. Last refreshed 2026-09-23: `msdyncrm_` added to the excluded prefixes and the dual-principal picker behaviour clarified upstream.*
v1last monthmarkdown import
Initial version.