SugarCRM SupportProduct GuidesSugar MarketSugar Market CRM Integration GuideMicrosoft Dynamics CRM
Sugar Market was formerly known as Salesfusion.

Microsoft Dynamics CRM

Overview

This page covers integrating Sugar Market with Microsoft Dynamics CRM, including configuring, syncing, and using data mappings.

Important: Review Integration Overview: All CRM Types before proceeding with this topic. If you are a new customer installing and configuring the MS Dynamics integration for the first time, then please also read this page on creating a Microsoft Application ID.

Topics

Supported Versions

Refer to the Sugar Market Supported Platforms page for the current list of Microsoft Dynamics CRM versions that Sugar Market supports.

Integration With Microsoft Dynamics

The following are the two main components in the Sugar Market bundle:

Buyer's Journey Integration

The Buyer's Journey Integration is automatically installed and added to the forms for contacts and leads and can be found near the bottom of the page under a section labeled Sugar Market when viewing a record.

1

Custom Entities

The following five custom entities are installed with the Sugar Market Dynamics bundle: Landing Pages, Events, Campaign Emails, Clicked Links, and Web Activities. They can be found under the record dropdown when viewing a contact or lead.

2

These custom entities can be used to store activity pushed from Sugar Market to MS Dynamics. You can also choose to push activity to the Activity Record in Dynamics instead of using the custom entities.

Emails

Once Sugar Market has captured the delivery status of an email recipient, the respective record in CRM will be updated per the options selected in the connector configuration. The two options are to create a Sugar Market Email Activity record, or a native Activity record.

Option 1: Sent Email to Sugar Market Email Entity (Campaign Emails)

Contains both the Open and Click count, the email sender, and the name of the campaign. This is a good option if you do not want to clutter up the Activity Record section as well as see more information at a glance.

3

Clicking into a campaign pushed to our custom entity will allow you to see the Links\URLs clicked.

4

Option 2: Pushing Email Sent, Opened, and Clicked to Activity Record

This option does not have the ability to roll up to one sent email. Therefore, each activity will be pushed up as a separate activity. This can become a bit cluttered, however if your sales team lives in the Activity record, it can be a good option.

5

Landing Pages

Once Sugar Market has captured a landing page completion, the respective record in CRM will have a Landing Page completion added to the Landing Pages custom entity.

Completions to Custom Entity

You will be able to see the Dialog Name and completed date for each landing page completion.

6

Completion Detail

Clicking into the completions allows visibility of the data submitted into the landing page. (Dialog Response)

7

Web Activity

Once Sugar Market has captured cookied web activity for a lead or contact, the respective record in CRM will be updated per the connector configuration. The two options are to create either a Sugar Market Web Activity record or a native Activity (history) record. You can also push up uncookied web activity at the account level.

Option 1: Web Activity to Sugar Market Web Activity Entity

This allows you to see more information easily, without having to click into the activity. Pushing the activity to our custom entity also will keep your Activity History from getting cluttered with lots of web activity. 

8

Clicking into any of the activities brings up more details on the web session.

9

Option 2: Web Activity to Activity Entity

This is a good option if your team lives in the Activity section of contacts and leads. The activity will be marked as completed by the syncing user.

10

Clicking into any of the activities expands more details on the web session.

11

Events

Once an event in Sugar Market is over, all registered and attended contacts and leads will have their respective records in CRM updated with the event information inserted into the custom Event Management entity.

Events to Custom Entity

This will allow you to see the event attendance information for any event that record has registered for.

12

Clicking into any of these events will allow you to see additional information about the event.

13

Tasks

When a task is created in Sugar Market, you can push those as Open Activities to the corresponding CRM record.

14

Marketing Lists

By selecting the corresponding checkbox in the Sugar Market connector screen, (Pull Marketing Lists to Distribution Lists) Sugar Market will sync down members of Marketing Lists from Dynamics into a Sugar Market distribution list, which can then be used as an include or exclude list. Static lists are synced every sync cycle, whereas Dynamic lists are synced every 24 hours from the first time we pulled the list down.

15

Notes regarding syncing Dynamics Marketing lists:

  • If the records do not already exist in our database (in contact table), we will not sync them into the Sugar Market distribution list.
  • Sugar Market distribution lists do not contain duplicate emails.

16

Installing Sugar Market

Prerequisites

To install the Sugar Market Bundle, you will need:

Installing the bundle is comprised of two key steps: Installing the solution and configuring the iframe.

Note: Please Publish All Customizations prior to starting this process to ensure it is error-free.

New Installations

Step 1: Download Install Files

There are different versions of Microsoft Dynamics CRM, each version requiring unique bundles. To find the bundle that matches your version, please see below.

If you currently do not have the Sugar Market solution then download the following.

For Microsoft Dynamics 365 Online only: Sugar Market 1.1.0.0

For Microsoft Dynamics 2015, 2016 (Online or On-Premise) OR Dynamics 365 (on-premise): Sugar Market 1.0.0.0

Step 2: Install Sugar Market Bundle

  1. Navigate to Settings > Solutions
  2. Select Import
  3. Once the pop up appears, select Choose File and select the Sugar Market Bundle downloaded in Step 1.
  4. Click Next
  5. On the following screen, under Post Import Actions, ensure "Enable any SDK Message processing steps included in the solution" is checked, then click Import
  6. After a short progress bar, you should be directed to the success screen

If the install fails, please export the log file and file a case with the Sugar Support team.

Step 3: Configuring the Buyer's Journey Integration

To configure the Buyer's Journey, navigate to Sugar Market > Configuration. Once there create a new configuration record.

There are four key items contained in this configuration, three of which need to be manually set:

  • Name: We recommend "Sugar Market Buyer's Journey", but can be anything
  • Sugar Market URL: https://app.salesfusion.com
    • Note: This option will not be applicable for Dynamics 365 Online
  • Buyer's Journey URL: https://iframe.salesfusion.com
  • Organization ID: Automatically populated per your CRM's Instance ID (Found in Developer Resources)

After filling in the necessary information, the configuration should look very similar to the screenshot below:
How the Integration Works - Dynamics - iFrame

 

Existing Installations and Upgrades

Step 1: Downloading the right solution

Note: Never uninstall your current version of Sugar Market as you will lose any data that was pushed up to the Sugar Market custom entities.

If you already have a Sugar Market solution installed in your Microsoft Dynamics CRM, then navigate to the Settings Menu and select Solutions to check which version is currently installed.

For Microsoft Dynamics 2013 to 2015, 2016 (Online or On-Premise) OR Dynamics 365 (On-premise only):

  • For those who have version 4.x.x.x already installed, then download the following:

Salesfusion 4.0.2.7 - Existing Installation (4.x upgrade)

  • For those who have version 3.x.x.x already installed, then download the following:

Salesfusion 3.0.2.7 - Existing Installation (3.x upgrade)

For Microsoft Dynamics 365 Online Only

  • For those who have version 1.x.x.x already installed, then download the following:

Sugar Market 1.1.0.1 - Existing Installation (1.x upgrade)

  • For those who have version 4.x.x.x already installed, then download the following:

Salesfusion 4.0.2.8 - Existing Installation (4.x upgrade)

  • For those who have version 3.x.x.x already installed, then download the following:

Salesfusion 3.0.2.8 - Existing Installation (3.x upgrade)

Note: For those upgrading from Microsoft Dynamics CRM 2011 to Microsoft Dynamics CRM 2015. Your upgrade will be done in 2 tiers, from 2011 to 2013 and then from 2013 to 2015. You must upgrade Sugar Market as you move up each version. So when you've upgraded to Microsoft Dynamics CRM 2013, before you continue to 2015 you need to upgrade the Sugar Market 2013 solution. Then once you've upgraded to 2015, you will upgrade to the Sugar Market 2015 solution.

Step 2: Upgrading the Solution

  1. Navigate to Settings > Solutions
  2. Select Import
  3. Once the pop up appears, select Choose File and select the Sugar Market Bundle downloaded in Step 1.
  4. Click Next
  5. On the following screen, choose the following options:
    1. Solution Action (This step will only be available for Online 365)
      1. Select: Update (not recommended) 
    2. Previous Customizations on Components Included in this Solution
      1. Select: Overwrite customizations (not recommended)
    3. Post Import Actions
      1. Select: Enable any SDK Message processing steps included in the solution
    4. Reference screenshot for the options above:
      dynamics upgrade customization Importing1
  6. Click Import
  7. After a short progress bar, you should be directed to the success screen

If the install fails, please export the log file and file a case with the Sugar Support team.

 

Minimum Permissions for Syncing Users

Below are the minimum permissions required for the user you are providing us with to authenticate against your Microsoft Dynam-ics CRM to push and pull data (sync). You may add more permissions if desired as using this user inside Microsoft will be limited with only minimum permissions, likely causing troubleshooting sync issues to be more challenging.

Please note that any the screenshots below show ONLY the permissions that are needed. Any permissions NOT mentioned are not necessary.

Core Records

Installing Salesfusion - Dynamics - Core Records

Marketing

Installing Salesfusion - Dynamics - Marketing

Sales

Installing Salesfusion - Dynamics - Sales

Business Management

Installing Salesfusion - Dynamics - Business Management

Customization

Installing Salesfusion - Dynamics - Customization

Custom Entities

Installing Salesfusion - Dynamics - Custom Entities

Below are the minimum permissions for users to interact with the Sugar Market Configuration tab as well as to only see the iframe.

Minimum Requirements for Sugar Market Tab or Sugar Market Iframe Only

MSRoleIFrameTab

Configuring the Microsoft Dynamics Connector

Accessing the Microsoft Dynamics Connector

Your Sugar Market CRM Connector will provide access to set up and modify your password access, synchronization preferences, and a timetable of the last completed sync with your CRM.

To access the Microsoft Dynamics Connector:

  1. In Sugar Market, navigate to User Menu > Administration View.
  2. In the External Connectors section, select "Microsoft CRM". The Microsoft Dynamics Configuration page displays.SM IG msconfig

Step 1: Syncing Credentials

To allow the sync between Microsoft Dynamics and Sugar Market, you need to first identify the Microsoft CRM user name and password that Sugar Market will use to sync with your CRM. You may create a new user or use a preexisting user since Microsoft CRM allows for concurrent logins, but be aware that all records created or updated by the Sugar Market sync will be attributed to the syncing user. The syncing user must have the necessary permissions to read and update all records you want to sync with Sugar Market.

To set syncing credentials:

  1. Complete the following fields in the Microsoft Dynamics CRM Web Service Credentials section:
    • Username: The Microsoft CRM CRM username we will use to authenticate via your web services
    • Domain: If necessary, the domain is located before the backslash (\) when logging in
    • Password: The password for above user
    • Application ID: The Microsoft-issued unique identifier for your application. Please refer to the Creating an Application ID for Sugar Market with Dynamics page for more information.
  2. After entering the credentials as mentioned above, click the Save Connection button. The password field will appear blank after the connection is saved.
    SM IG mssyncuser

Step 2: Web Services and Organization Information

Complete the following fields:

  • On Premise/Hosted: Select what version of Dynamics you have. If you are hosted by Microsoft or a partner, select "Hosted". If you are self-hosted with IFD (claims-based, ADFS), select "IFD". If you are self-hosted without IFD (published web resources externally), select "On-Premise".
  • CRM Organization Name: Found in Developer Resources
  • Organization ID: GUID Found in Developer Resources
  • Organization Service URL: Found in Developer Resources
  • Default user for new leads: The user assigned as the default (catchall) owner of a new lead when it is pushed up to Dynamics and the user does not already exist in Dynamics (the user only exists in Sugar Market). When the user does not already exist in Dynamics, Sugar Market assigns the defined user in this setting as the lead record owner. The user name only populates this list after the initial sync is complete.

To Access Developer Resources in Microsoft Dynamics:

  1. Navigate to Settings.
  2. Select Customizations.
  3. Click Developer Resources.

Once the information above is complete, click the Save Profile button.

Step 3: Syncing Dates

No Action Needed - this table will show you the last time Sugar Market has synced with your CRM. These will be up-dated once we have completed the initial integration. See the Integration With Microsoft Dynamics section for a deeper explanation on this component.

Step 4: Syncing Preferences

Set up your syncing preferences. This includes what information you want Sugar Market to sync down and what information you'd like Sugar Market to update and create, among other preferences. See the full explanation of each item below.

Note: In order for any table to push data up to the CRM, you must sync that table down first to Sugar Market. Example, if you select the option "Allow creation of new Lead/Contact" in the Push section then you must also select "Pull Contacts/Leads" respectfully as we only pull the table schema during the pull cycle.

Pull Data (Sync From CRM)

Pull Accounts

Whether or not Sugar Market should sync down Accounts from Dynamics CRM

Pull Contacts

Whether or not Sugar Market should sync down Contacts from Dynamics CRM

Pull Leads

Whether or not Sugar Market should sync down Leads from Dynamics CRM

Pull Teams

Whether or not Sugar Market should sync down Teams from Dynamics CRM

Pull Opportunities

Whether or not Sugar Market should sync down Opportunities from Dynamics CRM

Include Contacts and Leads without an email address (EmailAddress1 field)

Whether or not Sugar Market should sync down Contacts and Leads from Dynamics CRM that do not have email addresses assigned to them (These do not count against your database size)

Pull Marketing Lists to Distribution Lists

Whether or not Sugar Market should sync down Marketing Lists from Dynamics CRM as a distribution list in Sugar Market

Keep Picklist values in sync

Whether or not Sugar Market will sync down the picklist values from Dynamics CRM, and keep those lists updated as values are added or removed. This will allow these picklists to be used in landing page questions or selected in a drop down on the contact card.

*Note – Sugar Market picklists are not restrictive, so values outside of the picklist values will still be allowed.

Push Data (Sync From CRM)

Allow Updates for Lead and

Contact Records

Allow Sugar Market to push updated values to Lead and Contact records in Dynamics CRM

Allow creation of New Leads

and/or Contacts

Allow Sugar Market to create new Lead and/or Contact records in Dynamics CRM. The Sugar Market default is to create new records as Leads, unless the collected record has a specified CRMType as "Contact".

Allow Updating of

Unsubscribe Status

Allow Sugar Market to update the Unsubscribe status (DoNotBulkEmail field) of Lead and Contact records in Dynamics CRM

Allow Updating of Score Field

Allow Sugar Market

Push Sent Email to

Choose where, if at all, Sugar Market should push Sent Email records. The options are:

• Disabled: Do not push Web Activity records

• Activity Entity: Sent Emails will be pushed to CRM as a completed Activity record with references to the corresponding Lead/Contact

• Sugar Market Email Activity Entity: Sent Emails will be pushed to the Sugar Market-specific Email Activity entity, with references to the corresponding Lead/Contact

 

Do not push Email Body to Activity Record

Omit the Email body from the pushed record, reducing space consumed in the remote database.

Push Email Opens to

Activity Record

Push Email Opens to the Activity entity

Push Email Clicks to Activity Record

Push Email Clicks to Activity Record

Push Emails Click Data to Sugar Market Campaigner Clicks

Push URL's in campaigns clicked to the Sugar Market Email Custom entity

Push Identified (known Lead & Contact) Web Activity to

Choose where, if at all, Sugar Market should push known Web Activity. The options are:

• Disabled: Do not push Web Activity records

• Activity Entity: Web Activity will be pushed to CRM as a completed Activity record with references to the corresponding Lead/Contact

• Sugar Market Web Activity Entity: Web Activities will be pushed to the Sugar Market-specific Web Activity entity, with references to the corre-sponding Lead/Contact

 

Push Unidentified Web Activity to Sugar Market Web Activity Entity

Push unknown, account-level web activity to the Sugar Market web activity entity

Push Landing Page Completes to Sugar Market Landing Page Entity

Push landing page completes to Sugar Market's custom entity for Landing Page Completes

Push Attended Events to Sugar Market Events Entity

Push event attendance information to Sugar Market's custom Events entity.

Push Tasks to Activity Record

Allow Sugar Market to create Activity records in Dynamics CRM from Tasks created in Sugar Market

Push Opportunities created from Scoring

Allow Sugar Market to create new Opportunity records in Dynamics CRM

Push Delivery Status

Allow Sugar Market to push up the delivered or bounced reason to a custom field in CRM. Note: You will want to create a custom field in your CRM on the Contact/Lead table as a nvarchar(100) data type. Once the initial sync is complete and you have successfully pulled down Contacts and/or Leads, you will see your field in this drop down menu to select from.

Step 5: Database Integrity

Recycle Bin - When our bundle is installed, a few triggers are added which add any records deleted in Dynamics to a custom table. This table is referenced in the sync, and any records contained in this table are removed from Sugar Market's database. This is an important feature if you do not plan on marketing to any records deleted from CRM. If this box is checked at any point in time, all records that were deleted since the bundle was installed in CRM will be retroactively in Sugar Market as well.

Post-sync Cleanup Reports - Only if your database contains reports that meet the criteria mentioned in the UI, they will be displayed in a drop down. The minimum criteria for the reports are as follows:

Contacts

  • View: ViewAccountContact
  • Minimum Column: ContactID
  • Minimum Filter: CRMType = Contact

Leads

  • View: ViewAccountContact
  • Minimum Column: ContactID
  • Minimum Filter: CRMType = Lead

After a sync cycle completes, any records that fall into the report criteria will be removed from Sugar Market's database, as well as any lists or campaigns they may be in.

Microsoft Dynamics uses inactive and active for contacts. Records that are set as inactive are not considered "deleted" for the recycle bin, and therefore Sugar Market will continue to sync them. If you want to re-move inactive records from Sugar Market, autodelete reports can be used to do so. Below is the filter you can use to do so. To learn more on Statecodes and StatusCodes, please see this article.

Contacts

  • Statecode = 1

Step 6: CRM Alerts

Insert the email addresses of whom should be alerted should there be an credential issue with your sync. We typically recommend you include the CRM Admin and the syncing user. You can separate multiple email address with a semicolon.

Step 7: Initializing the sync

Once you have completed installing our solution and configuring the connector screen you will need to reach out to the Sugar Market team to initiate the sync. Please contact your Sugar Market representative to initiate this process.

Microsoft Dynamics Solution Patch Notes

Note: Uninstalling our solution will cause a lose of data that was pushed into the custom entities. It is recommended to instead overwrite the existing solution with the new solution.

Microsoft Dynamics 365 Online ONLY

Solution 1.1.0.1 - Q1 2020

  • Added compatibility for Microsoft Unified Experience.

Solution 1.1.0.0, 4.0.2.8, and 3.0.2.8 - Q4 2019

  • Handled the API changes deprecated by Dynamics 365 online (version >= 9.0)
  • Removed the Salesfusion app URL from the Sugar Market config page (as it is not needed in the bundle)

Microsoft Dynamics 2015, 2016 (Online & on-premise) and Dynamics 365 (On-Premise ONLY)

Solution 1.0.0.0, 4.0.2.7 and 3.0.2.7 - Q4 2019

Sugar Market has further performed a refresh on our Dynamics bundle by updating the branding from Salesfusion to Sugar Market, where applicable. 

  • New bundle 1.0.0.0 was created for new customers going forward that updates the bundle name and bundle display name to "Sugar Market" while maintaining the same architecture. 
  • Bundle 4.0.2.7 display name has been updated to "Sugar Market" while the bundle name is required to remain Salesfusion due to the architecture the bundle was built on.
  • Bundle 3.0.2.7 display name and bundle name both updated to "Sugar Market"

Solution 4.0.2.6 and 3.0.2.6 - Q2 2019

Sugar Market has performed a refresh on our Dynamics bundle in order to simplify and streamline the integrations between both systems. Below are the following changes to the bundle.

Sugar Market Module
  • Sugar Market Icon has been updated to the latest branding
  • Removed the following dashboards and functions due to usage (dashboards can be created for the user as needed by a CRM administrator):
    • Web Forensics: Dashboard, Web Tracking, Account Activity, Lead Activity, Contact Activity, Top Pages, Top Keywords, Top Referrers
    • Email Marketing: Dashboard, Campaigns, Marketing Lists, Templates
    • Sales: Call Down
    • Landing Pages: Landing Page Home, Landing Page Library, Landing Page Wizard
    • Sugar Market: Hot Leads, Hot Contacts, Hot Accounts
    • Extensions: Web Activity Details
  • Sugar Market Configuration icon has been updated
  • Sugar Market Configuration no longer auto-populates the iframe URL to future proof URL changes
Marketing List and Campaign Activity Module
  • The ability to send a Sugar Market marketing campaign through Dynamics Marketing List or Dynamics Campaign Activities has been removed due to usage and to streamline Sugar Market best practices.
Contact and Lead Module
  • Within a Contact or Lead the Sugar Market button has been removed in favor of the embedded iframe that outputs Sugar Market's Contact/Lead Journey.
  • Sugar Market Iframe's URL for the Sugar Market Journey has been updated from salesfusion360.com to iframe.salesfusion.com
    • The Sugar Market configuration will need to be updated to the latest URL manually. Instructions are in the installation guide.
  • The following changes to our custom entities within the Contact and Lead module
    • All icons have been updated
    • Dialogs renamed to Landing Pages
    • Campaign Clicked Links renamed to Clicked Links
    • Removed Nurture Leads

Microsoft Dynamics CRM Mappings

The following fields, grouped by their tables in Sugar Market, are pulled down from Microsoft Dynamics CRM into Sugar Market.

Accounts

Microsoft Field

Sugar Market Field

--

AccountID (primary key)

Microsoft's Account ID (primary key)

ID

Name

AccountName

OwnerID (foreign key)

OwnerID (foreign key)

Contacts and Leads

Sugar Market does not have a Leads table, but they are differentiated in the Contacts table by the CRMType field.

Microsoft Field

Sugar Market Field

--

ContactID (primary key)

Microsoft's Contact ID (primary key)

ID

Microsoft's Account ID (foreign key)

AccountID (foreign key)

OwnerID (foreign key)

OwnerID (foreign key)

--

CRMType*

--

CreatedDate

--

LastUpdate

CreatedOn

ExternalCRMCreatedDate

ModifiedOn

ExternalCRMUpdatedDate

FirstName

FirstName

LastName

LastName

EmailAddress1

Email

ParentCustomer

Account Lookup (Contacts only)

CompanyName

Account Lookup (Lead only)

DoNotSendMM

DONOTSENDMARKETINGMATERIALNAME

DoNotBulkEmail

OpOut

(Does not map)

Source

JobTitle

Title

Telephone1

Phone

MobilePhone

MobilePhone

Address1_Line1

--

Address1_Line2

--

Address1_Line3

--

Address1_City

--

Address1_State

--

Address1_StateOrProvince

--

Address1_PostalCode

--

Address1_Country

--

Address1_County

--

Address1_Fax

--

Address1_Telephone1

--

Address1_Telephone2

--

Address1_Telephone3

--

Opportunities

Microsoft Field

Sugar Market Field

--

OpportunityID (primary key)

Microsoft's Opportunity ID (primary key)

ID

Microsoft's Account ID (foreign key)

AccountID (foreign key)

OwnerID (foreign key)

OwnerID (foreign key)

Description

--

Closing_Date

--

Est_Closing_Date

--

Users

Microsoft Field

Sugar Market Field

--

UserID (primary key)

Microsoft's user ID (primary key)

ID

FirstName

First_name

LastName

Last_name

Username

Username

FullName

Name

Address1_Telephone1

Phone_Number

Address1_Line1

Address1

Address1_Line2

Address2

Address1_City

City

Address1_StateOrProvince

State

Address1_PostalCode

Zip

Address1_Country

Country

JobTitle

JobTitle

MobilePhone

Cell

Salutation

Salutation

Push Only - Sugar Market's Task to Microsoft's Activity

Microsoft Field

Sugar Market Field

--

TaskID (primary key)

Microsoft's Activity ID (primary key)

ID

Microsoft's ContactID (foreign key)

ContactID (foreign key)

ContactName

Contact.FirstName + Contact.LastName

ActualStart

DueDate

ScheduledStart

DueDate

Actual End

DueDate

Description

Comments

Subject

Subject

Note: If Sugar Market Task.Status is set as "Complete" through a Sugar Market automation we'll push the Status up as "Complete", otherwise we will push the task up as "ToDo."

Custom Entities

Ma_campaignemail (Campaign Email)

CRM Field

Type\Size

Relationship

new_alertcrm

Number

Direct

new_assetid

Number

Direct

new_body

String (2000)

Direct

new_bodynohtml

String (2000)

Direct

new_bodysource

String (100)

Direct

ma_campaignemailid

Lookup (CampaignActivity)

Lookup (CampaignActivity)

new_campaignerid

Number

Direct

new_campaignertype

Option Set

Direct

new_campaignid

Lookup (Campaign)

Lookup (Campaign)

new_clicked

Number

Direct

new_deliverymessage

String (100)

Direct

new_deliverystatus

Option Set

Direct

new_displayname

String (100)

Direct

new_dynamiccontentid

Number

Direct

new_forms

Number

Direct

new_friendforward

Number

Direct

new_fromemail

String (100)

Direct

new_fusionscore

Number

Direct

new_header

String (100)

Direct

new_id

String (100)

Direct

new_idclick

String (100)

Direct

new_idopen

String (100)

Direct

ma_nurtureleadid

Lookup (Lead)

Direct

new_opened

Number

Direct

new_postdate

Datetime

Direct

new_recipientid

Number

Direct

new_regardingcontactid

Lookup (Contact)

Lookup (Contact)

new_regardingid

Lookup (Lead)

Lookup (Lead)

new_sender

String (100)

Direct

new_campaignsubject

String (100)

Direct

new_threadnum

Number

Direct

new_toemail

String (100)

Direct

new_unsub

Number

Direct

Ma_campaignerclick (Campaign Clicks)

CRM Field

Type\Size

Relationship

ma_campaignemail

Lookup (Campaign Email)

Lookup (Campaign Email)

ma_campaignemailName

String (250)

Direct

ma_campaignerclickId

Unique ID

Unique ID

ma_LinksClickedId

Lookup (Campaign Activity)

Lookup (Campaign Activity)

ma_LinksClickedIdName

String (200)

Direct

new_CampaignerId

Integer

Direct

new_CampaignerLinkId

Integer

Direct

new_CampaignId

Lookup (Campaign)

Lookup (Campaign)

new_CampaignIdName

String (250)

Direct

new_ContactId

Lookup (Contact)

Lookup (Contact)

new_ContactIdName

String (160)

Direct

new_ContactIdYomiName

String (450)

Direct

new_LeadId

Lookup (Lead)

Lookup (Lead)

new_LeadIdName

String (160)

Direct

new_LeadIdYomiName

String (450)

Direct

new_LinkOrder

Integer

Direct

new_name

String (100)

Direct

new_rURL

String (200)

Direct

new_ToEmail

String (100)

Direct

new_WebSessionId

String (100)

Direct

Ma_dialog (Landing Pages)

CRM Field

Type\Size

Relationship

ma_completedDate

Date Time

Direct

ma_Contact

Lookup (Contact)

Lookup (Contact)

ma_ContactName

String (160)

Direct

ma_ContactYomiName

String (450)

Direct

ma_dialogId

Unique ID

Unique ID

ma_DialogResponse

Memo (32768)

Direct

ma_Fusionid

Integer

Direct

ma_Lead

Lookup (Lead)

Lookup (Lead)

ma_LeadName

String (160)

Direct

ma_LeadYomiName

String (450)

Direct

ma_name

String (255)

Direct

ma_StartformID

Integer

Direct

Ma_event (Events)

CRM Field

Type\Size

Relationship

ma_Attended

Boolean

Direct

ma_Contact

Lookup (Contact)

Lookup (Contact)

ma_ContactName

String (160)

Direct

ma_ContactYomiName

String (450)

Direct

ma_Duration

Integer

Direct

ma_EventDate

DateTime

Direct

ma_eventId

Unique ID

Unique ID

ma_EventLocation

String (255)

Direct

ma_eventname

String (255)

Direct

ma_Fusionid

String (100)

Direct

ma_Lead

Lookup (Lead)

Lookup (Lead)

ma_LeadName

String (160)

Direct

ma_LeadSource

String (255)

Direct

ma_LeadYomiName

String (450)

Direct

ma_name

String (255)

Direct

ma_Registered

Boolean

Direct

Ma_recyclebin (Recycle Bin)

CRM Field

Type\Size

Relationship

new_EntityID

String (100)

Direct

new_EntityType

String (50)

Direct

new_name

String (100)

Direct

new_Processed

String (5)

Direct

new_ProcessedDate

DateTime

Format: DateOnly

new_ProcessedNotes

String (500)

Direct

Ma_webactivity (Web Activity)

CRM Field

Type\Size

Relationship

new_RegardingAccountId

Lookup (Account)

Account.AccountName = WebActivity.OrganizationName

new_RegardingAccountIdName

String (160)

Based off of new_RegardingAccountId

new_RegardingAccountIdYomiName

String (160)

Based off of new_RegardingAccountId

new_RegardingContactId

Lookup (Contact)

Contacts.Email = WebActivity.EmailAddress

new_RegardingContactIdName

String (160)

Based off of new_RegardingContactId

new_RegardingContactIdYomiName

String (450)

Based off of new_RegardingContactId

new_RegardingId

Lookup (Lead)

Contacts.Email = WebActivity.EmailAddress

new_RegardingIdName

String (160)

Based off of new_RegardingId

new_RegardingIdYomiName

String (450)

Based off of new_RegardingId

new_ScoreWebActivityDetails

Integer

Direct

markauto_AreaCode

Integer

Direct

markauto_BrowserLanguage

String (100)

Direct

markauto_City

String (100)

Direct

markauto_ClientHostname

String (150)

Direct

markauto_ClientIP

String (50)

Direct

markauto_ColorDepth

String (4)

Direct

markauto_CountryCode

String (50)

Direct

markauto_CountryName

String (50)

Direct

markauto_CRMType

String (25)

Direct

markauto_dma_code

Integer

Direct

markauto_Duration

Decimal

Direct

markauto_EmailAddress

String (150)

Direct

markauto_EndDate

DateTime

Direct

markauto_Hemisphere

String (10)

Direct

markauto_IndentifiedBy

String (16)

Direct

markauto_ISP

String (100)

Direct

markauto_JavaEnabled

Boolean

Direct

markauto_JavaScriptVersion

String (8)

Direct

markauto_Latitude

Double

Direct

markauto_Longitude

Double

Direct

markauto_OperatingSystem

String (16)

Direct

markauto_OrganizationName

String (100)

Direct

markauto_PixelDepth

String (4)

Direct

markauto_PostalCode

String (25)

Direct

markauto_RecipientID

String (100)

Direct

markauto_ReferrerDomain

String (50)

Direct

markauto_ReferrerKeywords

String (1000)

Direct

markauto_ReferrerQuery

String (1000)

Direct

markauto_ReferrerReferrer

String (1000)

Direct

markauto_region

String (50)

Direct

markauto_Resolution

String (16)

Direct

markauto_Scoring

Integer

Direct

markauto_Source

String (100)

Direct

markauto_StartDate

DateTime

Direct

markauto_TimeZone

String (10)

Direct

markauto_TouchPoint

String (100)

Direct

markauto_UserAgent

String (64)

Direct

markauto_WebBrowserID

String (150)

Direct

markauto_WebSessionID

String (100)

Direct

Ma_webactivitydetail (Web Activity Detail)

CRM Field

Type\Size

Relationship

markauto_duration

Decimal

Direct

markauto_entrypage

String (1)

Direct

markauto_exitpage

String (1)

Direct

markauto_hostname

String (250)

Direct

markauto_interactiondate

DateTime

Direct

markauto_name

String (300)

Direct

markauto_parameters

String (250)

Direct

markauto_path

String (250)

Direct

markauto_protocol

String (250)

Direct

markauto_referrer

String (1000)

Direct

markauto_webactivityid

Lookup (WebActivity)

WebActivityDetail.WebActivityID = WebActivity.WebActivity ID

markauto_webactivityidname

String (200)

Direct

markauto_webinteractionid

String (100)

Direct

markauto_websessionid

String (100)

Direct

Static Lists vs Dynamic Lists

When integrating with Microsoft Dynamics, there are two types of lists we pull down to Sugar Market:

  • Static Lists
  • Dynamic Lists

When selecting the "Pull Marketing Lists to Distribution Lists" option in the Microsoft Dynamics connector screen, we will pull down both static and dynamic lists.

This is what the connector setting looks like:

Static Lists vs Dynamic Lists - Connector Setting

First we pull down Static Lists, for which we check the date the list was last modified as our pulling criteria. In short this means, if the last modified time is current, then we will pull down the list in the next sync cycle. Some updates to static lists in Dynamics or some custom workflows are able to add records without updating the modified date, which means Sugar Market will not know to pull down the changes. Make sure that you check the modified date when making changes to your static lists so that they will get pulled down to Sugar Market.

This is what the Modified On field will show in Microsoft Dynamics:

Static Lists vs Dynamic Lists - Modified On

The second list type is Dynamic Lists. Since these are dynamic in nature, we do not have the same modified date available to check when the sync pulls down lists. When we pull the dynamic lists, we pull the entire list from it's created date. Since this could be an enormous number of records, we do not run this in the normal sync cycle. We run the dynamic lists once per day to avoid a backlog of records in the normal sync process. Typically this sync runs in the late evening on eastern time. For these lists, if you need to add records and send to them the same day it would be better to use either a static list, or manually import the records via the File Import feature in Sugar Market.

Uninstalling Sugar Market

Disclaimer: You are deleting a managed solution. The solution and all of its components, including data in the components, will be deleted. This action cannot be undone. This solution might take several minutes to uninstall, and you cannot cancel the uninstallation after it starts.

  1. Navigate to Settings > Solutions. Click the Sugar Market solution, and then select Delete.
  2. Confirm uninstall of solution. After selecting Delete in step 1, a confirmation prompt will appear. Select OK to continue with the removal process.
  3. Verify Uninstall Complete. The uninstall process will take at least a few minutes, but may take much longer, depending on the amount of marketing data that has been pushed up to the custom entities within the bundle.

Once the uninstall pop up disappears, please verify that the Sugar Market solution is no longer mentioned in the solutions list.

If there are any errors in the uninstall, please download the log file and file a case with the Sugar Support team with the log file attached.

Note: If you also installed the Report Control for Dashboard (Prerequisite for versions 3.0.2.3 and 4.0.2.3 and earlier), you may repeat steps 1-3 for that solution as well.

Last modified: 2021-08-21 22:02:43