Button, Button, Who’s Got The Button?
“Button, button, who’s got the button?” is a children’s game in which one child hides a button in one of his or her hands, and another child tries to guess which hand it’s in. (Yes, before iPhones, children did indeed play games like this!) Believe it or not, there’s an equivalent game in Lightning Experience.
Mass Action Buttons (and Any Other List View Buttons)
In your Salesforce org, you may have created buttons that appear on a list view, allowing users to check a checkbox next to one or more records, and then performing some sort of action on all of the selected records. Alas, those buttons are not even visible in Lightning Experience. There are several reasons:
- Lightning Experience doesn’t display checkboxes next to records.
- As of Winter 16, Lightning Experience doesn’t support customization of list views. None of your custom buttons, whether mass action or not, will appear in Lightning Experience list views.
What can you do about this? Sadly, not much. At the moment, your only choice is to develop a custom UI (either in Visualforce or with Lightning Components) that emulates the Salesforce Classic functionality, displaying its own list view selector with a checkbox next to each record, and as well as a button that allows the user to perform the mass action. You’ll also need to come up with some way to launch your custom UI, since Lightning Experience doesn’t yet support adding custom buttons to list views.
Custom Buttons with URL Hacks
Yes, the word “hack” implies something that doesn’t quite play by the rules, but even so, people have been using Salesforce URL hacks for years now. A few examples:
- A custom button on the Contact page launches the standard Send Email page, with URL parameters that initialize the page with a specific email template, subject, and/or body.
- A custom button on the Account page that launches the standard New Opportunity page, with specific fields like Opportunity Name and Close Date pre-populated.
What can you do about this? Again, alas, not much. In some limited cases, you may be able to replace your custom button with an object-specific Quick Action or a Global Action, but the action types are limited: Create a Record, Log a Call, Update a Record, Visualforce Page, etc. The more likely scenario is that you’ll have to develop a custom UI (either Visualforce or Lightning Component based) that emulates the functionality that used to be supported with URL hacks.
Why, oh why, are my buttons disappearing?