#Salesforce Admin322 discutindo

Hey Regine, 

To retrieve files (ContentVersion, ContentDocument, Attachment) via API, here's the actual path: 

1. Set up a Connected App (Setup > App Manager > New Connected App), enable OAuth Settings, note the Consumer Key/Secret, this is what your external tool authenticates with. 

2. Authenticate using OAuth 2.0 (Web Server Flow for a server-side app, or Username-Password Flow for quick testing, though that's being phased out). This gives you an access token and instance URL. 

3. Query file metadata via REST API: 

- For files uploaded through Lightning (Files feature): query ContentVersion (has the actual file body in VersionData) and ContentDocumentLink (to find which records a file is attached to) 

- For older Attachments (Classic-style, still exist on many orgs): query the Attachment object directly, it has a Body field with the binary content 

4. To actually download the binary content, hit the REST API endpoint: 

`GET /services/data/vXX.0/sobjects/ContentVersion/{Id}/VersionData` (for Files) 

`GET /services/data/vXX.0/sobjects/Attachment/{Id}/Body` (for classic Attachments) 

with your Bearer access token in the header. 

If you're just testing/exploring rather than building an integration, Workbench (

) lets you browse and download files directly through a UI without writing code, useful for a quick one-off pull. 

Reference:

Hey Samir, 

Yes, that's correct, permission sets only list objects that already exist in your org. If it's a custom object the challenge expects you to work with, you need to create the object (and its fields) first, then go back to the permission set, it'll appear in Object Settings once it exists. 

If the object should already exist (a standard object, or a custom object from an earlier step in the same module), and it's still not showing up, double check: 

- You're in the correct Playground/org this challenge is checking against 

- If it's custom, confirm the exact API name matches what the instructions specify, small naming mismatches are a common cause of confusion here too 

Standard objects (Account, Contact, etc.) should always be available by default, if one of those is missing from the list, that'd be unusual and worth double-checking you're not filtering/searching incorrectly in the object picker.

Hey Vishal, 

This matches a documented Salesforce Known Issue: Internal Server Error in Experience Builder when creating/accessing page variations. It's a recognized platform bug tied to how the builder handles new page creation for certain page types, not something wrong with your API name or setup. 

Workaround from Salesforce's own known issue documentation: 

1. Open Experience Builder, open the Pages menu 

2. Locate the affected page, click the three dots next to it, go to Page Properties 

3. From there, try creating the page fresh as a page variation with a basic/blank layout rather than through the standard "New Page" flow 

If this workaround doesn't resolve it for you, per the same known issue, the recommended next step is opening a case with Salesforce Support directly, referencing this as matching the known "Internal Server Error in Experience Builder when accessing page variations" issue and providing your specific Error ID (628191604-286554) so they can trace it against the root cause already on file. 

Reference:

Can you post screenshots?  like this? 

1 

2 

3