Feed

Apex Permission is given.  

still facing same error.

I also face similar issue. I created AWS connection and also created DLO, DMO, Search Index successfully. But There is no chunks available when i query over DLO. I have one pdf file uploaded in AWS S3.

Hello @Prince Kothari

this is a common concern when dealing with complex orgs in Salesforce. Here's a breakdown of the implications and best practices around having 

200+ Record Types on a single object:

Drawbacks of Having More Than 200 Record Types

1. Performance Impact
   • UI loading can be slower, especially for profiles with access to many record types.
   • Metadata retrieval (e.g., deploying via Metadata API or using tools like VS Code/SFDX) can become slower and harder to manage.
2. Profile Management Complexity
   • Assigning record type visibility across multiple profiles becomes messy and error-prone.
   • Each profile has to be updated individually for record type access and default layout assignment.
3. Maintenance Nightmare
   • Admins and developers may struggle with managing mappings between 200+ record types and 160+ page layouts.
   • Deployment diffs become huge and harder to track.
   • Harder to test, document, or audit.
4. UI Limitation for Picklists
   • Picklist values per record type can get hard to manage. It's easy to make mistakes when controlling picklist availability per record type.
5. Developer Tooling Limitations
   • Some Salesforce tools (like SFDX, change sets) and IDEs may hit size or timeout issues when retrieving a huge number of metadata components.
6. User Confusion
   • End users might face difficulty selecting the correct record type if they’re exposed to too many options.

Recommendations / Alternatives

• Revisit the Need for Record Types  
  Are all 200+
  really needed? Could some be consolidated using dynamic forms, conditional layouts, or automation?
• Leverage Dynamic Forms and Lightning Pages  
  Instead of creating a new layout for every case, use visibility rules on fields/components.

• Use Custom Metadata or Custom Settings  
  Store business rules in metadata and conditionally render content based on those rather than splitting into many record types.

• Segment the Object  
  If feasible, consider breaking the object into multiple custom objects grouped by major categories.

Best Practice Summary

Since you're at 184 already, it’s definitely time to pause and reconsider architecture decisions before adding more.

We achieved this long long back using a dashboard called "Main Menu". Then each link widget was associated with one dashboard and then a text widget beside it described what the dashboard is meant for. If you do need a "See All" button, you can re-link this "Main Menu" dashboard to all the dashboards. But, as Roman said, users do have to click on the link widgets to open the dashboards.

Hello @Kaan Kartal Kuyucu

The issue could stem from a few things:

• Permission Set Not Created: The "Access and Manage Reviews" permission set might not exist or wasn’t created correctly in your Playground. The challenge expects you to have built it earlier in the module (e.g., with Read, Create, Edit permissions for the Review object).
• Playground Sync Issue: Even with a new Playground, if the environment hasn’t fully refreshed or the module’s dataset didn’t load properly, some objects or permission sets might be missing.
• Search/Filter Glitch: The "Add Permission Set" interface might not be picking up the permission set due to a filter or naming mismatch.

 Here are some solutions for this-

Verify the Permission Set: 

• Go to Setup > Permission Sets and look for "Access and Manage Reviews." If it’s not there, you need to create it: 
  • Click New, enter Label: "Access and Manage Reviews," keep License as "None," and save.
  • Click Object Settings > Reviews, then Edit, and check Read, Create, Edit permissions. Save.
• If it’s there but not showing, ensure its API name matches (e.g., "Access_and_Manage_Reviews").

Check the Recruiters Permission Set Group: 

• Navigate to Setup > Permission Set Groups, find "Recruiters," and click Manage Assignments > Add Permission Set.
• If "Access and Manage Reviews" still doesn’t appear, use the search bar within the popup and type the exact name. Sometimes the UI needs a nudge.

Try a Fresh Playground: 

• Since a new Playground didn’t help, ensure you’re launching it from the challenge page (Launch Trailhead Playground button). Old or cached Playgrounds can cause issues. Create another one, but this time, start the module from scratch and follow each step to build the permission set before adding it to the group.

Common Workaround: 

• Some users have reported success by logging out of Trailhead, clearing browser cache, and logging back in with a new Playground. Try this with Chrome or Firefox, as Edge has had validation quirks.

Hello @Puval Mahato

The issue is that you're trying to find the

1. Check if Custom Objects Exist

Make sure that Positions and Reviews are actual custom objects in your org.

• Go to Setup > Object Manager
• Search for Position and Review
  • If not found, they may not be created yet.

 If they do exist, continue with step 2.

 2. Check the Permission Set’s Scope

Ensure that the permission set you're editing is meant to grant access to those objects.

• In your screenshot, the permission set is called “Manage Positions”.
• It's possible that it was created without linking custom objects.

To fix this:

1. Click on "Object Settings" inside the Permission Set.
2. Scroll or search manually (Control + F) for Position or Review.
3. If still missing, you can:
   • Go to the custom object > Set Permissions via Profiles or create a new Permission Set that includes them.

 3. Manually Add Object Permissions

If you confirm the custom objects exist:

1. Go to the Permission Set.
2. Under Object Settings, click "Add" (you may need to assign permissions via Profile instead if not visible here).
3. Or create a new permission set and include custom object access explicitly.

Thank you for the response @Tushar Jadav, but I have given the right name as "Reservations" itself and still I get this error.

Hi @Anas Benbrik

, no I've not found the solution to this yet! I'm going to raise it with support.  

Apologies I missed this message