The Salesforce integration leverages the Salesforce SOAP API. Refer to Requirements, below, for additional information.

Features of the Salesforce integration include:

• Single Sign-On (SSO)
• Automatic updates to member data
• Community Group Management
• Security Group Management
• Activity Sync
• Contact Management flow

The Higher Logic integration is individual record bound, which means the above actions are tied to a member record. When reporting an issue to Higher Logic support, be sure to include the Legacy Contact Key (in this case the 18 digit case safe Salesforce Contact ID).

Who should read this guide

This guide is for Community Managers and may be passed along to technical contacts within your organization in order to understand Higher Logic web services.

This guide assumes that you are experienced using:

• Higher Logic Communities
• Managing Community Groups
• Managing Security Groups
• Salesforce
• Updating Contacts
• Generating Reports
• Updating and creating Flows

Notification

Higher Logic should be notified if there are any changes to the service or servers. This notification of scheduled changes should be made to Customer Support (create a case) as soon as possible. We request at least 3 weeks notice.

Requirements

This integration requires:

• Salesforce Contacts and Accounts
• The Salesforce version of Professional (or higher) with API provisioned
• The Salesforce version be provisioned for Flows
• A Salesforce user be provisioned and created for Higher Logic and connected to implementationoc@higherlogic.com. This user should:
  • not have a 90-day password reset. Resetting the password will disable the integration; customers will have to provide the updated Security Token and password to Higher Logic Support.
  • be a dedicated user for Higher Logic, with the following permissions:
    • System Administrator
    • Marketing User
    • Connected App Creation

Initial setup

Higher Logic Periodic Refresh

This integration requires the creation of a Contact-level field called HL_Mod_Date; its value is updated based on a Flow in Salesforce.

If activities for Contact records occur at the Account level (such as a member's active membership record being tied to a company-level membership), the Flow must incorporate that flow down.

NOTE: When implementing your Salesforce integration, two important fields were determined: IsActive and HL_Mod_Date.

• IsActive – if this setting is enabled then for a record to be added to Higher Logic is if this flag is checked.
• HL_MOD_DATE – this field determines the date and time when a record was last updated. If this field does not change, review the configuration of your Flows.

The following are the only activities defined in the standard integration for Salesforce.

Qualifying Events

• Changes to Contacts
• Changes to Accounts

Configuring HL_Mod_Date Flows

The Higher Logic Thrive Community (Thrive Community) Salesforce integration leverages Accounts and Contacts. In order to trigger the Periodic Refresh, a custom field, HL_Mod_Date, must be created on the Account and Contact objects by a Salesforce admin following the steps below.

NOTE: These instructions are for Salesforce Lightning. To create Flows for Salesforce Classic, see Build a Flow.

Create the HL_Mod_Date custom field

1. Navigate to Setup and select Object and Fields.
2. Select Object Manager, then Contact, and then Fields & Relationships.
3. Select New, then select Date/Time as the field type, and then click Next.
4. For field label, specify HL_Mod_Date.
   • Do not require a value in the field to save the record
   • Do not set a default value
5. Click Next.

NOTE: Depending on your organization, this field may be hidden or showing. If this field is shown on a layout page, make sure that it is a read only field for informational purposes.

6. Specify your field-level security and click Next.
7. Choose the page layouts you would like to expose this field to and click Save.

Repeat these steps for the Account object.

Create the Flow

1. Navigate to Setup.
2. From the left menu go to Process Automation > Flows
3. Click New Flow and select Record-Triggered Flow from the Options > Create.

4. Select the Object i.e. Contact or Account.

5. Set the trigger to A record is created or updated.

6. Set Condition Requirements to Formula Evaluates To True And specify the formula:

NOTE: Confirm your fields on the Contact record that should trigger a change in Higher Logic; incorporate these fields into your formula. Sample logic is provided below

ISNEW() ||

ISCHANGED(Email) ||

ISCHANGED(FirstName) ||

ISCHANGED(LastName) ||

ISCHANGED(Salutation) ||

ISCHANGED(Title) ||

ISCHANGED(AccountID) ||

ISCHANGED(MailingStreet) ||

ISCHANGED(MailingCity) ||

ISCHANGED(MailingState) ||

ISCHANGED(MailingPostalCode) ||

ISCHANGED(MailingCountry) ||

ISCHANGED(Phone) ||

ISCHANGED(MobilePhone) ||

ISCHANGED(HomePhone) ||

ISCHANGED(Fax)

 

7. Select Every time a record is updated and meets the condition requirements under When to Run the Flow for Updated Records.

8. Under Optimize the Flow for, select Actions and Related Records.

9. Click Done.

10. On the next page in Flow Builder, click the button to add an element.

11. From the list, select Update Records.

12. Label it / add description as per your requirements.

13. Under How to Find Records to Update and Set Their Values, select Use the contact/account record that triggered the flow.

14. Set filter conditions to None - Always Update Record.

15. Under Set Field Values for the Account/Contact Record Select HL_Mod_Date__c from the field list and set the value to {!$Flow.CurrentDateTime} or CurrentDateTime: $Flow > CurrentDateTime.

16. Click Done.

17. Click Save → Label your Flow and click Save.

18. Activate the Flow and test.

Repeat these steps for each object that should impact the Contact HL Mod Date (typically Contacts and Accounts).

Accommodating for account flow-down in Periodic Sync

Some changes made at the Account level should impact Contacts. For example, if using the Account address information to define Contact address information, then Contact records in Higher Logic should be updated when the Account address information changes.

To use Account information for Contacts:

1. Navigate to Setup > App Setup > Customize > Contacts > Fields > Contact Custom Fields & Relationships > New.
2. Select Formula as your data type and label the field something appropriately descriptive.

TIP: Note the field names because the Higher Logic project manager will need them to complete the integration configuration.

3. Select formula return type to match the Account field from which you are pulling data.
4. Choose the Advanced Formula tab to set the formula and click Insert Field.
5. Find the Account field, add an appropriate Description and, optionally, Help Text, and then select Treat blank fields as blanks.
6. Uncheck all visibilities except System Administrator (or whichever profile the Higher Logic API user has). This allows the API users to grab the field without exposing it to anyone who doesn't need it.
7. Remove from all custom layouts. This prevents the field from displaying anywhere in the Salesforce interface.

Repeat these steps for each Account field that will be pulled into Higher Logic as a Contact field. When this is completed, send the API names of the newly created fields to your Higher Logic project manager and update the Contact Flow to include the new fields. Now, changes to the Account data will be picked up in the periodic refresh.

Activity Sync configuration

Activity Sync is configured to the Salesforce Task object by default. If you want to write activity to a custom object instead, use the following parameters.

• The API name of the Salesforce object to which activities should be written
• The API name of the field on the object in which to write the:
  • legacy contact key of the user performing the activity
  • activity date
  • activity type
  • activity description

NOTE: Activity records are written in a batch process to Salesforce every 30 minutes. This process uses one API call per 200 records.

User permissions

The Salesforce user must have the following permissions:

• Contacts/Accounts - Read, Create, Edit, View All, and Modify All
• Tasks - Read, Create, Edit, View All, and Modify All

Contact creation initial setup

Provide the following information to Higher Logic when going through the implementation process for your integration.

• Whether you would like to update contacts, create contacts, or both.
• An account to test against
• Which fields you would like for a user to modify, as well as whether these fields are required
• Which fields you would like to be created when a user registers and whether these fields are required
• The label for the chosen field (for example, you could set the Salesforce Salutation field to display as Greeting)
• Provide the default Account ID for the “Fixed” value for Contact creation
  • We recommend that new contacts have a fixed Account ID, known as a Container Account. This account in Salesforce can then specifically hold all community applications to assist with progeny identification.

Best practices

• Create a Flow in Salesforce that sends an email request to approve new records to your Salesforce admin or Community Managers.
• Whoever approves new contacts in Salesforce can then assign the Contact to the proper account. Or your Salesforce admin can create a Salesforce process based on Email address and Website URL.

NOTE: If Contact Manager is enabled, we strongly recommend that the IsActive setting is enabled for your integration and a subsequent Flow be created that changes this flag only if contacts meet a specific criterion. A condition of that criteria is that a Contact must belong to an account other than the Container Account.

Single sign-on (SSO)

SSO allows members to access multiple authorized sites with one login. You can use Salesforce as your Identity Provider (IDP) or another third party solution to authorize access to your Thrive Community site.

Thrive Community supports OIDC, OAuth 2.0 and SAML 2.0.

Two benefits of implementing SSO are:

• Seamless creation of new members in Thrive Community
• Simplified login process across sites

SSO validation

After a contact is created in Salesforce and their data is available to sync to Higher Logic, authentication can be made via the IDP authentication service.

The member's initial log in will trigger a refresh of the user data; this is known as a Member Refresh. On the Sync External Database page, this refresh type will read as Unspecified' that is, it is not scheduled and refreshes as the user logs in.

Determine eligibility for community access

Periodic Refresh will refresh all members that have an updated HL_Mod_Date on the Contact record. However, not all Contacts with this updated field are eligible for community access. You might notice that these records are highlighted in red in the Sync External Database tool. Depending on your integration settings, there are three factors that determine whether your member is eligible for community access.

• Active status
• Expiration date
• Limit by Security Group

Active status

The active status for members in Salesforce is determined based on two configuration settings for your Thrive Community: IsActive and RemoveOn. These fields can be confirmed with Higher Logic Support.

IsActive

When configuring your Salesforce integration, one of the settings that is used to determine whether a member is active is based on a field of your choosing to determine eligibility. Generally, this is the IsActive checkbox field. (This might be called something else in Salesforce, but it will function the same.) If this field is checked, a record is active.

RemoveOn

If this configuration setting exists, an additional field might exist in your Salesforce instance. This field will only pull sync Contact data if this setting is not checked for a Contact record.

Expiration date

If a member expiration date has passed, the member will be deactivated in the community after the next Periodic Refresh.

Limit by Security Group

Limit by Security Group is a setting in your integration configuration that restricts community access to only those members whose Contact record in Salesforce has one of the allowed values.

To see a list of Security Groups that meet this requirement, navigate to the Security Groups Summary Report. At the top of the report is the Limiting Security Groups field. If the value is True, check the adjacent field, List of Security Groups Allowed to Sync to Higher Logic. This setting will allow records into your community only if their Contact record in Salesforce matches any of the values stored there.

Periodic Refresh

NOTE: The Periodic Refresh, Member Refresh, and a user login each use one API call. So, if you have 50,000 records to be refreshed, the integration will use 50,000 API calls.

To ensure that data on your Thrive Community site remains synchronized with your AMS, our Periodic Refresh tool will query your AMS every 30 minutes, explicitly checking the Contact record for the HL_Mod_Date field. Periodic Refresh also updates:

• Demographic information (e.g., First Name, Membership Expiration Date)
• Eligibility for membership to a Community Group
• Eligibility for membership to a Security Group

NOTE: This integration will limit its API calls to the Salesforce instance based on the daily API limit. If 75% of the API limit is reached, the integration will halt all refresh activity for 24 hours and resume from that point the next day.

Demographics

Demographics for a member are initially configured during integration setup. If new fields are to be added, Higher Logic support will require:

• The name of the field to be added
• A few Contact IDs with the field value

Demographics in Higher Logic can be created from the following Contact field types in Salesforce.

• Checkbox - For checkbox fields, Higher Logic creates "collapsed checkbox" demographics that are generally grouped by type. For example, a contact may have a checkbox field called "Bachelor's," which indicates having a bachelor’s degree, one called "Master's," and one called "PhD."

In this example, the demographic label may be Education Level. All Contacts with the Bachelor's field checked would have the bachelor's demographic with a value of Yes or No under the record in Higher Logic.

• Picklist: A separate demographic will be created for each pick list option that is selected by at least one contact syncing to Higher Logic. For example, if the picklist field is called Membership Type in Salesforce with the values of Platinum, Gold, and Silver, a demographic will be created for each of those values after an eligible member is synced to the Thrive Community.
• Multipick: A separate demographic will be created for each picklist option, like the picklist fields. The difference is that contacts can have more than one option selected and thus be assigned more than one demographic being pulled from this field.
• Text fields: The integration will pull the field name as a Higher Logic free-form demographic with the values assigned as the demographic values. 

Community Groups

A feature of the integration will generate a Community Group based on configuration settings. Community Groups in the Salesforce integration can be generated by:

• Contact fields
• Salesforce Campaigns

Contact Fields

Community Groups can be created based on the following field types in Salesforce:

• Checkbox: A Community Group will be created containing all contacts with the specified box checked in Salesforce
• Picklist: A separate Community Group will be created for each pick list option that is selected by at least one contact syncing to HL. For example, if the picklist field is called Membership Type in Salesforce with the values of “Platinum”, “Gold”, and “Silver” a Community Group will be created for each of those values once an eligible member is synced to the Thrive Community.
• Multipick: A separate community will be created for each pick list option, like the picklist fields. The only difference is that contacts can have more than one option selected and can exist in more than one Community Group.

The integration will generate a Community Group with the following settings for members.

• Community Group Name: This is the name of the field in Salesforce
• Community Group Type: Hidden AMS Default
• Community Group Description: This is the name of the field in Salesforce
• Community Group Member Start Date: This will be set to Null
• Community Group Member End Date: This will be set to Null
• Community Group Member Role: Member

Salesforce Campaigns

The integration can also sync Salesforce Campaigns as communities. This will generate a Community Group with the following settings for members.

• Community Group Name: This is the name of the Campaign in Salesforce
• Community Group Type: Hidden Event
• Community Group Description: This is the name of the Campaign in Salesforce
• Community Group Member Start Date: This will be set to Null
• Community Group Member End Date: This will be set to the End Date of the campaign and is when your member will leave the Community Group
• Community Group Member Role: This is the Campaign Member Status in Salesforce

Workspace

Workspace is not supported in this integration.

Integration community types

The types below are explicitly generated by the Salesforce integration.

Hidden AMS Default

As a default, when a Community is created by the integration, it will come into Higher Logic as a Hidden AMS Default. This default community will then require a Super Admin to:

1. Toggle whether members of this Community Group are Members
2. Change the Community Type

Hidden event

The Salesforce integration does not support Event Communities.

However, if the option to create Community Groups based on Campaigns is enabled, Community Groups generated by a Salesforce Campaign will be set to Hidden Event.

Security Groups

Security Groups in Higher Logic not only determine Member Status but can also determine access rights to functionality, navigation, and content within Thrive Community. In the Salesforce integration, Security Groups can be determined by:

• Automatic generation
• Configuration settings

Automatic generation

In a Higher Logic integrated Community, a Security Group is automatically generated for Accounts and Contacts. This setting cannot be disabled.

Configuration settings

A Higher Logic Integrated Community can generate Security Groups based on:

• Contact Fields
• Contact Field Values
• Record Types

Contact fields

Security Groups can be created based on the following field types in Salesforce.

• Checkbox: A Security Group will be created containing all contacts with the specified box checked in Salesforce
• Picklist: A separate Security Group will be created for each pick list option that is selected by at least one contact syncing to HL. For example, if the picklist field is called Membership Type in Salesforce with the values of “Platinum”, “Gold”, and “Silver” a Security Group will be created for each of those values once an eligible member is synced to the Thrive Community.
• Multipick: A separate community will be created for each pick list option, like the picklist fields. The only difference is that contacts can have more than one option selected and can exist in more than one Security Group.

Account Flow down Contact Fields

In the case of field flow down: when a field exists on an Account that you would like to apply to Contacts associated with that Account, you have to create a custom field on the Contact record. 

For example, if a "Membership Level" applies to an Account and should also apply to associated Contacts, you must then create a custom field on Contact which pulls the value of this Account field into it and name it appropriately (e.g. "Account_Membership_Level__c").

This newly created Contact field must then be included in the Contact Flow so that whenever it changes, the HL Mod Date field is updated and the record is picked up in the next periodic refresh.

Contact field values

An additional setting in the integration can delegate an email address domain or contacts associated with an Account ID to the Staff Security Group in Higher Logic. This setting can only apply to the Staff Security Group.

Record Types

The Higher Logic integration can create security groups based on Record Types for Contacts and Accounts. Security Groups generated based on Record Type will have the following values set in Higher Logic.

• Security Group Name: Record Type Name
• Security Group Description: Record Type Name
• Security Group Type: Contact Record Type
• Security Group Start Date: Null
• Security Group End Date: Null
• Security Group Member Role: Member

Event Calendar

The Salesforce integration does not support Event Calendar.

Integration tools

Sync External Database

The Sync External Database tool is the best place for admin users to confirm the status of their integration or whether records have been refreshed in the Thrive Community site.

To access Sync External Database:

1. Log in to your Thrive Community site.
2. Navigate to Admin > Settings > Integrations.
3. Select Sync External Database.

The Sync External Database page displays pertinent information for your integration, including:

• Community information for individual members
• AMS information for individual members
• Whether the integration is currently running
• Which records have most recently refreshed
• Provides tools for Higher Logic Super Admins to refresh individual records

In this area, you will see the following information:

• Overview information
• Refresh Member tool
• Member Refresh History
• Refresh Community Group Members tool
• Refresh Security Group Members tool
• Job History

Overview information

The overview information will display the status of your integration.

• Number of Contacts Pending Refresh: This is the number of records pending Periodic Refresh
• Periodic Refresh Schedule: How frequently the Periodic Refresh is scheduled
• Periodic Refresh Last Ran At: When the Periodic Refresh last ran
• Daily Refresh Status: This is typically disabled. This is a legacy refresh type that is no longer used.
• Daily Refresh: This will either say Never or a date far in the past as this Legacy refresh type is no longer used.
• Community Sync Schedule: This is a refresh type only used by the Weblink integration otherwise this will read as disabled.
• Community Sync Last Ran At: This value will update once per day if enabled, or if disabled will either read as Never or a date far in the past as it is a Legacy refresh type.

The Sync External Database page is also where Members can be manually refreshed with the Refresh Member tool.

Refresh Member

Periodic Refresh controls when all the records are updated (every 30 minutes) in bulk. If there are instances where Super Admins would like to refresh a Member manually, the Refresh Members tool will allow that to happen.

A Member Refresh can occur under the following instances:

• Every 30 minutes via Periodic Refresh provided the HL_Mod_Date field has changed
• If SSO is enabled and a user attempts to log in to the application for the first time
  • Higher Logic will validate whether that user has access to the Thrive Community site and refresh the user details
• Manually via the Refresh Member tool

A Member Refresh will update:

• Demographic information (ex. First Name, Membership Expiration Date)
• AMS managed Community Groups (ex. Discussions, libraries, and microsites)
• AMS managed Security Groups

To refresh a member manually, navigate to the Sync External Database tool:

1. Log in to your Thrive Community site.
2. Navigate to Admin > Settings > Integrations.
3. Select Sync External Database.
4. Scroll down to the Refresh Member Tool.

You’ll want to have the Integration Key of your user record handy. You can find this by leveraging the User search tool and clicking on a Member record.

Once you have the Integration Key, proceed to the Refresh Member tool.

1. Enter the Integration Key in the Member Info box.
2. Select Refresh Member.

The page will refresh, and you should see your member record in the Member Refresh History list with the value Member Refresh under the column Job Type.

The Refresh Member tool is also where you will find back-end information related to your members.

In Refresh Multiple Users, you can enter multiple Integration Keys and add those members to the queue.

Display Backend System User Data

The Display Backend System’s User Data is a tool to view the information related to your user in Salesforce.

Make sure you still have that Integration Key.

1. Enter the Integration Key in the Member Info box.
2. Select Display Backend System’s User Data.

You’ll be presented with a snapshot of this user’s information. This is particularly helpful when trying to diagnose why a member is not eligible for community access.

Display Connected Community User Data

To view a member record's information and their existing community information included security groups, demographic details, and community groups:

1. Enter the Integration Key.
2. Select Display Connected Community User Data.

Community Refresh

The Community Refresh tool allows a Community Group to be refreshed in the Higher Logic Community – note that this tool will only refresh the members already in the Community Group. To add new records to the group (records not already in the Community Group):

1. Create a Report in Salesforce with the field ContactID of the records you would like to add.
2. Paste the ContactIDs into the Refresh Multiple Users tool.
3. Select Refresh Members.

After the records have been added to the community, you can choose to refresh the Community Group.

To refresh a Community Group, navigate to the Sync External Database tool.

1. Log in to your Thrive Community site.
2. Navigate to Admin > Settings > Integrations.
3. Select Sync External Database.
4. Scroll down to the Refresh Community Group Members.

5. Select the Group Type from the drop down.
6. Select the Group Key you would like to refresh.
7. Select Refresh Group.
8. Under Job History, the Community Group will be listed with a summary.

• Date/Time: Will reflect the date and time of the refresh
• Status: Whether the refresh was a Success
• Job Type: Which job type completed, in this example it will say Community Refresh
• Comment/Error: This will reflect either a brief summary or if there was an error

Security Group Refresh

The Security Group Refresh tool allows a Community Group to be refreshed in the Higher Logic Community. Note that this tool will only refresh the members already in the Security Group. To add new records to the group (records not already in the Security Group):

1. Create a Report in Salesforce with the field ContactID of the records you would like to add.
2. Paste the ContactIDs into the Refresh Multiple Users tool.
3. Select Refresh Members.

Once the records have been added to the Security Group, you can now choose to refresh the Security Group.

To refresh a Security Group, you’ll need the Legacy Group Key. To obtain this, navigate to Security Groups under Users and grab the Integration/AMS Key, navigate to the Sync External Database tool:

4. Log in to your Thrive Community site.
5. Navigate to Admin > Settings > Integrations.
6. Select Sync External Database.
7. Scroll down to the Refresh Security Group Members tool.
8. Enter the Integration/AMS key.
9. Select Refresh Group.
10. Under Job History, the Security Group will be listed with a summary.

• Date/Time: Will reflect the date and time of the refresh.
• Status: Whether the refresh was a Success.
• Job Type: Which job type completed, in this example it will say Security Group Refresh.
• Comment/Error: This will reflect either a summary or if there was an error.

Member Refresh History and Job History

The Member Refresh History and Job History reflect the most recent jobs that have run.

Member Refresh History

Member Refresh History has the following:

• Name: The name of the user imported:
  • Not Imported: for members that were not imported to the Community.
  • Highlighted in Red: Deactivated members.
• Date/Time: The date and time of the refresh.
• Status: Whether this was a Success or a Failure.
• Legacy Contact Key: The Integration Key or ContactID.
• Job Type:
  • Periodic Refresh
  • Unspecified
  • Community Refresh
  • Security Group Refresh
• Comment/Error: A summary if there was an error with the specific record.

Job History

• DateTime: Will reflect the date and time of the refresh.
• Status: Whether the refresh was a Success.
• JobType: Which job type completed:
  • Periodic Refresh: How many records were identified as meeting the member eligibility and HL_Mod_Date as updated.
  • Community Refresh: How many records were identified for a Community Group refresh.
  • Security Group Refresh: How many records were identified for a Security Group refresh.
• Comment/Error: This will reflect either a summary or if there was an error.

Activity Sync

To enable Activity Sync for your integration, complete the following.

• Activity Sync has been purchased
• Activity Sync has been enabled and configured in Salesforce
• The subscriptions must be selected in Higher Logic

You can select the type of Activity Subscription by searching Activity Sync. If you are in the legacy interface, this is located under Contacts.

To learn more about Activity Sync in Higher Logic, see Member Activity Sync.

Contact management

Contact Manager is a Higher Logic feature that facilitates the creating and updating of Contact records in Salesforce. This feature completes the following workflows:

• Salesforce Profile Update: Allows users in Higher Logic to edit their Contact details and it overwrites field values in Salesforce
• Salesforce Contact Creation: Provides a form for new users to create a new user accounts in your Thrive Community site

To enable this feature, contact your account manager. 

Frequently Asked Questions

Why didn't my member record update in the community?

Check the HL_Mod_Date on the Contact record. If it doesn't have today's date, review the document Salesforce Integration Guide and Creating Flows.

How do I upload members?

Members are uploaded via the integration. Ensure that the Contact or Account field that is outlined in your integration technical worksheet is checked for that member.

How do I add a member (who isn't in Salesforce) to my community?

Non-Salesforce members will not be added to the community.

Why wasn't my member added to my community?

Is Limit by Security Groups enabled? View the report, Security Groups Summary (Users > Reports > People Reports). In the upper part of the report, if the value in the Limiting Security Groups field is True, check the adjacent field, List of Security Groups Allowed to Sync to Higher Logic: Does the Salesforce Contact field for membership match any of those values?

I don’t have Limit by Security Groups enabled, or my contact record for my member is listed in the “List of Security Groups Allowed to Sync to Higher Logic” box. Why wasn’t my member added to my community?

• Is your member active? Check your integration settings from the technical worksheet or ask Higher Logic Support which field is used for IsActive or that the RemoveOn and check that value.
• Has your member’s expiration date passed? Check whether your member is expired.

What happens if I delete a Contact record in Salesforce?

When the record is refreshed in Higher Logic, it will be disabled.

What happens when I merge a Contact record in Salesforce?

When the records are refreshed in Higher Logic, if the record is not found, it will be disabled in Higher Logic.

What happens when I delete fields in Salesforce?

We recommend that you do not delete any of your integrated fields in Salesforce. If you must remove a field, we recommend that you append XXX to the field name and hide the field from your Salesforce users. Create a case immediately and indicate which fields you would like to remove.

Why does the message “There has been an issue retrieving data from the web service.” display when I try to refresh a member or display back-end data?

Check to see if this Integration Key exists? This record may not have been synced to Higher Logic, or it may have been deleted in Salesforce, or merged. For one of these reasons, that Salesforce Contact ID is no longer available.

Can I use my Higher Logic Salesforce user to integrate Higher Logic Thrive Marketing Enterprise or Higher Logic Thrive Marketing Professional?

Yes.

Why is the integration failing with an "INVALID_LOGIN" error?

The credentials being used to access the Salesforce API are invalid. Provide a valid password and Security Token to Higher Logic.