Sooner or later, in the Salesforce ecosystem, you will find yourself writing code to customize a Salesforce organization. There are plenty of references about the Apex programming language, which is Salesforce's Java-esque proprietary language for controllers and triggers. Of course, you'll follow general programming best practices. You'll also want to keep a few things top-of-mind about Salesforce coding.
The basics are in place: you've set up your Salesforce org, and you've customized it enough to let your sales team work pretty efficiently. Now your users are asking for more. They want more automation to streamline their work, more customization to tailor their experience to their needs, more built-in business logic to improve the quality of report data. How much of this can you realistically do in-house? Is it time to outsource Salesforce work for your organization?
Salesforce is a terrific tool, and it continues to grow in capabilities as well as popularity. However, companies don't use Salesforce in a vacuum; they need to integrate it with their other systems to maximize value. Here are some pitfalls to beware of in Salesforce integration projects.
Now that you've implemented Salesforce and your team is reaping its benefits, it's time to step up your game. You're already rocking the CRM, streamlining the sales process, and using rich reports as feedback to keep on fine-tuning your sales machine. What's next? Your business processes. Here are some ways you can use Salesforce automation to improve business processes.
People who work in nonprofit organizations want to spend their time and energy on their primary mission, not entering data into a database. Unfortunately, nonprofits really do need to use some kind of database to manage relationships with their donors and their beneficiaries. From a human perspective, managing donor relationships is not much different from managing customer relationships. Managing your contacts in a spreadsheet might work when you're just getting started, but you'll do much better if you use a true Customer Relationship Management (CRM) system. The Salesforce Foundation makes it possible for you to cultivate donor relationships for little or no cost.
Salesforce User Adoption, Part II: Improving Salesforce User Adoption
Creating a great Salesforce app for your team is only part of the solution; the other part is getting your team to use the app. The best tool in the world is useless if it's not used! You've seen plenty of tips about signs your team has bought into using Salesforce. Your next step is improving Salesforce user adoption, and communication, training, and continuous refinement are the keys.
Many companies use Salesforce not only for sales-related CRM but also for managing disparate business processes. Salesforce record types can help administrators fine-tune their orgs and manage business processes for different users effectively.
Sometimes, administrators go a little overboard with custom record types. Even after reading the documentation, it can help to see how other admins utilize Salesforce record types. Here are some tips to help get you started.
Now that your company has rolled out its shiny new CRM system, you’ll want to make sure your team is fully on board. How can you track Salesforce user adoption? What are the signs you don’t have full buy-in from your organization on using Salesforce?
Of course, there are many useful reports available in the Salesforce Adoption Dashboards. To get the most benefit from those dashboards and reports, you'll need to quantify your expectations. How should your team use the system?
Working with Salesforce relationships is a little different from traditional relational database structures, but Salesforce has great tools for building custom data relationships and most people can adapt quickly to the SOQL model. As with any other system, though, there are a few "gotchas" to watch for when designing Salesforce relationships. I ran into one of these gotchas just recently. I needed a lookup relationship from our custom object to the standard Product table, Product2. No problem, right? Create the lookup field in the custom table, and there it is. Not so fast!