I have been developing with the SFDC platform for several years. In this time I have surmounted many a learning curve and devised copious work arounds for dead ends that I have run into because of system limitations. These challenges have been exciting to overcome but have often meant adding code that I knew I would one day be back to refactor. Salesforce has been sold as a clicks not code development platform but as anyone who has implemented SFDC knows there is a limit to where configuration alone can take you. I think this has created divisions between admins and developers. There has not been until now, a way to handoff your beautifully written and toiled over code solutions to your admin wizard friends. Along came Lightning and everything changes…
Adoption is still low because so many users are married to their Classic UI and are not inclined to invest in making the switch or are not sure where to begin. I think that Lightning adoption will grow as more developers understand the power of the framework. I am taking the Dev 601 course this week with Mike Topalovich. Although I have been building some Lightning Components over the past few months, I am finding lots of good nuggets that I have not yet discovered in this training. Kudos to Mike for his depth of knowledge on this subject and for keeping some levity through the tech talk!
Here are some of my favorite learnings so far:
- Components are your lego blocks… developing with SFDC is now modular by design!
- <Lightning:layout> component gives you the Grid for free! Crowds go wild… especially those who have toiled over SLDS styling for days….
- <aura:if> is magical…. I can see use cases with this involving custom component configuration by admins.
- Expose your components for use by your Admin friends and make them configurable by adding a Design Resource
- LEX is still a work in progress but there is something special about the SFDC developer community…. (just look at StackOverflow if you don’t believe me) I know that the innovation of folks working with SFDC LEX will grow exponentially now that we have just been given this awesome new set of tools for our toolkit!
….More to come!
Resources for learning online have exploded in number over the past five years. Many of these resources come with a moderate to hefty price tag, eg. Lynda.com or Pluralsight. I will not argue the merit of these subscription learning platforms as I have found their paid content to be valuable —particularly in the case of Lynda as they have free classes but their paid classes include resource files. There are however, many free options that may require a little more setup or self directed research by the user but are akin to the open source version of learning online. Salesforce has Trailhead, a learning platform packed with options and even badges that you can earn to display on your social media profile. The list is long and I don’t only consider the traditional tutorial platforms to be online learning. StackExchange is my personal learning trove. I am usually learning on the go, mid project as I need to understand a tool in a deeper way. StackExchange is perfect for this kind of learning as it is peer to peer but the FCC can’t shut it down because no music companies are being harmed in this trade 🙂
Here is a list for those curious about where to start:
76 of The Best Places to Learn to Code For Free
We recently went live with a team on Lightning only. Everything seemed to be going okay until the New Quote button disappeared suddenly from the quote related list on Opportunity on SF1. The button was there in LEX (Lightning Experience) but on mobile devices it was gone, just gone. And the worst part was it had been there the week before. I got on the SFDC help desk red phone and once I had my case elevated to tier 2, I had a very helpful rep research the issue for me. Come to find out SFDC R&D had removed the button from SF1 without notice because of some bugs they were seeing.
Well, not to be one to give up that easily I created a workaround. I was told the only workaround would be to create a Visualforce page which seemed really heavy handed, especially if SFDC is going to fix the issue sometime in the future.
Note, this workaround is designed for Lightning and SF1. If you are using classic then you would be better off going the route of a Visualforce page. Our users are going live on Lightning and are heavy mobile users so this functionality is critical for them. Enough talking and let’s get to the code…
This is a Lightning Component Action which means that once you have created the component you will need to create a Lightning Action that will use the code add the action to your page layout. Click into the links below to see the code in my GitHub repo. Note that you will need to wire up your own field validation (I have not added that as of yet). Happy coding!