Skip to main content Join us at TDX in San Francisco or on Salesforce+ on March 5-6 for the Developer Conference for the AI Agent Era. Register now.

#Trailhead Challenges2,383 discussing

Hands-on challenges are the “secret sauce” of Trailhead. Before searching for solutions to superbadge challenges, review the Salesforce Certification Program Agreement and Policies.

I am in the process of setting up our office with custom "Closed Won" sounds - however i want individual sounds for each different rep - how can this be achieved? 

 

I have completed the trailhead challenge to create the sound1 to play, but now i need to know how to apply this to my companies salesforce and customize a unique sound for each rep.

3 answers
  1. Nov 26, 2024, 6:10 PM

    Here’s a general guide on how to achieve this:

    1. Store Custom Sounds for Each Rep

     

    First, you'll need to ensure that the sound files for each individual sales rep are accessible in Salesforce. You have a couple of options here:

    • Static Resources: Upload custom sound files (e.g., MP3 or WAV files) to Salesforce as Static Resources. Each rep’s sound file will be named uniquely so that it can be easily referenced.
      • Go to SetupStatic Resources.
      • Click New to upload your sound files.
      • Name the file in a way that identifies the rep (e.g., "JohnDoe_ClosedWon" or "Rep1_ClosedWon").

    2. Custom Object or Field for Sound Selection

     

    You can either store sound preferences in a custom object or a custom field on the User record to map the specific sound to each rep. Here’s how:

    Option 1: Custom Field on the User Record

    • Go to SetupObject ManagerUser.
    • Create a Custom Field (e.g., "Closed Won Sound") of type Text or URL, where you store the path to the custom sound file. You can reference the Static Resource URL here, or if using a URL directly, you can point to the hosted sound file.
    • For example:
      • Text Field: "JohnDoe_ClosedWon.mp3"
      • Formula Field (if you want dynamic URL): HYPERLINK("/resource/JohnDoe_ClosedWon", "Sound File")

    Option 2: Custom Object for Sounds

     

    • Create a Custom Object called "Sound Preferences" that links to the User.
    • This object can contain fields like:
      • User (Lookup to User record).
      • Sound File (Text or URL to Static Resource or file path).
      • After this, create a relationship between the Sales Rep and the custom object, so each rep has a sound file associated with them.

    You can make use Use a Lightning Component or Visualforce Page to do it, also Process Builder and Flow

     

    Custom sounds for each sales rep can be a fun way to personalize the sales experience and keep things dynamic. If you're working with more advanced functionality, you can use Salesforce's new Omni-Channel feature for notifications or even push sound notifications via Salesforce Notifications (for mobile). However, for most cases, a combination of Lightning Components or Visualforce pages along with Process Builder/Flow should get you the desired outcome

0/9000

Hi all,

The instructions say to create a test class that uses a mock class to mock the callout. 

I think that the mock class uses a static resource to mock the callout and does the callout to the main class.  Does it then return a StaticResourceCalloutMock object to the test, with the return value from the mock callout set as the body of the mock object?

 

Thanks in advance,

Matt 

 

#Trailhead Challenges

6 answers
  1. Nov 13, 2024, 3:08 PM

    Hi all,

     

    Never mind--I see elsewhere that the mock class should return an HttpResponse rather than using a static resource.

0/9000

I am working on the Apex Integration Services-Apex rest Callouts module. When i am creating the File|New|Static resource for name enter GetAnimalResource and MIME type is text/plain, i am getting the below error:

Screenshot (72).png

 

#Trailhead Challenges

8 answers
  1. Nov 8, 2024, 12:13 AM

    Hi ,

     

    Workaround

     

    1. Use API Version 37 or Lower

      - When making the REST API request, set the API version to v37.0 or lower. 

      - Update your endpoint to reflect this version:

     

    Endpoint: https://{mydomain}/services/data/v37.0/tooling/sobjects/StaticResource

     

    2. Create the Static Resource from the Salesforce UI

      - Instead of using the API, log in to your Salesforce org.

      - Navigate to Setup > Static Resources.

      - Click New to create the static resource directly through the UI. 

     

    Not able to create/update StaticResources through tooling api with version 38.0 & above. 

    https://issues.salesforce.com/issue/a028c00000zilvAAAQ/not-able-to-createupdate-staticresources-through-tooling-api-with-version-380-above

0/9000

Hi, I am working on the "Apex Integration Services"  Module on the  "Apex REST Callouts" unit. I need to create a Static Resource in the developers console:

File -> New -> Static Resource

I enter the Name (GetAnimalResource). select the MIME type:text/plain and when I press submit i get this error:

UNKNOWN_EXCEPTION

An unexpected error occurred. Please include this ErrorId if you contact support: 1345751719-421449 (1976928079).

 

I've tried with other browsers and playgrounds but got the same error always.

Can you help me?

 

#Trailhead Challenges

7 answers
  1. Nov 8, 2024, 12:14 AM

    Hi ,

     

    Workaround

     

    1. Use API Version 37 or Lower

      - When making the REST API request, set the API version to v37.0 or lower.

      - Update your endpoint to reflect this version:

     

    Endpoint: https://{mydomain}/services/data/v37.0/tooling/sobjects/StaticResource

     

    2. Create the Static Resource from the Salesforce UI

      - Instead of using the API, log in to your Salesforce org.

      - Navigate to Setup > Static Resources.

      - Click New to create the static resource directly through the UI.

     

    Not able to create/update StaticResources through tooling api with version 38.0 & above.

    https://issues.salesforce.com/issue/a028c00000zilvAAAQ/not-able-to-createupdate-staticresources-through-tooling-api-with-version-380-above

0/9000