Search Results

While there is overlap, the Tooling API is specifically designed to help developers build IDE apps for salesforce, while the metadata API is more general purpose configuration migration. For example, …

The UI uses the sorted property to override the input order and alphabetize the values according to their label. This is a UI-only feature. If you want to do this in code, you'll have to sort the valu …

It appears that you're looking for the getRecordCreateDefaults method. This requires no Apex and returns the layout assigned to the user, optionally based on the record type, if specified. From there, …

Apex Code exposes PermissionSet, SetupEntityAccess, FieldPermissions, and ObjectPermissions, so you can directly query these objects as if they were normal sObject entities. In other words, you don't …

The GACK ID values are derived heuristically, and are only meant for grouping crashes with the same root cause together, in order to define the frequency of the crash. It is up to a human to read the …

Just create a new package version that contains no elements (or perhaps some dummy element), and use the upgrade type "DeprecateOnly" when upgrading. All of your metadata will be in a Deprecated statu …

You can build a JSON helper class, then call the endpoint and deserialize. Here's a quick example I wrote up that will copy-paste execute in Execute Anonymous. You'll have to put the classes and metho …

Technically, there's nothing stopping you from calling the tooling API or metadata API directly from Apex. However, code changes always require running all tests in production, so you would find that …

The available types are listed in several places, CustomField being one. I'm not sure if there's a way to actually "describe" these values dynamically; the Tooling API only describes the field as a "c …

Edit: We can now query the ApexTypeImplementator table to find all public and global classes that implement a given interface locally, as well as global classes in managed packages that implement a sp …

You can use the following format to get any record without using an ID: /services/data/vXX.X/*/sobjects/**EntityName**/**ExternalIdField**/**ExternalIdValue** For example, you can use: /services/data …

That's as simple as: for(RootObjectMetadata.MetadataRecords records: parsedResponse.records) { records.id = null; } You don't need anything more complicated than that.

You can use \r and \t to format your code. You can also make your code easier to read with some proper JSON encoding: public class ApexClassWrapper { public String Name; public String Body; } Ape …

You just need to make the property reactive: @wire(getDynamicTableDataList, {TableName: '$objRecId'}) Now that your wire handler will be called at least twice, once with no data, and once with the pr …

The Tooling API doesn't support standard record objects. It's meant to be a way to access metadata objects, such as ApexClass and CustomField, particularly in a way that you'd use it for "tooling" (me …