Skip to main content

I was able to use this for a standard object(ContentVersion) and it worked fine. For the POST request it showed a lot of fields without the create() property so I had to clean it up. 

 

When I ran it for a custom object though it came back empty. I double checked that the user that was authorized has access to it.

3 Antworten
  1. 13. Jan. 2025, 23:38

    As far as I can tell, you aren't using the API properly.   There's no ability to specify which objects you want detail on as you are implying with your resources.   Instead use one of the resources specified here: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/openapi_beta.htm      For example: 

    { "resources" : ["*"]}

    or  one or more of these literal strings:

    NOTE: {blobField}, {id}, and {sObject} must be entered literally. They aren’t variables as you might expect working with an OpenAPI spec:

    { "resources" : [

    "/sobjects/{sObject}",

    "/sobjects/{sObject}/{id}",

    "/sobjects/{sObject}/deleted",

    "/sobjects/{sObject}/describe",

    "/sobjects/{sObject}/{id}/{blobField}"

    ]

    }

0/9000