New answers tagged

0

Your request to update the ApexTriggerMember of this MetadataContainer succeeds, but that doesn't actually perform a deployment - it stages it in the container. The ApexTrigger Tooling API object itself does not support CRUD operations in an active org. From the Tooling API documentation, Use a MetadataContainer as a package for your tool’s workspace. As ...


1

If you want to use APIs (to keep this very simple) you can: Create a folder using ContentFolder You can then create a Document and give it the Folder ID However if you are trying to do this programmatically - I assume you mean via Apex? In which case you can create these via Apex (there are a couple of ways to do this, here is an example of using Connect ...


6

Making a call to the {your sandbox domain}/services/data REST API will return a JSON response with all the available API versions. Here is the JSON response: [..., { "label" : "Winter '19", "url" : "/services/data/v44.0", "version" : "44.0" }, { "label" : "Spring '19", "url" : "/services/data/v45.0", "version" : "45.0" }, { "label" : "Summer '...


2

I'm not aware of such an API, or any other way of extending standard metadata like this. I think you might be forced into: Storing the values you require as some Custom Metadata Type, with a 'Key' field that holds the Object and Field API names for querying. Storing the values in some global utility class, with each JSON string being a value in a Map of <...


Top 50 recent answers are included