Gaps Between Salesforce Classic and Lightning Experience.

  • Lookup fields in Salesforce Classic show record names regardless of sharing permissions. As a result, users can see the names of records that they can’t access.
  • In Lightning Experience and the Salesforce app, lookup fields respect sharing permissions and only show the name of records that the user can access. The one exception is owner lookup fields, which always display the name of the record’s owner, regardless of sharing permissions.
  • In Lightning Experience, page layouts support up to 35 lookup fields. In Salesforce Classic, page layouts support up to 40 lookup fields.
  • Lightning Experience includes new Files and Notes related lists, in addition to the classic Notes & Attachments related list.
  • You can create filters for related lists with Quick Filters.
  • Quick filters are different from regular list view filters in that they aren’t saved, persist only throughout your current session, and can’t be shared.
  • Quick filters aren’t supported in all related lists.
  • Quick filters also aren’t available for formula fields.
  • Feeds are not available
  • The icon to create a printable view of the list is not available( Now Printable View Button is available in Lightning )
  • The dropdown menu shows up to 2,000 views.
  • You can’t change the order of columns by dragging the column heading to a new position in the table.
  • The Recycle Bin isn’t available. Records deleted in Lightning Experience still go to the Recycle Bin, but users have to switch to Salesforce Classic to view or restore recently deleted records.
  • The Salesforce sidebar that appears on the left side of most pages in Salesforce Classic isn’t replicated in Lightning Experience.
  • Accessibility mode isn’t provided because it’s not needed in Lightning Experience. The interface is designed according to the latest accessibility standards, so screen readers are supported natively.
  • The close case layout isn’t available, but you can add closed statuses to case edit pages. From the Support Settings page in Setup, select Show Closed Statuses in Case Status Field.
  • Omni-Channel is available in Lightning Experience as a utility in the Service Console app.

  • Objects that aren’t supported in Lightning Experience can’t be routed using the Omni-Channel utility. For example, SOS isn’t supported in Lightning Experience, so you can’t route SOS sessions using Omni-Channel.

  • here are separate Open CTI APIs for Salesforce Classic and Lightning Experience. You can’t swap the two Open CTI APIs in custom JavaScript code because they behave and function differently.
  • Users with Accessibility Mode turned on must switch to Salesforce Classic to create and edit reports.
  • To follow reports, users must switch to Salesforce Classic. But, if Feed Tracking is enabled for Reports, then Chatter feeds are available in Lightning Experience.
  • Scheduled report refreshes from Salesforce Classic continue to work in Lightning Experience.

  • Reports exported from Lightning Experience never include a disclaimer that reads “Confidential Information – Do not Distribute” in the report footer. The disclaimer is excluded even if you disable the Exclude Disclaimer from Exported Reports setting in Setup.Instead of scheduling report refreshes, users can subscribe to reports in Lightning Experience.

  • In the Lightning report builder, you cannot hide report types when creating a new report in Lightning Experience. To limit the visible report types when creating a new report, select a report type from the left menu or use the search capability.

  • In the embedded Salesforce Classic report builder, you can hide report types. Report types hidden in the embedded Salesforce Classic report builder are also hidden in the Lightning report builder.

  • Pie charts from Salesforce Classic display as donut charts in Lightning Experience.
  • In Lightning Experience, negative values display on funnel charts.
  • In the chart editor, users can’t:
    • Add more than 4 measures
  • Cloning or creating email templates as a Partner Community or Customer Community Plus user is not available.
  • Deep Clone and Mass Delete are not available in Lightning Experience.
  • Custom buttons with a content source of OnClick JavaScript is not available in Lightning Experience.
  • Custom buttons with a content source of URL that pass parameters to standard pages in Salesforce Classic, such as pre-populating fields when creating a record is not available in Lightning Experience.
  • Manual User Record Sharing
    • This checkbox enables or disables manual sharing on user records via the Sharing button. This button is available in Salesforce Classic only.
  • Manager Groups
    • This checkbox enables or disables record sharing with managers and manager subordinates groups which is available via sharing rules, manual sharing, and Apex managed sharing. Manual sharing via the Sharing button is available in Salesforce Classic only.
  • Portal User Visibility
    • This checkbox enables portal users to be visible to other portal users in the same account or only to those users above them in the role hierarchy. Portals are available in Salesforce Classic only.
  • These page layout elements aren’t supported in Lightning Experience:
    • Expanded lookups
    • Mobile cards
    • S-controls
    • Tags
  • The following triggers aren’t supported:
    • Case Comment Triggers
    • Email Message Triggers
    • FeedComment Triggers
    • FeedItem Triggers
    • Group Triggers
    • Group Member Triggers
    • Group Record Triggers
    • Topic Triggers
    • TopicAssignment Triggers
  • The following layouts aren’t supported:
    • Feed Item Layouts
    • Group Layouts
    • Publisher Layouts
  • A common technique in JavaScript to navigate to a new page is to manipulate the window.location value. This technique isn’t possible in Lightning Experience. Use the navigation methods instead.
  • When running in Lightning Experience, Visualforce pages ignore the <apex:page> showHeader and showSidebarattributes. You can’t suppress the Lightning Experience header and navigation menu.
  • S-controls are an obsolete method of customizing the Salesforce user interface. They are superseded by Visualforce and Lightning Components, which are superior in every way.
  • S-controls aren’t available in Lightning Experience, and never will be. If your org depends on s-controls, you must replace them before you can move to Lightning Experience.

Thanks to Shivam for motivating me to write a blog on this topic.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: