What Revial syncs with Microsoft Dynamics 365
For your Dynamics administrator and whoever reviews the integration's data access — every Dataverse column Revial reads, everything it writes back, and the known gaps.
This page lists, column by column, what Revial reads from Dynamics 365 and what
it writes back. For connecting and admin consent, see
Connecting Revial to Microsoft Dynamics 365.
Names in code are Dataverse logical names.
Revial connects either as the user who signs in, or as an application user (Entra app registration with a client secret). Either way, that identity's Dataverse security roles decide what Revial can see and change.
1. How the sync runs
- A sync starts as soon as you connect, then runs roughly every hour. (A service account set up by Revial staff waits for the next hourly run.)
- Revial uses Dataverse change tracking: after the first sync, only changed and deleted rows are returned.
- Rows deleted in Dynamics are removed from Revial's copy.
- Revial stores each row as returned, including Dataverse's formatted values, alongside the columns mapped below.
- Disconnecting deletes Revial's synced copy of your Dynamics data.
2. Accounts
Active accounts only.
| In Revial | Dataverse column |
|---|---|
| Name | name |
| Website, phone | websiteurl, telephone1 |
| Employees, revenue | numberofemployees, revenue |
| Industry | industrycode, as its standard label |
| Description | description |
| Address | address1_line1, address1_city, address1_stateorprovince, address1_postalcode, address1_country |
| Parent account | _parentaccountid_value |
| Created / modified | createdon, modifiedon |
emailaddress1 and telephone2 are also read but not used.
3. Contacts
| In Revial | Dataverse column |
|---|---|
| First, last and full name | firstname, lastname, fullname |
| Email addresses | emailaddress1 (primary), emailaddress2 |
| Phones | telephone1, telephone2, mobilephone |
| Job title, department | jobtitle, department |
| Address | address1_* columns as for accounts |
| Company | _parentcustomerid_value |
description is also read but not used.
4. Leads
| In Revial | Dataverse column |
|---|---|
| Name, email, phones | firstname, lastname, fullname, emailaddress1, telephone1, mobilephone |
| Company, job title | companyname, jobtitle |
| Topic, description | subject, description |
| Source, status | leadsourcecode, statuscode |
| Open / qualified / disqualified | statecode |
| Owner | _ownerid_value |
5. Opportunities and stages
| In Revial | Dataverse column |
|---|---|
| Deal name | name |
| Value | actualvalue if won, otherwise estimatedvalue |
| Status (open / won / lost) | statecode |
| Stage | stepname, matched against your sales process stages |
| Win probability | closeprobability |
| Expected / actual close date | estimatedclosedate, actualclosedate |
| Account and contact | _parentaccountid_value, _parentcontactid_value |
description, statuscode and _transactioncurrencyid_value are also read but
not used.
Stages come from your opportunity sales process: processstageid, stagename
and stagecategory.
6. Mapped columns in the sync
If field mapping is configured for your organisation, the mapped columns on accounts, contacts, leads and opportunities are added to the sync and stored with each record.
7. What Revial does not read
- Activities — appointments, emails, tasks and phone calls are not synced.
- Notes and attachments (annotations).
- Owners, except on leads.
- Currency, products and quotes.
- Connections, teams and business units.
Outside the sync, Revial makes a few targeted reads: the signed-in user
(WhoAmI, systemusers), a system user by email to set an appointment owner,
appointments near a meeting's start time (sections 9.2 and 9.4), current column values
before writing, and column definitions for the settings screen.
8. Known limitations when reading
- Every amount is shown in euros, whatever the opportunity's currency.
- Only one sales process's stages are read.
- Stage-entered dates are the time of the sync, because Dynamics does not expose when the stage changed.
- Deactivated accounts stay in Revial's copy with their last values.
- Briefings do not use Dynamics activity history, since activities are not synced.
9. What Revial writes to Dynamics 365
Revial never deletes anything in Dynamics, never creates accounts, contacts or opportunities, and never closes an opportunity as won or lost.
9.1 Meeting summary note — automatic
After a meeting's summary is ready, Revial creates a note (annotation):
| Column | Value |
|---|---|
subject | "Meeting Summary – meeting title" |
notetext | The summary in your note template, a link to the meeting in Revial and an AI-generated notice. Capped at 64 KB |
| Regarding | The matched opportunity, account or contact |
- Attached to: the matched opportunity; if none, the account; if none, one note per matched contact. Admins can change this order in CRM settings.
- Written once per meeting, in your CRM output language if one is set.
- No owner is set.
Automatic pushing can be switched off for a connection by Revial support. Any team member can also push a summary manually, editing it first.
9.2 Note on the existing appointment — set up per organisation
The recommended setting for organisations using server-side sync between Dynamics and Exchange, which is the default in most Dynamics 365 + Microsoft 365 organisations.
Revial finds the appointment the seller already has for the meeting and writes
the summary as a note (annotation) attached to that appointment:
| Column | Value |
|---|---|
subject | "Meeting Summary – meeting title" |
notetext | The summary, as in section 9.1 |
| Regarding | The matched appointment |
- The appointment is matched on start time (±30 minutes by default) and on the contact, opportunity or attendees of the meeting. An ambiguous or unscoped match is refused, and completed or cancelled appointments are ignored.
- If no appointment matches, the summary is written as an ordinary note on the opportunity or account, exactly as in section 9.1.
- Revial never creates an appointment in this mode. Notes do not sync to Exchange, so nothing reaches the customer's mailbox and the seller's existing Outlook meeting is not duplicated.
- No owner is set.
9.3 Appointment — set up per organisation
Revial can instead create an appointment of its own, as well as or instead of the note:
subject, and adescriptionholding the summary or a link to it.scheduledstartandscheduledendfrom the calendar event, otherwise the recording, otherwise now plus 30 minutes.- Regarding the opportunity, otherwise the contact, otherwise the account.
- Owner set to the seller's system user, who is also the only required attendee. Customer contacts are never added as attendees — under server-side sync, Exchange mails a meeting request to every attendee on an appointment, which would send the customer an invitation containing the summary. The customer is linked through Regarding instead.
- The appointment is never marked completed.
If your organisation has server-side sync enabled for appointments, prefer section 9.2. An appointment Revial creates is synced to the seller's Outlook calendar, and if the seller's meeting is already tracked in Dynamics you will see it twice on the timeline.
9.4 Notes on a custom entity — set up per organisation
For organisations with a custom meeting-record setup, Revial finds the existing appointment for the meeting (the seller's choice, otherwise the one closest to the start time) and writes the summary, and optionally the transcript, into the configured columns — replacing what was there. It can also create the linked custom record if it is missing. This replaces the standard note.
9.5 Mapped columns — optional
Admins can map Revial summary fields and custom extraction fields to columns on contacts, accounts and opportunities.
- Revial updates the matched record only.
- A column that already has a value is left alone, unless that mapping is set to overwrite. Revial reads the current values first.
- Any column can be mapped, standard ones included.
- If a batch update fails, each column is retried once individually.
9.6 Not written to Dynamics 365
- New opportunities — deal creation is not available for Dynamics.
- Transcript notes as annotations, and tasks.
10. Privileges Revial relies on
- Read on account, contact, lead, opportunity, sales process stages and system user (organisation level).
- Create on annotation, and on appointment if Revial creates appointments (section 9.3), with Append / Append To on the tables they are linked to — including Append To on appointment, which notes on an existing appointment (section 9.2) are attached through.
- Write on any mapped columns and configured custom entities.
- Assign, where Revial sets the appointment owner.
A missing Read privilege on accounts, contacts, leads or opportunities is not skipped: the sync stops at that table and tries again on the next run.
Connecting Revial to Microsoft Dynamics 365
Finding your instance URL, connecting with Microsoft sign-in or an Entra service account, and the admin consent your IT administrator may need to grant.
Dynamics 365 technical integration guide
For Dynamics and Entra administrators, security reviewers and IT — both authentication modes, required Dataverse privileges, API consumption, failure behaviour and auditing.