Transitioning to Salesforce Lightning


Transitioning to Salesforce Lightning | AppBuddy Blog

Posted by AppBuddy on Apr 19, 2017 8:30:00 AM | Share

With another Dreamforce event around the corner, if there’s one thing that’s certain, it’s that all Salesforce demos will be shown in the Lightning user experience. If you’ve been pushing out your migration to Lightning because of the time and effort involved, you are not alone. However, by now it’s clear that it’s no longer a matter of ‘if’ you will make the transition, but an inevitable ‘when’ you will transition.

AppBuddy is committed to promoting and educating our customers about best practices and Lightning migration.Because we understand that change is not always easy or fun—but it often leads to growth and opportunities—we held a webinar to discuss best practices to make an optimal and strategic transition to Lightning.

Since we had a great turnout and more questions than we had time to answer during the webinar, we’ve published the top questions from our Q&A below:  


Q: We have over 100+ reports that we are not looking forward to recreating. Are parameterized reports possible in Lightning?

Parameterized reports were  delivered  by Salesforce in Spring 2017. However, many of our customers use Grids  with charts in place of reports so that users can edit the records they are managing / monitoring.

This is one of the things we help customers with, even outside of the Lightning Experience. Reports are great, you can drill down to the actual record in Salesforce, but a challenge is that in order to take action on them, you have to open each record in a separate tab to make edits to that record. Our customers can use GridBuddy to replace or have something that matches the dashboards, so instead of going to a report they are taken to a grid where the filters and filter parameters that we have can be used even if the reports in the Lightning Experience don’t support those user filter parameters. Instead, GridBuddy takes the users to an editable grid that’s filtered to their specific domain or product. We recently helped a customer in this regard. They were doing forecasting and we took all of their forecasting reports and created grids that were filtered by product and territory specific to the users who were clicking into the grid.


Q: Service Cloud is behind Sales Cloud in Lightning development. How does your approach to Service Cloud users differ from your approach to Sales Cloud users?

A: Lightning does not have to be turned on at once for all users in an organization, instead it can be enabled by profile. Where one set of users would not gain a productivity increase, we recommend waiting to turn on Lightning until Salesforce closes the gaps and those users would benefit. An interim step that can be useful is to use GridBuddy within Service Cloud as described  here.


Q: Is the Grid component created with the GridBuddy install? Or does the customer have to create this custom component?

A: Currently, the Grid component feature is not part of the GridBuddy install. However, it is something that is delivered to customers that are already adopting Lightning as part of an implementation, so it’s already proven and out there. We are looking to roll this feature into the actual install shortly. So, you can expect to see it within couple of releases or within that timeframe. In the meantime, we are happy to install the component in its’ current state for our customers. 


Q: How long, on average, do Lightning migrations take?

A: It definitely varies by the size of the organization, how long it’s been around, and how many customizations they have. The short answer is: It’s probably a lot less than what you think it is, and it’s worth doing the level of effort. We had a Lightning migration that took one day, another one that took about two months, and we had another one that took six months. The one that took six months is an example of an organization wanting to achieve more than just migrating to Lightning, they wanted to use the migration as the impetus to streamline their business processes and eliminate some of their tech debt that had been lingering for six years. So that’s the approach they went after. Lightning migrations are really about what you want to get out of it. Another important thing to note, is that you can migrate in a phased approach, by setting some goals each quarter, you can enable specific users until you are ready to turn on all the lights. There’s a certain flexibility to it—it’s definitely worth doing the level of effort so you actually know what is involved.


Q: Can you share any lessons on converting S-Controls over to Lightning?

A: S-Controls are similar to JavaScript buttons, but often generate part of the user experience in the JavaScript, which becomes difficult to maintain. Like JavaScript buttons, S-Controls can be moved almost directly to buttons on GridBuddy, but are often worth inspecting to see if they can be optimized. If the JavaScript in an S-Control is creating HTML, it may be worth creating a new Lighting Component where the JavaScript is re-factored into an HTML component and a JavaScript controller—this is much easier to maintain. While a universal formula does not exist, it’s often a triage exercise to determine what path is easiest versus what path is best for long term success.


Q: How will Lightning impact/change building our Knowledge management system with Salesforce?

A: In the Lightning User Experience, Salesforce refers to Salesforce Knowledge as Lightning Knowledge. To explore the changes, here's a list of features comparisons between Salesforce Knowledge and Lightning Knowledge. In addition, here’s a list of limitations in Lightning Knowledge to consider.


Q: How does Lightning interact with TaskRay? Is there overlap between what TaskRay is currently offering and what Lightning can provide?

A: This question is best answered by TaskRay, but from the AppExchange, TaskRay is listed as "Lightning Ready." This designation indicates that TaskRay is ready to be used in the Lightning User Experience. You may need to upgrade to the latest version of TaskRay to reap the benefits.

Also, GridBuddy and TaskRay have collaborated on an offering where GridBuddy can be used with TaskRay to mass edit projects and tasks.


Q: Since we migrated some business units in our organization over to Lightning, we've consistently observed that the Lightning UI is slower than the Classic UI. How have other customers overcome this issue as they moved from faster to slower load times on many pages in the tool?

A: Salesforce continues to improve performance with every release, but there are still some challenges. A couple of important things to consider are the browser and laptop your users are using. Since Lightning Experience is more client side than "Classic," the speed of user's laptops and the performance of the JavaScript engine of the browser are important considerations. Additional information is covered in this thread from the Salesforce Success Community.


If you missed the live event or would like a replay, the webinar is now available on-demand for your convenience.

In this webinar, you will learn:

  • How to assess your organization for the transition
  • How to work around features not supported in Lightning Experience
  • How to plan the transition
  • The lessons learned from other customers that have made the transition with GridBuddy

Watch the on-demand webinar now! - Or - Learn more about GridBuddy 


Subscribe To The AppBuddy Blog

Or Leave A Comment


Stay Connected

Related Posts

Popular Posts

New Call-to-action