Two-way sync for data fields (Dynamics 365)

Christoffer Utterborn
Christoffer Utterborn
  • Updated

Set up data field mapping in Dynamics 365

PREREQUISITES

Before you can map data fields, you must first install, connect, and assign roles for the Oneflow for Dynamics 365 integration.

Make sure you have the Oneflow Admin role assigned to access the Oneflow settings page.

RELATED ARTICLES

Data fields let you populate your Oneflow contracts with data from Dynamics 365 entities. The primary purpose is to transfer data from Dynamics 365 into the contract when it's created. Optionally, you can enable two-way sync so changes in Oneflow can be written back to Dynamics 365.

Navigate to data field settings

  1. In Dynamics 365, click the current app name (e.g., Sales Hub) to go to the apps page.

    Dynamics 365 App Menu
  2. Select Oneflow Administration.

    Oneflow Administration App

    NOTE

    If you use an older version of Dynamics 365:

    • If you use an older version of the integration (before 3.8.0.8), then Oneflow Settings appears under the main Settings menu in the Advanced settings page of the legacy UI of Dynamics 365.
    • If you use an older version of the integration (before 3.8.0.8) with the new Dynamics 365 UI, then Oneflow Settings appears in the side panel in the Advanced settings page of Dynamics 365.
  3. Open the Setup Entities tab. From the list on the left, select the entity you wish to configure (e.g., Opportunity, Quote).

    Setup Entities Tab
  4. Click on the Data fields sub-tab.

Configure custom data fields

Data Fields Tab
  • Dynamics entity: A related (child) entity with an N:1 relationship to the selected primary entity (e.g., creating contracts from Opportunity and pulling fields from related Contact).
  • The left panel lists primary entities you’ve enabled for contract creation.
  • The Dynamics entity dropdown lists related child entities available for mapping based on your Dynamics relationships.
  • This lets you pull data from related entities (e.g., Contact) into a contract created from the parent (e.g., Opportunity).
  • Dynamics field: A specific field from the selected related (child) entity to map into Oneflow.
  • Oneflow field: The destination data field in Oneflow.
  • Sync direction:
    • Sync once: Transfer once at contract creation. Any changes made after contract creation will not be synced back.
    • Dynamics to Oneflow: Keep Oneflow updated from Dynamics. Allows you to push changes using the Push updates to Oneflow button.
    • Two-way sync: Updates flow both ways (Dynamics ↔ Oneflow). This enables both "Push updates" and "Fetch updates".
NOTE Dynamics entities currently syncing to Oneflow are shown as Active. To activate an entity, select it in the left panel and toggle it on. You cannot activate entities from the dropdown itself.

Push updates to Oneflow

Once you change data fields in Dynamics 365, you can then sync (push) these changes to their mapped data fields in Oneflow.

  • To push updates, click the Push updates to Oneflow button on the Oneflow widget in Dynamics 365.
    • This rewrites all data field values in the Oneflow contract with data from your Dynamics data fields.

NOTE

Pushing updates to Oneflow will only update data fields with a sync direction of Dynamics to Oneflow or Two-way sync. Data fields set to Sync once will not be overwritten.

Fetch updates from Oneflow

Once you change data fields in Oneflow, you can sync (fetch) these changes to their mapped fields in Dynamics 365.

To fetch updates, click on the three dots in the contract card, then click Fetch updates from Oneflow.

NOTE

Fetching updates from Oneflow will only update data fields where the sync direction is set to Two-way sync. Data fields set to Sync once or Dynamics to Oneflow will not be overwritten.

  • As the fetch feature works using Webhooks, this is usually automated. However, you may fetch updates manually in the following scenarios:
    • Your instance missed a webhook update due to temporary technical issues.
    • The contract is still in draft state (webhook events trigger only after the contract is sent to counterparties).
    • Webhooks are not enabled for your Oneflow integration.

Limitations

Although bidirectional data synchronization is a powerful tool, it comes with a set of limitations.

  • Two-way sync direction is not available for the following field data types:
    • Lookup
    • Optionset Value
    • Unique identifier
    • Calculated
    • Multi-select optionset
    • Customer
  • It is also not possible to sync Participant or Party type data fields from Oneflow to Dynamics 365.
    • This is due to technical limitations in the way data is stored at the database level, which is different from the way it is displayed.
  • Date and time values could sync incorrectly from Oneflow to Dynamics 365 due to timezone differences. Any time value synchronized from Oneflow to Dynamics 365 is always assumed to be in UTC time.
  • Boolean properties can be synced to Oneflow using a limited set of custom text labels. Data fields containing values like Yes/No, True/False, 1, or 0 will be synced to a boolean property in Dynamics 365 while any other values will be ignored.

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request