Tag Archives: Salesforce Developers

Spring ’16 – Highlighting 32 of the New Features for Salesforce Classic

Spring 16 Butterfly

Spring ’16 brings a ton of new features for Lightning and Classic. As most of us are not on Lightning yet, I’m only covering 32 of the highlights for Classic in this post.

You can access the full release notes by clicking the butterfly above.


Process Builder

  • Create Email Alerts for Tasks & Events
    • Also available on Workflow Rules, Approval Processes, and Flows

  • No more retyping names and descriptions for new versions

  • See entire field name in criteria

  • Drag & Drop Criteria Reordering

Reports & Dashboards

  • Option to exclude the Confidential Information Disclaimer

  • Access to Reports & Dashboards in user’s Private folder via Workbench

  • Ability to report on the top 300 File search terms queried by your users

Service Cloud

  • Block Sensitive Data in Chats

  • Supervisors can assign skill sets

  • Case Feed Filters

  • Drag & Drop Files into Case Feed Email

  • INTRODUCING: Work Orders
    • Work Orders are tasks to be performed on a customer’s product, typically in field service.
    • They can be associated with accounts, assets, cases, contacts, entitlements, service contracts, and other work order
  • Asset Hierarchy: An asset can have up to 2,000 child assets, and a hierarchy of assets can have up to 50 levels
  • Knowledge
    • Validation Rules for article types
    • Force.com and Chatter Plus users may be granted read access to articles without the Knowledge User license.
  • Service Console
    • Tab Hovers see highlights of tab contents
  • Macros: Now run on any feed-based layout

Sales Cloud

  • Get Mass Email Opt-Out and Bounce Alerts Before You Send

  • Data Import Wizard: Import Data from the following object Home Pages:
    • Accounts
    • Contacts
    • Leads
    • Custom Objects
    • Person Accounts



  • Broadcast Groups: a group where only group owners and managers can create posts.

  • Group Limits: 300 per user & 30,000 per org.

  • Email Announcements: Group owners and managers can now send email notifications to all group members regardless of their email notification settings.

  • @Mentions are now going to show the people you interact with most instead of alphabetical


  • Synonym Groups (words/phrases that are treated equally in searches) & Spell Correction are now available in the following
    • Knowledge Articles
    • Cases
    • Chatter Feeds
    • Files
    • Ideas
    • Questions


Data Import Wizard

  • Import Person Accounts

  • Display Import Status

  • Import Contacts & Person Accounts as Campaign Members
    • update Campaign Member Status

  • User Permission to import custom objects


General Administration

  • URL Custom Buttons & Links are now available in Lightning & Mobile.

  • Quick Actions update
    • Option to exclude from creating a feed item
    • Include custom success message

  • Picklist Updates
    • Restricted Picklists now in Beta:  Prevents users from importing/updating values that don’t exist.
    • Global Picklist pilot: Multiple Custom Picklist fields can get their values from the same master set.

  • Easier Migration to Lightning with “Migration Assistant”

  • Optimized parallel sharing rule recalculation, will help reduce time org is locked.

  • Login Forensics to help prevent identity fraud


Lightning Containers: Definitions & Environments You Can Use Them

Here’s a list of Lightning containers, what they are, and where you can use them.

  • Lightning Components – UI framework for developing dynamic web apps for mobile and desktop devices.
    • Environments:
      1. Lightning Experience
      2. Salesforce1 Mobile
      3. Mobile SDK Hybrid Apps
      4. Communities
      5. Standalone Lightning Apps
  • Lightning Component Tabs – Create a Tab to display a Lightning Component
    • Environments:
      1. Lightning Experience
      2. Salesforce1 Mobile
  • Lightning Components For Visualforce  Integrate Lightning components into Visualforce pages for a dynamic development experience.
    • Environments:
      1. Lightning Experience
      2. Salesforce1 Mobile
      3. Salesforce Classic
      4. Mobile SDK Hybrid Apps
      5. Communities
  • Lightning Apps – An App consisting of Lightning Components.
    • Environments:
      1. Lightning Experience
      2. Salesforce1 Mobile
      3. Mobile SDK Hybrid Apps
      4. External Sites
  • Lightning Out – Directly embed lightning components cross domain 
    • Environments:
      1. Mobile SDK Hybrid Apps
      2. External Sites
  • Lightning Extensions – A mechanism for using custom-built components to replace existing components in the Salesforce1 Mobile App.
    • Environments:
      1. Lightning Experience
      2. Salesforce1 Mobile


Lightning Containers and Environments Chart
Credit: Skip Sauls [@SkipSauls] Salesforce Director of Product Management – Lightning Components & Customizations Special thanks to Samantha Ready [@Samantha_Ready] for sharing on Twitter.

25 Things I Learned After 5 Years as a Salesforce Admin

Wonka 5 Years v2

It occurred to me the other day that I’ve been a Salesforce Admin for over 5 years now. That got me thinking about the things I’ve learned or wish I knew sooner.

  1. Your personal development is a journey, not a destination. 

  2. You have to be all in.  It’s like Mr. Miyagi would say: Either Salesforce Admin do “yes” or Salesforce Admin do “no.” You Salesforce Admin do “guess so,” get squish just like grape.

  3. Bosses that support your work-life balance, personal development, and appreciate your Salesforce skills are very important to your success.

  4. Executive sponsorship is really important.

  5. If there is a lack of accountability in your company, you’re going to have a bad time.

  6. Designing & developing a solution for a bad business process is not fun.

  7. Speak in a language your audience can understand.

  8. It’s impossible to reach expert level. 

  9. Understand what Apex is capable of.

  10. Self-sufficient users will make your job much easier.

  11. Automation is great, but too much of anything can become problematic.

  12. Stakeholders who have a good idea of what Salesforce is capable of will make your job easier.

  13. Your users are more important than you are.

  14. It’s OK say “I don’t know.”

  15. Trying to be a hero can backfire and cause you to burn out.

  16. Having a good change management process is very important.

  17. Project documentation is very important.

  18. Don’t neglect the little things.

  19. No matter what you do, you will always have some users that just don’t get it.

  20. Know when to turn to the appexchange.

  21. Be an evangelist, but don’t drink the Kool-Aid.

  22. Participation in the Salesforce Community can be rewarding in many ways.

  23. Things that seem impossible now will turn into  things you can do in your sleep.

  24. Knowing the right questions to ask can make all the difference.

  25. Many of the most valuable things you learn only come after you’ve screwed something up.  

“What The Heck Does This Error Mean?” Simple Explanations of Common Errors

Apex Error

If you know how to troubleshoot a few common Apex errors, you can resolve issues faster.  Technical Architects and Developers will love you for not asking them as much.

Furthermore, If you can teach your users what some of the Apex and other common errors mean, they might be able to resolve something on their own without coming to you.  

Here are some phrases to look for.

 “Attempt to de-reference a null object”

  • Most often, this means that a record involved in the process is missing a key piece of data referenced in the code.

  • It could also mean the user who triggered this process doesn’t have access to a field, object, or record type.



  • There is a validation rule preventing the record from being updated.


“System.LimitException: Too many query rows: 50001

  • You get this error when when Apex Code tries to query more than 50,000 records, which is the Salesforce limit for Apex.
  • Solution:  Try to use more filters in the search. A code update may also be needed


Other “Exceptions”


“Insufficient Privileges”  

  • The user doesn’t have access to edit or view a record.
  • Could also happen due to a lack of user permissions


“Insufficient access rights”  -or-  “Invalid access rights on cross reference ID”

  • Basically, this is the Data Loader version of Insufficient Privileges.


“ID value of incorrect record type”

  • Another Data Loader error, caused by a funky ID on your source file.
    • Check your ID’s, are they valid?
    • Could also be that you mapped a text column to the Salesforce ID column.


“Your account has been disabled”  (The dumbest error)

  • It happens on Approval Processes and has nothing to do with the user who received the error, but they’ll think it does and come to you quite concerned.

  • What it actually means is that one (or more) of the steps on an Approval Process contains an inactive user on the approver list.


Did I leave any out? Any other tips for troubleshooting errors?  Comment below.