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

Salesforce CRM

Overview

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

Important: Review Integration Overview: All CRM Types before proceeding with this topic.

Topics

Supported Versions

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

Integration With Salesforce

Emails

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

Option 1: Sent Email to Sugar Market Email Entity

Does contain Opens and Clicks count, as well as being able to see who email was sent from and the name of the campaign. This is a good option if you don't want to clutter up the Activity History section.

2020-02-27 16-42-45 SF 1

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

Note: Open Activities and Activity History are Salesforce entities, and are not related to the Campaign detail.

2020-02-27 16-44-01 SF 2

Option 2: Sent Email to Activity (History) Entity

This doesn't contain opens and clicks, but is a good option if your sales team lives in the Activity History.

2020-02-27 16-44-46 SF 3

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.

2020-02-27 16-45-59 SF 4

Completion Detail

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

2020-02-27 16-46-22 SF 5

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.

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 possibly getting cluttered with lots of web activity.

2020-02-27 16-46-46 SF 6

Clicking into any of these activities grants you visibly into more activity details, as well as the web pages that were hit.

2020-02-27 16-47-36 SF 7

Option 2: Web Activity to Activity (History) Entity

This is a good option if your team lives in the Activity History.

2020-02-27 16-48-16 SF 8

Clicking into any of these activities will allow you to see additional details regarding the web activity.

2020-02-27 16-48-46 SF 9

Tasks

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

2020-02-27 16-49-14 SF 10

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 events which the record has registered for and attended.

2020-02-27 16-49-41 SF 11

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

2020-02-27 16-50-06 SF 12

 

Salesforce Campaigns

Distribution Lists

By selecting the corresponding checkbox in the Sugar Market connector screen, (Download Campaign Members to Distribution Lists) Sugar Market will sync down members of Salesforce campaigns into a distribution list, which can then be used as an include or exclude list.

2020-02-27 18-57-24d1

Notes regarding syncing Salesforce campaign 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
  • Sugar Market distribution lists do not contain blank or invalid emails

2020-02-27 18-57-44d2

Installing Sugar Market

Overview

There are 4 main components to the installation:

  1. Installing Sugar Market from the Salesforce AppExchange
  2. Customize your Salesforce options
  3. Modifying the Sugar Market Custom Objects
  4. Campaign Click Configuration

To install Sugar Market, you will need Salesforce credentials with administrator privileges.

Step 1: Login to Salesforce

Visit this URL and login with your salesforce credentials: https://login.salesforce.com/packaging/installPackage.apexp?p0=04t2J000000V9RU

Step 2: Select users to access

You will see the following screen where you can select who will be able to use the bundle. Select your preferred access. If you would like all users to access the Sugar Market components, then select 'Grant access to all users' and click Install. You may also select either of the other options that will restrict access to certain users. Doing so will limit the users who can access the marketing data available in the Sugar Market iFrame as well as data pushed up to custom entities installed with this bundle.

2020-02-27 17-43-00SF 1

Step 3: Verify install complete

Once the installation is complete, you will receive an installation successful message. If for some reason you did not then please record the error message and reach out to support.

Post-Installation Configuration

Now that the application is installed, you will need to configure it so that the Sugar Market components will show under-neath your Contacts and Leads.

Step 1: Customize Lead Layout

Click App Setup. Then select Setup > App Setup > Customize > Leads > Page Layout > Edit. You should see a screen similar to the image below. If you have multiple page layouts, you may be prompted to select the layout you wish to add the Salesfusion components to.

Step 2: Adding Custom Objects

There are 4 custom objects that you have the option to add to your Page Layout:

  • Web Activity
  • Email Campaign
  • Landing Pages
  • Event Management

Select the Related Lists section at the top left of the layout configuration. Here, you will see Web Activity, Email Cam-paigns, Dialogs, and Events Management. You can drag and drop these four items to anywhere on your page layout.

2020-02-27 18-13-42SF2

Step 3: Adding the Customer Journey

Select the Visualforce Pages. Drag "Section" to your desired location on the Lead Layout Card. After releasing the mouse, you will see this popup. Configure the popup as pictured:
Installing Salesfusion - Salesforce - Popup

Click "OK" to create the new section, and then drag the 'Lead Journey' to the new section.

2020-02-27 18-16-34SF3

Step 4: Customize the Lead Journey

You will need to configure the width of the lead journey VisualForce Page by selecting the wrench icon.

2020-02-27 18-17-14SF5

Select the properties to a width = 100%, height = 500 pixels, and check the "show scrollbars" option. Click ok, then click save in the toolbar to save the new customer journey section.

Step 5: Repeat steps 1-4 above on the Contacts record

Modifying the Sugar Market Custom Objects

If you would like more detail to appear on your four custom objects in the Lead and Contact card, then you can add additional fields to display additional information.

Note: Below are recommendations based on how many customers choose to customize, but please add/remove as you see fit for your organization.

Step 1: Edit the Lead Layout

Select Setup > App Setup > Customize > Leads > Page Layout > Edit. Select the "wrench" icon on top right of each custom panel (this will be the same for all 4 panels). 

2020-02-27 18-28-40SF11

Step 2: Select Fields

You will see a pop up window with options of fields you can choose to add to this view. After selecting your fields, choose OK. Below are the recommended fields to display for each custom object.

Email Campaigns Field Recommends:

2020-02-27 18-24-38SF9

Web Activity Field Recommends:

2020-02-27 18-21-32sf7

Landing Pages Field Recommends:

2020-02-27 18-19-55SF6

Events Management Field Recommends:

2020-02-27 18-23-28SF8

Step 3: Repeat steps 1 and 2 for the Events, Web Activity, and Email Campaign Objects

Step 4: Repeat steps 1-3 for the Contact record

Campaign Click Configuration

Step 1: Open the Email Campaign Object

Select Setup > Create > Objects > Select Email Campaigns. Click the word Email Campaign, not the edit button.

2020-02-27 18-42-00sff1

Step 2: Edit Layout

Email Campaigns have their own unique layout, so scroll down to the Page layouts and select Edit to configure the layout.

2020-02-27 18-42-33sff2

Step 3: Configure the layout

Configure the layout by selecting "Related lists.' This will present an option for 'Email Link Clicks'. Drag and drop this before the 'Open Activities' section shown below.

2020-02-27 18-42-51sff3

Configure this list view by selecting the 'wrench' icon.

2020-02-27 18-43-12sff4

Step 5: Add Fields

Add the selected fields. Then click ok.

2020-02-27 18-43-36sff5

Step 6: Save the layout

2020-02-27 18-43-57sff8

Verifying Setup

To make sure your setup is correct, you can open a contact or lead record. Scroll to the bottom of the page (or wherever you've added these entities), and you should see your four new sections. You will also see a new panel for Sugar Market Customer Journey that you added.

Note: In your layout options, you'll see the following legacy features that you can disregard.

  • Fields: Fusion Score, Fusion Score Value, Fusion Score Description
  • Buttons: Sugar Market (Legacy Feature)
  • Custom S-Controls: Sending Using Sugar Market (legacy Feature)

Salesforce Security

Salesforce guidelines require that you have added valid IP Ranges to your Salesforce instance in order for Sugar Market to sync with your database. To do this, please follow these steps:

  1. Log into you Salesforce.com account.
  2. Access the Setup menu located at the top of your screen.
  3. Select Administration Setup > expand the Security Controls section > select Network Access.
  4. Add the following IP address range:
    • 52.90.37.96 - 52.90.37.103
    • 54.72.104.95

Once complete - please refer to directions for Configuring your Sugar Market Connector.

Post-Installation Configuration - Lightning (Optional)

If you have Salesforce Lightning Experience enabled for your company you will need to follow the below steps to configure it so that the Sugar Market components will show underneath your Contacts and Leads. If you've already completed the steps above in classic view, then there is no need to follow these steps again.

Step 1: Customize Lead Layout

Click the Gear Cog. Then select Setup > Objects and Fields > Object Manager > Leads > Lightning Record Pages > Select Page to Configure > Edit.

2020-02-27 18-51-28ssf1

Step 2: Adding Custom Objects

There are 4 custom objects that you have the option to add to your Page Layout:

  • Web Activity
  • Email Campaigns
  • Landing Pages
  • Event Management

Select Related Lists on the left side of the layout configuration.

2020-02-27 18-51-52ssf2

Step 3: Adding the Customer Journey

On the left hand list, select Visualforce.

2020-02-27 18-52-09ssf3

Step 4: Customize the Lead Journey

You may adjust the Height and Label of the Journey as shown in red if desired, this is not a requirement.

Step 5: Repeat steps 1-4 above on the Contacts record

Configuring the Salesforce Connector

Accessing the Salesforce Connector

Your Sugar Market CRM Connector will provide access to setup & modify your password access, synchronization preferences and a time table of the last completed sync with your CRM. To access the Salesforce Connector, you will log in to your Sugar Market account. From the user menu in the upper right-hand corner of the screen, choose Account Configuration.

On the left hand side of the screen, you'll see a section for external connectors. After selecting Salesforce.com, you will then see the Salesforce.com Configuration screen.

Step 1: Syncing Credentials

First thing you'll do is enter the Salesforce.com username and password that Sugar Market will use to sync with your CRM. You may create a new user or use one that is pre-existing as Salesforce.com allows for concurrent logins. However, do note that all records created or updated by our sync will be attributed to the syncing user. The sync-ing user must have the necessary permissions to read and\or update all records which you wish Sugar Market to sync.

Fields:

  • Username : The Salesforce.com CRM username we will user to authenticate via your web services
  • Password : The password for above user

After entering the credentials as mentioned above, click Save Connection to the right.

Step 2: 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 Salesforce section for a deeper explanation on this component.

Step 3: 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.

Pull Data (Sync from CRM)

Download Accounts

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

Download Contacts

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

Download Leads

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

Download Opportunities

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

Download Events

Whether or not Sugar Market should sync down Events from Salesforce CRM

Download Campaign Members to Distribution Lists

Whether or not Sugar Market should sync down Campaign members from Salesforce CRM into a Distribution List.

Keep picklist values in Sync

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

Note: Sugar Market picklists are not restrictive, so values outside of the pick-list values will still be allowed.

Push Data (Sync to CRM)

Allow Sugar Market to Insert and Update Salesforce Records

Allow Sugar Market to Insert new or Update already existing contacts and leads. Once checked, the following options are available.

Insert as Lead – All new records will be inserted as a lead, regardless of if lead or contact in Sugar Market

Insert as Contact – All new records will be inserted as contacts regardless of if lead or contact in Sugar Market

Insert as Lead or Contact – All new records will be inserted based off of whether lead or contact in Sugar Market

Insert as Person Account – All new records will be inserted as a person account, regardless of if they are a contact or lead in Sugar Market.

Allow Sugar Market to update the 'HasOptedOutOfEmail' Field

When someone unsubscribes through Sugar Market, allow Sugar Market to up-date the Unsubscribe status of that Lead or Contact record in Salesforce

Allow Sugar Market to update the Score Field

If a CRM custom field is selected as the field to be used in a scoring profile, allow Sugar Market scores to be pushed into Salesforce as well. Field must be an integer field and exist on both contact and lead tables.

Allow Sugar Market to update delivery message

Allow Sugar Market to push up the delivered or bounced reason to a custom field in CRM. Field must be nvarchar(100)

Do not push email content (Saves storage space)

Omit the Email body from being pushed up to CRM, drastically reducing space consumed in the remote database.

Create New Tasks in Salesforce.com

Tasks can be created for contacts\leads through Sugar Market. This allows these tasks to be pushed up into Salesforce as well.

Push Web Activity

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

• Disabled: Do not push Web Activity

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

• Sugar Market Web Activity Entity: Web Activity will be pushed for the corresponding Account/Lead/Contact to the Custom Web Activity Entity installed with the Sugar Market App

 

Push Email Activity to:

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

• Disabled: Do not push Email Activity

• Activity Entity: Email Activity will be pushed to CRM as a completed Activity record for the corresponding Account/Lead/Contact

• Sugar Market Web Activity Entity: Email Activity will be pushed for the corresponding Lead/Contact to the Custom Email Campaigns Entity installed with the Sugar Market App.

 

Push Email URL Clicks

This will push up the URLs of each click in an email to the Custom Email Campaigns Entity installed with the Sugar Market App.

Push Landing Page Completion Data

This will push the landing page completion data to the Custom Landing Page entity installed with the Sugar Market App

Push Event Registration Data

This will push event registration\member data to the Custom Event entity installed with the Sugar Market App

Step 4: Remove Data from Marketing

When our bundle is installed, triggers are added which make an API call against ourdatabase when a record is de-leted, ensuring that these removed records are also deleted from Sugar Market's database. An autodelete report may also be added to remove records from Sugar Market with a specific critieria if desired.

Step 5: CRM Alerts

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

Note: Completing the bundle installation and connector configuration will not initiate the sync. You will need to contact Sugar Market to turn on the Sync.

Integrating With Campaigns

Users can integrate their form submission data with the campaigns in their CRM. Marketers who want to track the contacts via their campaigns built within a CRM such as Salesforce can do so with ease. With the Campaign Objects integration, the submission data automatically syncs up to your CRM campaign whenever a new lead fills out a form that has a campaign specified.

Setting up campaign objects in forms:

New campaign object action

How does it work?

1. Start building your form through Form Builder and go through the Basics step.

2. When you reach the Build Step, insert your form fields as normal.

The following are required for Campaign Objects to sync to your CRM:

  • Your form must have a First Name field and you must map it to the FirstName CRM field.
  • Your form must have a Last Name field and you must map it to the LastName CRM field.
  • Field submission values must be something that Salesforce can recognize, otherwise, the contact won't sync. For example, if a user submitted a string value of 'Hi my name is Jake' for a Revenue field which expects a number, then Salesforce won't be able to sync that submission up to the campaign.

3. Continue to the Actions step where you'll first add a redirect URL. Then, a new button displays where you can add a new form action.

New push to object form action

4. Click the form action button to see a dropdown with some options. Select the action Push to Campaign Object.

New push to campaign object form action

5. Select from the list of campaigns that are synced down from your Salesforce instance. There 2 important fields that you need to be set:

Campaign object modal

  • Campaign Object - Select the campaign in Salesforce to which you want to sync your form submissions
  • Status - Select the status for a lead that submits a form. Contacts are synced to your campaign in Salesforce with the specified status. These values are pulled from the campaign member statuses in your Salesforce Campaign.

6. Search and select your campaign to which you want to push your form submission records.

7. The Status field is then enabled for you to select the status for your submissions to have when they are pushed up to the campaign in Salesforce.

8. Click Okay. A new form action element appears under the Form Actions section on the page as shown:

New Campaign Object Form Action Element

The campaign object has been successfully associated to the form.

9. Publish your form. You are now ready to use your campaign object integrated form to start collecting and syncing your form submission data.

You have 2 options:

  • Embed the form into your page by grabbing the code that's presented after publishing your form.
  • Embed the form into a landing page built with Page Builder.

I've embedded my form onto my page. What happens now?

Now that you've placed your campaign object enabled form on your page, here's what you can expect. When a new contact fills out that form, that contact syncs up to your campaign in your CRM. Below is an example screenshot of how it works for the Salesforce CRM.

campaignObjectinPageV2.png

And here is that contact form submission showing up in the campaign within Salesforce:

Synced up contact to Campaign in Salesforce

 And that's it! You should see a corresponding record populate in the Campaign Members section for every record that submits the form.

Salesforce Package Patch Notes

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

Package Version 5.15

Rebranding on the Salesfusion logo to Sugar Market (applies to new installs only)

Package Version 5.14

Sugar Market has performed a refreshed update on our Salesforce package in order to simplify and streamline the integrations between both systems. For any of the legacy buttons and modules it's recommended to remove them from your page layout. Below are the changes to the package.

Salesforce Tabs

The following modules have been deprecated and no longer supported due to usage and to streamline Sugar Market best practices. (Due to limitations the following modules redirect to the Salesforce home screen and are renamed as Legacy Feature accordingly instead of being removed).

  • Web Tracker Tab now redirects to the Salesforce help screen and has been relabeled to Web Tracker (Legacy Feature)
  • Sugar Market360 Tab now redirects to the Salesforce help screen and has been relabeled to Sugar Market (Legacy Feature)

Contacts and Leads Modules Updates

  • Custom S-Controls > Sending Using Sugar Market has been deprecated for some time and has been renamed to Sending Using Sugar Market (Legacy feature)
  • Buttons > Sugar Market no longer redirects to the Sugar Market Journey in favor of the Sugar Market Journey iframe and has been renamed to Sugar Market (Legacy Feature).
  • Related Lists > Sugar Market Webactivity has renamed to Web Activity
  • Sugar Market Iframe's URL for the Sugar Market Journey has been updated from salesfusion360.com to iframe.salesfusion.com

Campaign Module Updates

  • Custom S-Controls > Sending Using Sugar Market has been deprecated for some time and has been renamed to Sending Using Sugar Market (Legacy feature)
  • Buttons > Sugar Market has been deprecated and has been renamed to Sugar Market (Legacy Feature)

CRM Mappings

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

Accounts

Salesforce Field

Sugar Market Field

--

AccountID (primary key)

Salesforce's Account ID (primary key)

ID

Name

AccountName

OwnerID (foreign key)

(if multiple owners, we pull the first Salesforce owner)

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.

Salesforce Field

Sugar Market Field

--

ContactID (primary key)

Salesforce's Contact ID (primary key)

ID

Salesforce's Account ID (foreign key)

AccountID (foreign key)

OwnerID (foreign key)

OwnerID (foreign key)

--

CRMType

--

CreatedDate

--

LastUpdate

CreatedDate

ExternalCRMCreatedDate

LastModifiedDate

ExternalCRMUpdatedDate

FirstName

FirstName

LastName

LastName

Email

Email

HasOptedOutOfEmail

OpOut

(Does not map)

Source

LeadSource

LeadSource

Title

Title

Phone

Phone

MobilePhone

MobilePhone

MailingStreet

MailingStreet

MailingStreet2

MailingStreet2

MailingCity

MailingCity

MailingState

MailingState

MailingZip

MailingZip

MailingCountry

MailingCountry

OtherStreet

OtherStreet

OtherCity

OtherCity

OtherState

OtherState

OtherZip

OtherZip

OtherCountry

OtherCountry

Opportunities

Salesforce Field

Sugar Market Field

--

OpportunityID (primary key)

Salesforce's Opportunity ID (primary key)

ID

Salesforce's Account ID (foreign key)

AccountID (foreign key)

OwnerID (foreign key)

OwnerID (foreign key)

Leadsource: Description

LeadSource

Description

Description

--

OpportunityName

Name

Name

--

Stage

StageName

StageName

Users

Salesforce Field

Sugar Market Field

--

UserID (primary key)

Salesforce's user ID (primary key)

ID

FirstName

First_name

LastName

Last_name

Username

Username

FirstName + LastName

Name

Cell

MobilePhone

Phone Extension

Extension

Address1

Street

City

City

State

State

Zip

PostalCode

Country

Country

JobTitle

Title

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

Salesforce Field

Sugar Market Field

--

TaskID (primary key)

Salesforce's Activity ID (primary key)

ID

WhoIs (foreign key)

ContactID (foreign key)

ContactName

Contact.FirstName + Contact.LastName

ActivityDate

DueDate

Description

Comments

Priority (value "Normal")

--

Note: If Sugar Market Task.Status is blank we will push the value "Completed" otherwise, we will push the value defined.

Custom Entities

Salesfusion__WebActivity__c (Web Activity)

CRM Field

Type\Size

Relationship

salesfusion__ClientHostname__c

Text(100)

Direct

salesfusion__ClientIP__c

Text(50)

Direct

salesfusion__IsNotified__c

Text(5)

Direct

salesfusion__Organization_Name__c

Text(100)

Direct

salesfusion__Duration__c

Number(16, 2)

Direct

salesfusion__EndDate__c

Date/Time

Direct

salesfusion__Hemisphere__c

Text(50)

Direct

salesfusion__StartDate__c

Date/Time

Direct

salesfusion__Timezone__c

Text(70)

Direct

salesfusion__Operating_System__c

Text(50)

Direct

salesfusion__Referrer__c

Text(100)

Direct

salesfusion__Keywords__c

Text(100)

Direct

salesfusion__Referrer_Query__c

Text(200)

Direct

salesfusion__Longitude__c

Number(10, 8)

Direct

salesfusion__Latitude__c

Number(10, 8)

Direct

salesfusion__Area_Code__c

Text(10)

Direct

salesfusion__City__c

Text(100)

Direct

salesfusion__Country_Code__c

Text(10)

Direct

salesfusion__Country_Name__c

Text(100)

Direct

salesfusion__DMA__c

Text(20)

Direct

salesfusion__Postal_Code__c

Text(25)

Direct

salesfusion__Region__c

Text(50)

Direct

salesfusion__ISP__c

Text(200)

Direct

salesfusion__ContactId__c

Lookup(Contact)

WebActivityObj.emailAddress =

ContactObj.Email

salesfusion__LeadId__c

Lookup(Lead)

WebActivityObj.emailAddress =

ContactObj.Email

CRM Field

Type\Size

Relationship

salesfusion__Web_Session_ID__c

Text(100)

Direct

salesfusion__Campaign_Actual_ID__c

Number(18, 0)

CampaignerActual.CampaignerActualID =

CampaignerLinkClick.CampaignerActualID

salesfusion__Campaign_ID__c

Number(18, 0)

Direct

salesfusion__Click_Date__c

Date/Time

Direct

salesfusion__Email_Address__c

Email

Direct

salesfusion__Email_Campaign__c

Lookup(Email Campaign)

CampaignerActual.CampaignerActualID =

CampaignerLinkClick.CampaignerActualID

salesfusion__Link_Order__c

Number(18, 0)

Direct

salesfusion__Link_URL__c

URL(255)

Direct

Salesfusion__Dialog__c (Landing Pages)

CRM Field

Type\Size

Relationship

salesfusion__Lead__c

Lookup(Lead)

Direct

salesfusion__Contact__c

Lookup(Contact)

Direct

salesfusion__Completed_Date__c

Date/Time

Direct

salesfusion__Dialog_ID__c

Number(18, 0)

Direct

salesfusion__Dialog_Name__c

Text(255)

Direct

salesfusion__Dialog_Response__c

Long Text Area(32768)

Direct

salesfusion__Start_Form_ID__c

Number(18, 0)

Direct

Salesfusion__Event_Management__c (Event Management)

CRM Field

Type\Size

Relationship

salesfusion__Lead__c

Lookup(Lead)

WebinarMember.Email = Contacts.Email

salesfusion__Contact__c

Lookup(Contact)

WebinarMember.Email = Contacts.Email

salesfusion__Event_Date__c

Date/Time

Direct

salesfusion__Attended__c

Checkbox

Value based on WebinrMember.Attended

salesfusion__Duration__c

Number(18, 0)

Direct

salesfusion__Event_Location__c

Text(255)

Direct

salesfusion__Event_Name__c

Text(255)

Direct

salesfusion__Lead_Source__c

Text(255)

Direct

salesfusion__Registered__c

Checkbox

Value based on WebinarMember.Registered

Salesfusion__Web_Campaign__c

CRM Field

Type\Size

Relationship

salesfusion__CampaignDate__c

Date/Time

Direct

salesfusion__Subject__c

Text(100)

Direct

salesfusion__Body__c

Long Text Area(32000)

Direct

salesfusion__Contact__c

Lookup(Contact)

CampaignerActual.ToEmail = Contacts.Email

salesfusion__Lead__c

Lookup(Lead)

CampaignerActual.ToEmail = Contacts.Email

salesfusion__FromEmail__c

Text(100)

Direct

salesfusion__Clicks__c

Number(18, 0)

Direct

salesfusion__Opens__c

Number(18, 0)

Direct

Salesfusion__WebInteraction__c (Web Pages)

CRM Field

Type\Size

Relationship

salesfusion__Duration__c

Number(16,2)

Direct

salesfusion__Referer__c

Text(250)

Direct

salesfusion__Title__c

Text(250)

Direct

salesfusion__URL__c

Text(250)

Direct

salesfusion__WebActivityID __c

Lookup(Web Activity)

WebActivityDetail.WebActivityID=

WebActivity.WebActivityID

Uninstalling Sugar Market

Disclaimer: Please note that uninstalling our bundle will perform the following:

  • Permanently delete all components in this package
  • Permanently delete all customizations you have made to these components
  • Permanently delete all data that you have created for all custom objects in this package
  • Permanently delete any reports, views, and custom tabs based on the custom objects in this package
  • Permanently delete any relationships and related lists associated with the custom objects in this package

Step 1: Navigate to Installed Packages (Setup > Installed Packages)

Click Uninstall next to the Sugar Market package.

Step 2: Select type of uninstall

The next page breaks down everything that will be uninstalled from Salesforce. Scroll down to the bottom of the page to select whether you want to save the data contained in our bundle or not. When you uninstall a package, by default, all its data as well as related notes and attachments are automatically saved as an export file. This file is available for 48 hours in case you need to recover the data. To reload the data, import the export file manually and recreate any relationships between objects. Some components can't be recre-ated and others require special treatment.

You can also prevent the package data from being exported by selecting the Do not save a copy of this package's data after uninstall radio button. If you select to not save a copy, you will be asked to confirm this in a browser pop up.

Step 3: Select final checkbox confirming uninstall of package, then click the Uninstall button

Step 4: Confirm Uninstall

Upon clicking the uninstall button in the previous step, you will be re-directed to the Installed Packages page. There you will see Sugar Market in the Uninstalled packages section, temporarily with an Uninstall Status of "In Progress".

Lightning Experience

Salesforce offers the ability to upgrade to the Lightning Experience. Lightning is the collection of tools and technologies behind a significant upgrade to the Salesforce platform. These upgrades are made to both the backend of the platform as well as the UI\frontend.

Both the Sugar Market Sync and Sugar Market Bundle support either the Classic and Lightning version of Salesforce. When upgrading from Classic to Lightning, the only thing that may be necessary is to update the page layouts, and add the Sugar Market custom entities and iFrame after upgrading.

Salesforce Shared Contacts (Contact Tied to Multiple Accounts)

SalesForce rolled out a feature in the Summer 2016 release that allows contacts to be associated to multiple accounts. This is done through use of a custom object, which handles these additional relationships. Due to the fact that it uses a custom object, it is not something that it is not supported at this time.

Last modified: 2020-09-16 20:43:49