Five overlooked Dataverse features that still add practical value
Diesen Beitrag auf Deutsch lesen
Dataverse includes useful capabilities beyond the maker portal, including Outlook integration, Exchange email, diagnostics, field mappings and multi-table lookups.
TL;DR
Dataverse supports Outlook record association, Exchange Online email without Power Automate flows, a diagnostics URL for model-driven app performance, classic-interface field mappings during record creation, and multi-table lookups. Field mappings require matching compatible types and do not propagate later parent updates; custom multi-table relationships require SDK or XrmToolBox configuration.
Original by Nick Doelman, on ReadyXRM Blog. Read the original
This is our own summary, not a republication or full translation.
Governance takeaway
- Makers: Use field mappings when creating related records to populate compatible fields automatically, but do not expect later parent changes to update children.
- Makers: Run the model-driven app diagnostics URL regularly so performance changes can be compared over time.
- Admins/CoE: Review Exchange Online integration, mailboxes and queues before building email flows that consume flow runs or require specialized service accounts.
- Admins/CoE: Treat custom multi-table lookups as a controlled design choice because the source says their setup is limited to SDK or XrmToolBox rather than the maker interface.
Frequently asked questions
Do I need a Dynamics 365 license to use the Dynamics 365 Outlook connector?
No. According to the author, anyone with a Power Apps license is fully entitled to use it.
What is the advantage of native Exchange Online integration in Dataverse?
It lets you send and receive emails from Power Apps without a Power Automate flow, so flow run allocations are preserved, and it needs no special service account.
How do Dataverse field mappings work and what are their limits?
Mapped values are copied to a new related record, but only at creation and only for matching field types of equal or smaller size. Later parent changes do not cascade.