Entries in Salesforce (18)


Mapping Fields for Lead Converstion

A lot of valuable information can be captured on a lead and in most cases I see it is just lost. People just simply forget to go map the fields over to Contact/Account and finding the place to do this is not super obvious either. Using the latest release Summer 16' we'll show you below a quick reminder on how to map your lead fields in Salesforce to the proper fields on the Contact and Account objects so that the data is not lost.

Step 1)

Go to Setup-->Customize-->Lead-->Fields

Salesforce Lead Conversion Field Mapping Step 1 

Step 2)

Click on the Lead Field Mappping Button in the section between the standard Salesforce Lead fields and the Custom Lead Fields

Salesforce Convert Map Lead Fields


 Step 3)

Map the various Salesforce Lead fields to the fields on the Salesforce Contact and Account objects. During the SalesforceLead converstion these values will then transfer to those fields on the object of choice.

Salesforce lead to contact and account field mappingUpon Saving, you'll get a confirmation and all future Salesforce lead conversations should follow this pattern.


Salesforce Lightning Experience Roadmap

Below (obviously subject to change) is the lastest Lightning Experience Roadmap.

Click to expand


Salesforce Spring '16 Preview Documents Here

Excited to see the new Spring '16 Preview documents are online. Some really cool stuff coming down the way and I recommend when you get a minute that you take glance at what is coming!

Salesforce Spring ’16 Release Notes

Download as a PDF here


Custom Objects in Salesforce

In Salesforce, you're able create a custom object to store a particular set of data where users can create and manage that data all under a tab . Today, I'm going to show you how to create a custom object in Salesforce and place its data under a tab.


Building the Structure of the Custom Object :

In this tutorial, I'll be creating a "Reservations" custom object to be able to create and track customer reservations.

  • To get started, go to SetupApp SetupCreateObjects. Then click "New Custom Object."

  • Next, fill in the name for the object and click "Save."

  • Under Optional Features, make sure to allow for Reports, Activities, and Tracking Field History.
  • Next, I'm going to allow for Adding Notes and Attachments. Tick the checkbox to "Launch new Custom Tab Wizard" to customize the look and feel of the tab.

Creating the Tab for the Custom Object:

Now that I've built the structure of the custom object "Reservations," I can create the Tab where the object will be stored.

  • Pick the appropriate style of the tab and click "Next'.

  • Next, add the profiles you want to see and/or use the "Reservations" objects, then click "Next".


  • Then, determine which Salesforce apps you want this object to be available and click "Save".

  • Finally, under Custom Fields and Relationships, create the appropriate custom fields for the object. I'm going to add a new custom field "Reservation Date and Time"
  • Now, you can see the "Reservations" tab at the top where you can create new reservations.


Salesforce: Create Your Own App Marketplace

Last month, Salesforce announced Private AppExchange-- a feature that lets managers create a private app marketplace with a specific selection of apps totally private to their organization.

Click to read more ...


Salesforce Page Layout

In SalesforcePage Layouts allow for customization of UI pages for users in your organization. And often times throughout, you have pages of objects that might contain items that are not used by many users. Today, I'm going to explain how you can customize a Salesforce page layout with the fields, related lists, and custom links that suit your organization's use.

In the example below, I'll change the layout of the page Contracts. Note that you can "Edit" the current page layout of that object, but it's best to create a new Contract Page Layout and then assign it the default one.

  • To get started, go to Your NameSetupCustomizeContractPage Layout> Click on New.

  • Fill in the appropriate information and click "Save".

  • Next, drag and drop the fields, buttons, and related lists you want on the Contract Page Layout.

  • Then, click "Save".

Assigning Page Layouts

Now that you've created the page layout, you can assign it to the appropriate user Profiles in your Salesforce org.

  • Go back to the "Contract Page Layout" and click "Page Layout Assignment".

  • Pick the profile and assign the appropriate Page Layout. Then, click "Save".


Introducing Salesforce Connect Offline

Up until recently, using offline was unheard of. Fortunately, Salesforce recently released a new piece of software that allows you to do just that-- using Salesforce totally unplugged! Today, I'll be giving a brief introduction to Connect Offline: a client application that allows you to do your work in Salesforce offline.


The way Connect Offline works is by allowing you to perform tasks and changes to your Salesforce offline, then when connected online, it synchronizes the Connect Offline database with Salesforce's and pushes all changes made over to Salesforce.

What makes Connect Offline particularly convenient is that it lets you perform all typical Salesforce tasks smoothly. Here's a list of what you can do in Salesforce when offline:


The subset of data you can access in Salesforce while offline is called a briefcase. Admins can configure the parameters of a briefcase: thereby determining what data is accessible in a briefcase. For example, if you want to create a Connect Offline briefcase specifically for salespeople, then you would configure the briefcase to only include Leads and Accounts.


Connect Offline comes with support for mobile and various browsers and operating systems. It is also available for free for Enterprise, Unlimited, and Developer Editions. Also available for additional cost to Professional Edition. It will be interesting to see how this new software might change habits of how organizations work with Salesforce and how it might increase productivity among users.


Top 5 New Features in Salesforce Winter '14

It's that time again, Salesforce is about to introduce its next iteration: Salesforce Winter '14. The new release is said to be packed with valuable improvements that should enhance the overall experience as well as improvements under the hood. Today, I'm going to highlight the  5 most noteworthy features of Salesforce Winter '14:

Introducing Salesforce Performance Edition

Beginning in November of this year, Salesforce will be rolling out a brand new edition named Performance Edition. The edition will include all functionality of the Unlimited Edition on top of, which provides targeted customer data as well as

Salesforce Console for Sales

Salesforce Console for Sales basically combines the features of Agent Console and the Service Cloud Console together. This feature will prove very valuable, especially to salespeople. Instead of having to abandon the current page and go to the previous one, salespeople will be able to keep view of their critical fields and related lists and opportunities in a side panel. Check out the screenshot below of the new Salesforce Console for Sales.

Deployment Monitoring

The Monitor Deployments page will get new improvements. When deploying through the Migration Tool, you will now get more detailed information on the status of the deployment:

  • In Progress: this basically means that the deployment has started but is not finished yet.
  • Pending: This means that the deployment hasn't yet started but is queing to start.
  • Succeeded–All: All components of deployments and tests have succeeded.
  • Succeeded (partially): This means that the deployment went ahead with some errors either to some components or ones related to tests.
  • Cancel Requested: The status means that the deployment is starting to get cancelled.
  • Cancelled: This status means that the deployment has been fully cancelled.
  • Failed: This means that the deployment has failed and subsequently no changes were made to the org either because some files/components were missing or as a result of errors in tests.

Embedded Analytics

With Winter '14, you'll be able to embed performance analytics unto a page layout. This feature, if used properly, can be very helpful especially to organizations who rely on reports and performance, trends, status info. Here's a picture of it below:

Search for Configurations in "Setup"

This is probably my favorite feature of all. With Salesforce Winter '14 you'll be able to find Setup Menu Items and Setup Configuration Records by simply searching for them under Setup. Here are some of the new items you can search and find under Setup:

  • Setup Pages
  • Custom Profiles
  • Permission Sets
  • Public Groups
  • Roles
  • Users


These are only some of the new features that will be rolling out with Salesforce Winter '14. For more info on the new release of Salesforce, check out this page:


The Four Essential Salesforce Security Areas Every Admin Should Understand

With a Salesforce instance that encompasses many users of different hierarchical roles, a Salesforce admin should realize how important it is to lock down and protect data within the system. When designing a security policy in Salesforce, you should continously ask yourself this question, "Does this person/role have a need for access to this data?"

Today, I'm going to introduce and explain the four security cornerstones that should give you an understanding of how to better secure your Salesforce instance with a comprehensive security policy.

Organization Defaults:

Out of the box, the Organization-wide Defaults are simply wide open. These can be found under Setup> Security Controls> Sharing Settings. There, you'll find four options:

  1. Private
  2. Public Read Only
  3. Public Read/Write
  4. Public Read/Write/Transfer

The goal here is to keep these settings restrictive enough so intended users will have the ability to do their jobs without anybody else interfering. When setting the appropriate options in the Organization Defaults, I suggest you consider not only the current users and what data they need access to, but also of future employees. Understand that this is going to take quite some time to fully comprehend the organization-wide employee's hierarchical roles and implement the appropriate rules accordingly. Also, keep in mind that down the road when business demands it, you can always go back to relax the rules.

Role Hierarchy:

Found under Setup> Mange Users> Roles, this setting will basically show how users within your Salesforce instance are related to each other. Setting Role Hierarchy is important for two reasons: one, users in higher hierarchy will be able to see records of users below them and two: they will consequently inherit the security attributes of the Roles below them. As best practice, every user when first added into the org should be assigned with a Role so that the associated security settings are inherited.

Records Ownership:

In Salesforce, each record must have an Owner. As best practice, always take time in setting record ownership so that security settings in Organization Defaults are honored. Note that only active users can be set as owners of records. This is essential when, for example, importing data from legacy systems, where you'll have to activate an (inactive) user, then go back and deactivate that user again.

Sharing Rules:

Also found under Setup> Security Controls> Sharing Settings, the Sharing Rules allow you to set exceptions to the otherwise comprehensive Organization Defaults. A big benefit of Sharing Rules is that the rules are based on Record Owners, meaning all records owned by a particular group/role can be shared. Alternatively, you can set the Sharing Rules based on records that meet a specific criteria, such as Industry. Remember that Sharing Rules are there to set exceptions to the Organization Defaults and having too many of them might cause vulnerabilities.

I hope you find this high-level overview of Organization Defaults, Role Hierarchy, Records Ownership, and Sharing Rules helpful in setting your sales force security policy.