The technical integration framework between your Association Management System (AMS) and Higher Logic is determined by the information received in this technical worksheet. This framework defines how Higher Logic interacts with the data in your AMS to create:
- member profiles,
- security groups,
- communities, and
- events.
After the integration is established, a periodic check (Periodic Refresh) for changed records in your AMS, coupled with a refresh of each updated record (Member Refresh) yields a robustly integrated ecosystem. The Periodic Refresh and Member Refresh ensure that Higher Logic has the most-up-to-date member data.
Complete the information below, providing as much detail as possible. Contact your project manager if you have any questions.
Prerequisites
- You must be on Microsoft Cloud Dynamics 365 (Dynamics 365)
- Dynamics 365 must be version 9 or above
Section I: Basic info
NOTE: This section is to be completed by the Higher Logic project manager.
| Organization Name | |
| Abbreviated/Short Name | |
| Main Website URL (www.) | |
| Higher Logic Community Site URL | |
| Higher Logic Project Manager |
Section II: Set up in Dynamics 365
The integration depends on Azure AD being configured inside your Dynamics 365 instance.
The integration must be configured in Dynamics 365 as a Client Secret on the App Registration page > Certificates and Secrets > New client secret.
NOTE: This would need to be your IT/D365 administrator, not necessarily the point of contact.
For additional information, see the following Microsoft documentation on set up.
- Use single-tenant server-to-server authentication
- Dynamics 365 Online Authenticate with Client Credentials
Section III: Web service access
To start the integration, provide the following Dynamics 365 credentials to Higher Logic.
If you have trouble finding this information, consult Microsoft Support.
| Parameter | Value |
|---|---|
| Service URL | |
| Dynamics version number | |
| Client ID | |
| Client Secret * | |
| Azure Tenant ID |
* Provide the value, not the Secret ID.
Section IV: Data mapping setup
Place a Y in the To be Synced column to indicate the fields that you want mapped from Dynamics 365 to your Higher Logic community.
NOTE: The mapping cannot be changed.
Contact details (from the Dynamics 365 'Contact' & 'Account' objects)
NOTE: In the following table, required fields are bold.
| Field Name | Data Type | Dynamics 365 Mapping/Notes | To be Synced |
|---|---|---|---|
| ContactId | string | contactid/accountid | |
| Birthday | DateTime | birthdate | |
| PrimaryEmailAddress | string | emailaddress1 | |
| Prefix | string | prefix | |
| FirstName | string | firstname | |
| MiddleName | string | middlename | |
| LastName | string | lastname | |
| InformalName | string | nickname | |
| Gender | Option Set | gendercode | |
| Suffix | string | suffix | |
| OrganizationName | Entity reference | parentcustomerid.name | |
| Title | string | jobtitle | |
| ParentContactId | Entity reference | parentcustoerid.id | |
| DoNotEmail | boolean | donotemail | |
| IsDeleted | boolean | contact.statecode == 1 |
Contact Address
| Field Name | Data Type | Dynamics 365 Mapping/Notes | To be Synced |
|---|---|---|---|
| AddressName | string | address1_name | |
| AddressLine1 | string | address1_line1 | |
| AddressLine2 | string | address1_line2 | |
| AddressLine3 | string | address1_line3 | |
| City | string | address1_city | |
| StateProvince | string | address1_stateorprovince | |
| PostalCode | string | address1_postcode | |
| CountryCode | string | address1_countrycode | |
| AddressType | string | address1_addrestype | |
| Latitude | decimal | address1_latitude | |
| Longitude | decimal | address1_longitude | |
| DoNotPublish | boolean | N/A | |
| IsBill | boolean | N/A | |
| IsShip | boolean | N/A | |
| IsMail | boolean | N/A | |
| IsPrimary | boolean | N/A |
Contact Phone
| Field Name | Data Type | Dynamics 365 Mapping/Notes | To be Synced |
|---|---|---|---|
| FormattedNumber | string | telephone1 | |
| PhoneType | string | Business Phone | |
| IsPreferred | boolean | N/A | |
| IsSmsPreferred | boolean | N/A | |
| DoNotPublish | boolean | N/A |
Contact Email
| Field Name | Data Type | Dynamics 365 Mapping/Notes | To be Synced |
|---|---|---|---|
| EmailAddress | string | emailaddress1 | |
| EmailType | string | N/A | |
| IsPreferred | boolean | N/A (by default, emailaddress1 is the primary email address) | |
| DoNotPublish | boolean | N/A |
Security Groups, Community Groups, & Custom Demographics
Dynamics 365 Option Sets are used on the 'Contact' and 'Account' objects to set up the Groups and Demographics in Higher Logic. See the Microsoft support article for help in creating Option Sets.
- Fields that are synced as Groups will be treated as both Security Groups and Community Groups by default.
- Fields that are synced as a Demographic will be synced as a Custom Demographic in your community.
Section V: Single Sign-On
The Single Sign-On (SSO) tech worksheet will be sent separately.
NOTE: Are you planning an SSO implementation with Higher Logic? If so, your implementation project may require a one-time fee for configuration and testing. Reach out to us to learn more.