Skip to main content

#Trailhead Challenges1,556 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. ** NOTE ** : If you were able to get a response that solved your issue, please mark it as the 'Best Answer' to help other Trailblazers. If the issue persists after 48 hours, create a Trailhead Help case at https://help.salesforce.com/s/support for further assistance.
3 answers
  1. Sep 7, 5:58 AM

     Hi @Anubha Khandal, 

     

    This looks like a Trailhead Playground/org-data mismatch rather than an issue with your challenge steps. 

    The challenge is expecting a role named VP Human Resources, but some newer Playgrounds appear to have SVP Human Resources instead. The challenge validator specifically looks for the expected role name. 

    I would suggest checking Setup → Roles first. If SVP Human Resources exists but VP Human Resources does not, you can edit the existing role and rename it to VP Human Resources, then make sure the required hierarchy is correct: 

    CEO → VP Human Resources → Recruiting Manager  

     

    There are also recent Trailblazer Community reports of the same issue, where renaming SVP Human Resources to VP Human Resources resolved the challenge.  

     

    If you prefer not to modify the existing Playground, you can also try creating a new Playground specifically from the challenge/module, since Salesforce notes that some challenges require a particular org configuration or data.  

     

    After making the change, return to Trailhead and click Check Challenge again.  

     

    Hope This Helps!!

0/9000

Body: I’m stuck on the Trailhead challenge “Handle Field Access with a Permission Set” (Recruiting app). The checker reports it can’t find a permission set that grants read/edit on all Job Application fields except Position and Candidate (read-only). I’d appreciate guidance on what I’m missing. 

 

Requirements I’m following: 

 

Create a permission set: 

Label: Manage Job Applications 

API Name: Manage_Job_Applications 

License: None 

Job Application object permissions: Read, Edit (no Create/Delete/View All/Modify All) 

Field-level security on Job Application: all fields readable and editable, except Position and Candidate (read-only) 

What I configured: 

 

Permission Set 

Label/API/License match the spec: Label “Manage Job Applications”, API Name “Manage_Job_Applications”, License “None”. 

Object Settings > Job Application: 

Object Permissions: Read and Edit only; Create/Delete/View All/Modify All are unchecked. 

Field Permissions: 

I enabled Read and Edit for all fields, then unchecked Edit only for Position and Candidate, keeping Read checked. 

I re-verified that every other field has Edit=ON, and Position/Candidate have Edit=OFF. 

Job Application object definition 

Label: Job Application; Plural: Job Applications 

API Name: Job_Application 

Record Name: Job Application Name (Auto Number; Display Format: JA-{0000}) 

Optional features: Allow Reports=On, Track Field History=On; Allow Activities/Allow in Chatter Groups/Enable Licensing=Off 

Classification: Allow Sharing=On; Allow Bulk API Access=On; Allow Streaming API Access=On 

Deployment Status: Deployed=On 

Search Status: Allow Search=Off (can turn On if required) 

Org Language/Locale: Language=English; Locale=United States 

Fields on Job Application 

Position (API: Position__c): Lookup (or Master-Detail) to the Position object. 

Candidate (API: Candidate__c): Lookup to the Candidate object. 

Both are English labels/API names. I did not create similarly named extra fields (e.g., Position_Lookup__c). 

Profiles/Assignments 

Error message (excerpt): “Couldn’t find the ‘Manage Job Applications’ permission set that grants read and edit access to all Job Application fields except Position and Candidate.” 

 

Troubleshooting already done: 

 

Switched org Language/Locale to English/United States, waited a few minutes, and re-ran the check. 

Reconfirmed Job Application > Field Permissions: Position/Candidate are Read=On, Edit=Off; all others Read/Edit=On. 

Reconfirmed object permissions are exactly Read+Edit only. 

Verified Position/Candidate field data types and lookup targets. 

Ensured there are no duplicate or similarly named fields. 

Verified object labels and API names conform to the spec. 

 

Open questions: 

 

Does the checker require an actual user assignment of the permission set? 

Are there any other commonly missed toggles (e.g., View All/Modify All flipped on elsewhere, permission set group interactions, metadata propagation delays)? 

What I can provide: 

 

Screenshot of the permission set (Manage Job Applications) > Object Settings > Job Application > Field Permissions showing Position/Candidate Edit=Off and all others Edit=On. 

Job Application Fields & Relationships list (with Position__c/Candidate__c types and lookup targets). 

Org Language/Locale settings. 

User permission summaries if needed. 

 

Goal: Identify the minimum changes needed for the checker to pass (e.g., turning on Allow Search, changing Record Name to Text, assigning the permission set), so I can re-run the challenge successfully. 

 

Thanks in advance for your help and any insights! 

 

 

“Handle Field Access with a Permission Set” keeps failing. I made “Manage Job Applications,” gave Job Application Read/Edit, and set FLS Edit for all fields except read-only Position/Candidate. Both are lookups. EN/US locale. What am I missing?

 

 

 

#Trailhead Challenges

2 answers
  1. Aug 27, 6:37 PM

    The wording can not find a permission set that grants... is the clue — the grader looks the set up by API name first, then checks the field pattern. Two things trip most people here: 

     

    1. The API name must be exactly Manage_Job_Applications (underscores, not spaces). If it is even slightly different the grader cannot find it and reports exactly that message. Open the permission set and confirm the API Name reads Manage_Job_Applications. 

     

    2. Position and Candidate must be Read-only, meaning Read checked and Edit unchecked — not hidden. If you unchecked Read as well they count as not readable and the all-fields-readable check fails. Verify both show Read on, Edit off. 

     

    Also worth a quick pass: 

    - Every other Job Application field needs BOTH Read and Edit checked. Scroll the entire field list — a single field left without Edit fails it. (Any formula field can only be Read, and that is expected.) 

    - Object permissions: Read and Edit only, which you have — no Create, Delete, View All, or Modify All. 

     

    Nine times out of ten on this one it is the API name, or Position/Candidate being hidden instead of read-only. Fix that and recheck. 

     

    if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

0/9000

im working on (Turn On Your New Lead Nurturing Agent

) under the section (Configure Data for Your Agent).  

The below are the instructions  

(

  1. Click New Library +.
  2. In the pop-up window, enter the following:
    • Name: Welo Customer Policies LibraryCopy
    • API Name: Auto-generated
    • For Description, paste the following: A collection of Welo’s official customer-facing documents, including return policies, warranties, service terms, and support guidelines.Copy
  3. Click Save. Your data library is now set up and ready for you to start adding sources, giving your agent the information it needs to deliver accurate, customized responses for your business.
  4. For this project, let’s add a web source. This type of data lets your agent search relevant websites to enrich its knowledge and deliver more accurate results. Click the Data Type dropdown and select Web.
  5. For this project, let’s add a web source. This type of data lets your agent search relevant websites to enrich its knowledge and deliver more accurate results. Click the Data Type dropdown and select Web.
  6. Toggle on the Turn on Web Search button to enable it.

) 

but the ui seems to not support these instuctions wt im trying to say is, i cant find the "

New Library" button instead i have a "Add data" within which i can then select either a "Upload file " or a custom "retriver" 

i tried surfing through both the options but i cant find any sections that would support step 4, 5, 6.  

 

im not sure of how to proceed pls help me  

 

and im facing a similar issue with a different Badge called (Build Your First Sales Coach:

Configure and Activate Your Sales Coaching Agent

) even in this perticual lab the instructions dont match/support the ui  

 

IF ANY ONE KNOWS HOW TO FIX THIS PLS HELP ME OUT!!

 

 

why is the instuctions outdated

 

 

 

#Trailhead Challenges

8 answers
  1. Jul 12, 6:02 PM

    You're running into the same UI-vs-instructions gap several people are hitting on recent Agentforce modules - Trailhead's written steps still describe the older "New Library" flow, but the current Agentforce Data Library UI uses "Add Data" with Upload File or Add Custom Retriever instead. Assumption: since I can't see your org directly, this is based on the same pattern reported on other Agentforce modules recently, not a confirmed fix for this exact badge. Workaround that has worked for others: use Add Data, Upload File as your data source instead of creating a New Library - the library gets created implicitly when you add the first file. For the Web source step, check AI Models or Retrievers first; many orgs already have an active Salesforce-managed Web search retriever available, which can satisfy that requirement without a separate manual Web data type toggle. If Check Challenge still fails after the file-based workaround on either badge, that is worth a Trailhead Help case at help.salesforce.com/s/support flagging the instructions-vs-UI mismatch so the module gets updated.

0/9000

Hi Trailblazers,

I manage a local-services website and I’m exploring how Salesforce could support a privacy-conscious enquiry workflow.

The workflow should collect only necessary information, restrict access to authorised users, record consent, and remove enquiry data after 90 days unless it must be retained for a legal reason. Sensitive message content should also stay out of unnecessary logs and reports.

Which Salesforce products or Trailhead modules should I study for:

• Permission-based record access 

• Consent management 

• Flow automation 

• Data-retention rules 

• Secure enquiry handling

I would appreciate recommendations from anyone who has built a similar privacy-conscious workflow. 

https://bangalore.sweetypatel.net/

 

 

#Trailhead Challenges

0/9000

Looking for a Remote Salesforce Internship Opportunity (Paid or Unpaid)  

 

Hi Trailblazers! 👋 

 

I'm Peer Abbas Ali Shah, a Computer Science (AI) graduate from Pakistan with 1 year of hands-on experience as a Salesforce Admin & Developer Intern at Cyber Tech Infinity. I've worked across Object Manager, Flow Builder, Validation Rules, Reports & Dashboards, Profiles/Roles/Permission Sets, and have practical exposure to Apex, LWC, and SOQL. I'm also actively progressing through Trailhead's Admin and Developer pathways while preparing for my Salesforce Certified Administrator exam. 

 

I'm looking to connect with startups, nonprofits, consulting partners, or growing teams who could use an extra pair of hands on their Salesforce org — whether that's configuration, automation, data cleanup, or reporting. I bring reliability, a fast learning curve, and genuine enthusiasm for the platform. 

 

If you know of any openings, referrals, or teams looking for motivated Salesforce talent, I'd really appreciate a connection. Happy to share my resume directly too! 

 

#TrailblazerCommunity #Salesforce Developer #Salesforceadmins  #Ohana #Trailhead Challenges  #Salesforcecommunity #Agentforce  #Remote Internship

0/9000

node:internal/modules/cjs/loader:1386 

  throw err; 

  ^ 

 

    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)      

    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) 

    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)         

    at Function._load (node:internal/modules/cjs/loader:1192:37) 

    at TracingChannel.traceSync (node:diagnostics_channel:322:14) 

    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 

    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) 

    at node:internal/main/run_main_module:36:49 { 

  code: 'MODULE_NOT_FOUND', 

  requireStack: [] 

} 

 

Node.js v22.19.0 

PS 

C:\Users\USER

> sfdx 

node:internal/modules/cjs/loader:1386 

  throw err; 

  ^ 

 

    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)      

    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) 

    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)         

    at Function._load (node:internal/modules/cjs/loader:1192:37) 

    at TracingChannel.traceSync (node:diagnostics_channel:322:14) 

    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 

    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) 

    at node:internal/main/run_main_module:36:49 { 

  code: 'MODULE_NOT_FOUND', 

  requireStack: [] 

} 

 

Node.js v22.19.0 

PS 

C:\Users\USER

> sf 

The Salesforce CLI 

 

VERSION 

  @salesforce/cli/2.109.6 win32-x64 node-v22.19.0 

 

USAGE 

  $ sf [COMMAND] 

 

TOPICS 

  agent            Commands to work with agents. 

  alias            Use the alias commands to manage your aliases. 

  analytics        Work with analytics assets. 

  apex             Use the apex commands to create Apex classes, execute         

                   anonymous blocks, view your logs, run Apex tests, and view    

                   Apex test results. 

  api              Commands to interact with API calls. 

  cmdt             Generate a field for a custom metadata type based on the      

                   provided field type. 

  code-analyzer    Output the current state of configuration for Code Analyzer.  

  community        Create an Experience Cloud site using a template. 

  config           Commands to configure Salesforce CLI. 

  data             Manage records in your org. 

  dev              Audit messages in a plugin's messages directory to locate     

                   unused messages and missing messages that have references in  

                   source code. 

  flow             Display test results for a specific asynchronous test run.    

  force            Legacy commands for backward compatibility. 

  info             Access Salesforce CLI information from the command line.      

  lightning        Work with Lightning Web and Aura components. 

  logic            Use the logic commands to run Apex and Flow tests and view    

                   the test results. 

  org              Commands to create and manage orgs and scratch org users.     

  package          Commands to develop and install unlocked packages and managed                   2GP packages. 

  package1         Commands to develop first-generation managed and unmanaged    

                   packages. 

  plugins          list installed plugins 

  project          Work with projects, such as deploy and retrieve metadata.     

  schema           Generate metadata files. 

  sobject          Commands to interact with Salesforce objects. 

  static-resource  Work with static resources. 

  update           update the sf CLI 

  version 

 

COMMANDS 

  autocomplete  Display autocomplete installation instructions. 

  commands      List all sf commands. 

  doctor        Gather CLI configuration data and run diagnostic tests to        

                discover and report potential problems in your environment.      

  help          Display help for sf. 

  plugins       List installed plugins. 

  search        Search for a command. 

  update        update the sf CLI 

  version 

  whatsnew      Display Salesforce CLI release notes on the command line.        

  which         Show which plugin a command is in. 

 

PS 

C:\Users\USER

> sfdx 

node:internal/modules/cjs/loader:1386 

  throw err; 

  ^ 

 

Error: Cannot find module '

C:\Users\USER\undefined' 

    at Function._resolveFilename (node:internal/modules/cjs/loader:1383:15)      

    at defaultResolveImpl (node:internal/modules/cjs/loader:1025:19) 

    at resolveForCJSWithHooks (node:internal/modules/cjs/loader:1030:22)         

    at Function._load (node:internal/modules/cjs/loader:1192:37) 

    at TracingChannel.traceSync (node:diagnostics_channel:322:14) 

    at wrapModuleLoad (node:internal/modules/cjs/loader:237:24) 

    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:171:5) 

    at node:internal/main/run_main_module:36:49 { 

  code: 'MODULE_NOT_FOUND', 

  requireStack: [] 

} 

 

Node.js v22.19.0                                           

 

After install the salsforce cli I got this error on vs code terminal     

 

 

 

#Trailhead Challenges

3 answers
  1. Manish Kumar Yadav (Hitachi Energy) Forum Ambassador
    Oct 29, 2025, 6:00 PM

    Above error is valid because you are running sfdx which is depricated, 

     

    You should run only sf beacuse Salesforce has deprecated the old sfdx CLI in favor of sf.

    sf --version

    Thanks, 

    Manish Kumar Yadav 

    Trailblazer Community Forum Ambassadors 

     

     

0/9000

In Sales Cloud Account List Views, there are fields that i cannot find as "Fields" or "Custom Fields" in the Account object.  

 

They are the following :

Native List View Fields

 

I would like to see how they were created or if they can be modified. I would like to implement : 

 

Last 60 Days Activities 

Last 90 Days Activities  

 

etc... 

 

I understand creating a "Cutom" formula field would suffice but i want to make sure i do not create another Field if i can modify the existing functionality. TIA! 

 

#Trailhead Challenges  #Trailhead  #Salesforce Admin  #Salesforce Developer

1 answer
  1. Feb 23, 6:08 PM

    Hello @Jorge Diaz Fields like Last Activity or Last Activity Date are what Salesforce calls Derived or Summary Fields. They don't technically live on the Account object as a standard data column. Instead, they are dynamically calculated based on the Task and Event objects. If you are using Einstein Activity Capture (EAC), fields like Last Activity

    behave differently. These fields are "Virtual." You can see them in List Views and Reports, but you cannot find them in the Object Manager because they aren't standard fields. 

     

    As a best approach instead of creating a field that "looks back" 60 days, create one field that calculates the

    age of the last activity. You can then use this single field to power all your list view filters and logic.

    1. Go to: Object Manager > Account > Fields & Relationships > New.
    2. Type: Formula (Return Type: Number).
    3. Field Label: Days Since Last Activity
    4. Formula: TODAY() - LastActivityDate
    5. How to use it: In your List View Filters, simply set: Days Since Last Activity less than or equal to 60. This gives you the flexibility to change the "60" or "90" on the fly without creating new fields for every time window.

    Hope this clarify your doubt. Feel free to mark this as helpful for others :)

0/9000

Hi everyone — I’m a Revenue Operations Manager looking to deepen my Salesforce expertise from a RevOps perspective (pipeline management, forecasting, reporting, automation, data quality, etc.). 

 

Can anyone recommend the most useful trails or curated trailmixes that focus on real-world RevOps workflows rather than pure admin or developer content? 

 

Ideally looking for content that helps with:

  • Sales pipeline & forecasting
  • Reporting and dashboards
  • Campaigns & attribution
  • Data management / governance
  • Automation (Flows, processes)
  • Cross-functional visibility across Sales, Marketing, and CS

If there are any must-do learning paths you’ve found especially valuable in a RevOps role, I’d really appreciate the recommendations.

Thanks in advance! 

 

#Trailhead Challenges  #Trailhead

0/9000
3 answers
0/9000