Salesforce’s standard Lead Conversion leaves a lot to be desired, unfortunately.
For example, the standard conversion process does not create an association between a Contact and an Account unless you are:
1. Creating a new Account and new Contact;
2. Creating a new Contact to associate to an existing Account; or,
3. Creating a new Lead using an existing Account and an existing Contact associated to that Account.
Thankfully, they have provided the means to enhance the functionality without touching a single line of Apex. As a note, this presumes that your org is configured to allow Contacts to be associated with multiple Accounts AND that you’re expecting an Account, Contact, and Opportunity as an output of the conversion process. So, the scenario below works IF you are creating a new Account and associating it with an existing Contact (who has a primary relationship with a different Account).
This can be achieved by creating a Process in Process Builder for the Lead object that checks that:
– “IsConverted” flag is checked; and,
– “ConvertedOpportunityId”, “ConvertedAccountId”, and “ConvertedContactId” are not NULL.
This combination of fields validates that the Lead has been corrected converted and has the appropriate association with the downstream objects/records. The flow then takes the record ID of the Lead as its initial input (we created a custom field to store this value just as an internal validation). From that Lead record it returns the IDs in the “ConvertedAccountId” and “ConvertedContactId” fields. These ID values are then used to query the Account Contact Relationship object to determine if a relationship currently exists. If the answer is “No” then we create that relationship (which appears as the secondary relationship for the existing Contact). If the answer is “Yes” then we proceed to the next step. This step makes updates to the Opportunity record (e.g., changing a field value and updating the Oppty name per a specified naming convention).
Not without an issue…
There is, however, a final scenario in which Salesforce presents a glaring bug, limitation, issue (whatever you want to call it – but it’s been submitted to Salesforce as a bug) that this Process and Flow does not cover. This scenario is when you want to convert a Lead that points to an existing Account and an existing Contact who does not have an existing relationship with the specified Account. For example,
– Contact 1 has a relationship with Account 1
– You create a Lead with Account 2 and Contact 1
During the conversion process Salesforce ignores the Account specified and substitutes in the Account that’s associated with the Contact. Bug logs, unfortunately, provide no clues as to the cause. Workarounds do exist but…they require additional fields on the Lead which, in turn, rely on user input and would require an update to the Flow to take this additional data into consideration. Hopefully (fingers crossed), Salesforce responds to my case with an update in the near future!! If/when they do I’ll post an update.
If you’d like to see how CleanSlate can help you take full advantage of your Salesforce org please shoot us an email!
Salesforce has recently published a news release that is relevant to all users of middleware solutions.
To uphold the best practices in Security, Salesforce has decided to rotate some certificates out during January and February 2018. Google Chrome no longer supports Symantec-issued HTTPS certifications and is now going to use DigiCert-issued certificates instead.
This could have an impact if you and your company use a middleware solution like Mulesoft, Scribe, IBM Broker, etc. to interact with Salesforce once the certificates are updated by Salesforce. According to Salesforce, “To test your software and middleware solutions, use //certtest.force.com as the base URL of the API login URL.
- If you see an invalid username error or a different HTTP status code, then the test was successful.
- If you see a certificate trust error, then the trust was unsuccessful.”
For the vast majority of Salesforce users this will have no impact on your day-to-day experience. However, companies with middleware solutions are most likely going to require some configuration updates to trust the new root, intermediate, and other relevant certificates with DigiCert.
The deployment schedule for these updates certificates are: 1) Sandbox instances during the second week of January, and 2) Production instances during the second week of February. Additional information can be found at the following site, Salesforce Certificates change from Symantec to Digicert in Jan 2018. These updates should be thoroughly tested and validated in your Sandbox instances prior to the Production deployment.
If you would like to see what CleanSlate can do for you and your Salesforce Sales and Service Cloud orgs please contact us today!
What 20th-century invention goes best with beer and pizza? If you answered “robotics,” you’re right! (We also would have accepted “Buffalo wings.”)
Kidding aside, the CleanSlate team recently joined other technology firms around the Indianapolis area for a program called BeerBots. This event is a joint effort hosted by TechPoint Foundation for Youth and Sun King Brewery. The two companies want to ensure “Indiana’s underserved K-12 students have access to experiential learning opportunities that inspire the pursuit of STEM careers.” BeerBots is a fun way to show the promise of their efforts and share its relevance with the technology community.
On another level, it’s a chance to relax with coworkers while nerding out and working with robotics. Over the course of the event, our CleanSlate crew created robots, drank beer, ate pizza, and teamed-up to win prizes in battle. The game is simple: Robots battle for 1 minute, with a mandatory driver change at the 30-second mark. As the rules state, “Both offense and defense are permitted during the battle, and strategy is key.” The first-place team wins a trophy. Three other teams get the Badass Award, the Nerd Award, and the Terminator Award.
If you or your company are looking for a fun teambuilding activity, contact TechPoint Foundation for Youth for more information.