Prework and Notes
- Grab a pen and paper. You may want to jot down notes as you read the requirements.
- Complete all steps in this superbadge in Salesforce Lightning Experience.
- Some of the terminology used in this superbadge is descriptive and may not match the name as it appears in the user interface (UI). This is to test your knowledge of Salesforce features and ability to select the correct feature to satisfy a business need.
- Where possible, solutions will be evaluated based on the expected outcome instead of a specific formula syntax. We recommend using sample data to test and validate your activated solutions.
- All solutions in this superbadge unit must be built with declarative, out-of-the-box functionality.
- Descriptions and help text* must be set where possible for all data validation solutions in order to pass the challenges.
*Note: While it's required to populate help text to complete many of the challenges in this unit, excessive help text can negatively affect the user experience, especially for screen reader users and people with attention disorders. In the real world, admins label fields clearly and succinctly and use help text only when the user needs more information about the data housed there.
Sign Up for a Developer Edition Org with Special Configuration
To complete this superbadge unit, you need a special Developer Edition org that contains special configuration and sample data. Note that this Developer Edition org is designed to work with the challenges in this superbadge unit.
Sign up for a free Developer Edition org with special configuration.
Fill out the form. For Email address, enter an active email address.
- After you fill out the form, click Sign me up.
When you receive the activation email (this might take a few minutes), open it and click Verify Account.
Complete your registration by setting your password and challenge question. Tip: Write down your username, password, and login URL for easy access later.
You are logged in to your superbadge Developer Edition org.
Now, connect your new Developer Edition org to Trailhead.
Make sure you’re logged in to your Trailhead account.
In the Challenge section at the bottom of this page, select Connect Org from the picklist.
On the login screen, enter the username and password for the Developer Edition org you just set up.
On the Allow Access? page, click Allow.
On the Want to connect this org for hands-on challenges? page, click Yes! Save it. You are redirected back to the Challenge page and ready to use your new Developer Edition org to earn this superbadge.
Now that you have a Salesforce org with special configuration for this superbadge unit, you’re good to go.
The fashion company Rambunctious Armadillo Socks (RAS) is a large retailer with more than 1,000 employees, and the company is growing quickly. But growth is often accompanied by growing pains, and RAS is no exception. The company has a large volume of opportunities, accounts, and cases in its Salesforce database and has experienced a number of data quality issues.
RAS leadership is looking for quicker insights from the company’s Salesforce data and has reported a variety of frustrations. Executives are finding that they need to perform some calculations outside of Salesforce. They’ve also discovered that a variety of records are related to the wrong records in lookup relationships, which makes analytics unreliable. And stakeholders report that critical data is often inconsistent, incomplete, or inaccurate.
As a Salesforce admin at RAS, you’ve been asked to use out-of-the-box functionality to improve data quality and enhance the user experience to make data entry and analysis a breeze.
This section represents the requirements for RAS’s data standardization needs.
Display Key Opportunity Data
The RAS sales leadership team wants a quick way to gain insights about each account’s opportunities. After meeting with the stakeholders to understand their highest priority data needs, you’ve identified three opportunity summaries to display in the newly created Opportunity Revenue section of the Account Layout. Build your solutions based on the requirements outlined below.
Won Opp Revenue
|The total revenue generated for all Closed Won opportunities
Open Opp Expected Revenue
|The revenue expected from all open* opportunities based on both the opportunity amount and likelihood of winning the opportunity
High Probability Opp Revenue
|The total revenue associated with open opportunities where the probability is greater than or equal to 75%
*Any opportunity where the stage is not closed won or closed lost is considered open.
Address Incorrect Record Relationships
It has come to the Salesforce team’s attention that users occasionally attach the wrong records in lookup fields. Based on conversations with end users and leadership, you’ve identified two areas that need immediate attention.
Primary Campaign Source
RAS tracks primary campaign sources for all opportunities to understand where efforts are successful and where they need redirection. The Campaign object has two different record types: marketing and sales. All opportunities should be tied to a sales campaign, but it’s been discovered that some users are mistakenly attaching marketing campaigns.
Create and activate a solution for the standard Primary Campaign Source field on the Opportunity object that will only show users sales campaigns. Users should not be able to save the record if the wrong campaign type is selected. If the user does try to save the record with the wrong type, they should see the message, “
Only Sales Campaigns can be added as a Primary Campaign Source for an Opportunity.”
Wrong Assets Attached to Cases
Your team also identified a number of cases where the related asset belonged to a different account than the one related to the case. Your colleague was quick to build a solution that would only show assets with the same account as the case in the lookup field. You even helped test the solution and confirmed it was working per the requirements.
But now that this solution is live in production, an integration that creates and updates case records is breaking. After some impressive detective work, you’ve determined that the integration is only breaking when all of the following conditions are true.
- The integration is attempting to update a case. (The integration can create new case records without issue.)
- The case it is attempting to update was created before the asset lookup solution was implemented.
- The case record has an asset from the wrong account.
The RAS Salesforce team and its stakeholders have not prioritized updating old case records that have the wrong assets attached. That work may happen in the future as part of data cleansing efforts but for now, the priority is new cases. With that in mind, you need to update this solution so that it will continue to show users only assets related to the same account as the case. However, this solution should not prevent the integration from updating other fields on an older record.
But, hold on. Being the super smart admin that you are, you know that this update could lead to some of the same data quality issues the org experienced before. Your partner on this project has built a companion solution with the name Asset_Must_Match_Case_Account that will prevent the record from being saved without an accepted asset record only if the Asset field is populated or changed. This solution will not prevent unrelated fields from being updated on older records. Once you’ve made the appropriate updates to get the integration back up and running, activate your partner’s solution to maintain true data quality.
Standardize Regions and Subregions
Those cheeky armadillo socks are a global sensation! RAS has been using the custom Subregion field on the account to look for sales and service trends across its customer base. But recently, it has come to the Salesforce team’s attention that stakeholders also want to see trends for the larger regions that each subregion belongs to. Additionally, these regions and subregions are a standard for RAS, and end users should see the same options on any object where “region” is a data point.
Create a solution with the label and name
Region that will allow users to select a region from a predetermined list based on the table below. This list of regions should be able to be reused across objects. Then, add this list to the Account object with the same label.
Next, use the existing Subregion field on the Account object to convert the list items to a set that can be used across objects. Finally, build a solution for the Account object where the subregions displayed to the end user are based on the region selected. Reference the table below for your configuration.
- Central America
- North America
- South America
- Central Asia
- East Asia
- South Asia
- Southeast Asia
- Central and Eastern Europe
- Nordic countries
- Southern Europe
- Western Europe
Middle East and North Africa
- Middle East
- North Africa
- Australia and New Zealand
- Pacific Islands
- Central Africa
- East Africa
- Southern Africa
- West Africa
Show Offered Services for Consulting Partners
RAS works with a wide range of accounts for its information technology (IT) consulting needs. Some accounts specialize in one niche area while others provide a buffet of services for RAS to choose from. Currently, RAS users utilize a variety of methods to document the types of services each account offers. Some use the Chatter feed, some use Notes, and others use sticky notes at their work station. Sounds like the perfect candidate for data standardization!
Create a solution with the name
Offered_Service that will be related to the account. Each account can have multiple offered services, and every offered service record should have an account. The solution should support clear reporting for a variety of analytics needs. This solution should contain a list named
Service_Type with the following options to select from.
- Artificial Intelligence (AI)
Finally, make sure users can see each account’s offered services on the Account Layout and that Service Type is clearly displayed.