Skip to main content

Hi All!  

 

I'm on the "Control Access to Fields" unit (

Force.com

Admin Intermediate trail, Data Security module), specifically the "Set Field Permissions for Multiple Permission Sets" step, which asks me to set field-level security on the Candidate object's Job Category field. That field doesn't exist anywhere in my org (confirmed via a global Setup search), and neither do several others the unit references — Apex, C#, Hire By, Hiring Manager, and the sensitive ID field mentioned in the unit text. 

 

My Candidate object does exist, with fields like Current Employer, Currently Employed, Education, Years of Experience, Legacy Candidate Number, etc. — a completely different set from what the unit describes. 

 

For context: earlier in this trail I ran into a separate issue where the Position/Candidate/Job Application/Review objects didn't exist at all, which I resolved by installing a package referenced in an earlier community thread. That got the base objects working, but it looks like this package doesn't include the custom fields (Job Category, Apex, C#, etc.) that this later unit assumes exist — I suspect those are meant to come from manually completing "Create Custom Recruiting Fields" in the "Build a Data Model for a Recruiting App" project. 

 

Has anyone else run into this specific mismatch? Is completing that earlier project the right fix, or is there a different/updated package I should be using instead? Any guidance appreciated.

Thanks! 

 

#Trailhead Challenges  #Salesforce Admin

1 respuesta
  1. 7 sept, 13:06

    Hi @Carolina Scarpa

    If you've already installed a package but still don't see fields such as Job Category, Apex, C#, Hire By, and Hiring Manager, it's possible your org contains a mix of manually created components and packaged components, causing the mismatch. 

     

     Several users have reported success by installing the package in a fresh Playground and completing the exercises there rather than trying to reconcile an existing setup.

    Since the package includes its own Candidate, Position, and related metadata, creating a new Playground org and completing the setup from scratch may be the quickest path forward. 

    Ref: 

    https://trailhead.salesforce.com/trailblazer-community/feed/0D5KX00000KBv8S0AT

0/9000