MS Dynamics 365
Microsoft Dynamics 365 is a cloud-based CRM that focuses on intelligent customer engagement and allows companies to market and sell more productively and smarter to their customers. Native integrations to other Microsoft products make this a powerful CRM. Office 365 is Microsoft’s App suite and cloud collaboration tool and includes Microsoft Dynamics 365.
Below you'll find detailed information, specifically for Microsoft Dynamics 365 integrations:
Supported MS Dynamics 365 Integrations
This video sets up a 2-way sync between Microsoft Dynamics 365 and Chargebee.
Authorizing MS Dynamics 365
We simply ask your login details and your permission. To Authorize your MS Dynamics 365 account, we need:
- Your Microsoft Dynamics 365 'Root Service Address', to be found in the URL of your application, it should end in dynamics.com.
- Your Microsoft Dynamics API version - you can retrieve this in the settings 'About' / The first 2 numbers represent the API version.
If you already authorized Microsoft Dynamics 365 account(s) in the past or in any other PieSync integration, you'll be able to the first part of the authorization and choose from your CONNECTED ACCOUNTS.
Choose your contact type
Distinguish between Contacts, Leads or Accounts before proceeding to the configuration page.
- Learn about our contact sync below.
- More in-depth info about syncing Leads can be found here.
- More in-depth info about our Company to Company sync can be found here.
[IF] Supported Conditions/Filters
- EMAIL OPT-IN/OPT-OUT STATUS
- ACTIVE/INACTIVE STATUS
- ALREADY EXISTING IN APP YOU SYNC WITH
- CONTACT FIELDS (phone, address, ....)
- CUSTOM FIELDS
[THEN] Supported Actions
- UPDATE (CUSTOM) FIELD VALUES
Default Field Mapping
Depending on the other app you're syncing with, you'll see a number of standard Microsoft Dynamics 365 fields being mapped by default. For instance, in a connection with Google Contacts, the default field mapping looks like this:
Customizable Field Mapping
You can custom map your Microsoft Dynamics 365 Custom Fields and any additional standard fields that aren't included in the default mapping yet. Bear in mind a mapping between two fields can only exist if the types of fields are compatible and the particular compatibility will determine the direction of the mapping as well. More information on Customizable Field Mapping HERE.