We Read Through the Salesforce Summer ’17 Release Notes So You Don’t Have To

 

Go on and head outside! Our notes will be waiting for you when you get back.

Go on and head outside! Our notes will be waiting for you when you get back.

No time to read through the Salesforce Summer ’17 release notes? Not to worry. We’ll give you the highlights of our favourite new features. This release is packing a punch, especially around the new Lightning features, and brushing up on them will make you look like a rockstar as a Salesforce admin or consultant!

Prevent users from switching back to classic
Applies to: Lightning
Having trouble getting users to switch over to Lightning? You can now hide the option to switch to Classic via profiles and permission sets. Note: this permission doesn’t affect Salesforce1 users – they will still be able to switch back to Classic.

Access field history related lists in Lightning Experience
Applies to: Lightning
You can now track field history for Lightning. If field history tracking has already been set up in Classic, you can now see it automatically in Lightning. To set up new field tracking in Lightning, see below:

After clicking “Enable Lead History,” select the fields you want to track and remember to pull the lead history related list onto the page layout.

After clicking “Enable Lead History,” select the fields you want to track and remember to pull the lead history related list onto the page layout.

Keep related files and records when reps convert leads
Applies to: Lightning, Classic, Salesforce1 mobile app
When a lead is converted, files and related records are carried over to the resulting contact, account, person account and opportunity records. These related lists on leads are attached to the created account, contact or opportunity during lead conversion.

Relate accounts to leads quicker with account matching
Applies to: Lightning
Support for person accounts – if the lead does not contain a business name, Salesforce searches person accounts instead of business accounts.

Enhanced type ahead – type ahead search in the account name field now searches across all accounts, rather than searching only the user’s most recent accounts.

Multiple match – when a user clicks the account name field during lead conversion, a dropdown menu includes a list of all accounts that match the lead’s company name.

See opportunity stage history in Lightning
Applies to: Lightning
There is now a separate related list to track opportunity stage history, which tracks changes to an opportunity’s amount, probability, stage and close date.

screenshot 2

Use your Classic email templates in Lightning
Applies To: Lightning
You know all the effort that was put into building the Classic email templates? Well, the effort has not been wasted. You can now use the same email templates – text, custom HTML and letterhead – in Lightning. The templates are automatically made available when you insert a new email template.

Lightning for Gmail
Email templates
Applies to: Lightning
Lightning for Gmail is now generally available. You can use Lightning email templates to compose templates for Gmail.

Events sync
Applies to: Lightning and Classic
If you set up your users for both Lighting for Gmail and Lightning Sync, you can sync your Gmail calendar events to the events in your Salesforce org. Note: events sync only one way from Gmail to Salesforce, not the other way around.

Contacts sync
Applies to: Lightning, Classic, Salesforce1
Contacts sync in both directions between Google contacts and Salesforce.

Add and edit multiple order products
Applies to: Lightning
Users can now add more than one product at the same time.

Convert attachments to files
Applies to: Lightning, Classic
Attachments are on the way OUT and Files are IN! Now, what should we do with all our old attachments? You can use the attachments to files tool, which will be available on the App Exchange, to run bulk jobs that convert large numbers of attachments. You can then delete the attachments after they have been converted.

Private attachments can also be converted into files. Since Lightning does not support private files, users must make a converted private file public to keep it attached to a record. If users would like to keep it private, it will no longer be attached to the record, and they must access the private file from the files object.

Move Communities between orgs with change sets
Applies to: Lightning
Change sets are now available for Lightning communities and Salesforce Tabs + Visualforce communities. There are some limitations to deploying communities; for example, you can’t create a new community directly from an inbound change set. More limitations are highlighted in the release notes.

The release notes go into everything I’ve listed above in detail, but this should give you a good start. If you’d like to learn more about how these and other features may benefit your Salesforce org, please get in touch with our experts.

Headshot karen dixon cropWritten by Karen Dickson, Business Solutions Consultant at Traction on Demand.