In order to make use of Custom Metadata types in your Apex classes, you must extend the EventService class. Specifically, you cannot override the getInstance method. The reason for this is that SOQL queries are slow. This is one of the main reasons why you should consider using the getInstance method instead. It uses the sObject directly without having to rely on SOQL, which is faster and avoids contributing to the Query Rows limit.
For faster access, use the getAll() or getInstance(qualifiedApiName) Apex methods. These two methods return sObject details directly, and they don’t rely on the SOQL engine. You can use the label and developer name fields to identify the custom metadata for a given instance. You must assign the appropriate permission set to the user. This way, the Apex class can read the metadata and return it.
In order to use the getInstance method to retrieve custom metadata, you need to have the API key. You should assign the user who needs to use the API keys with the appropriate permissions. To do this, you need to have the required permission set. In order to access the Custom Metadata Loader API, you must be logged in as the owner of the application. This will allow you to write and modify the meta data on your account.
The getInstance() method is used to access the custom metadata for an instance. It is not possible to access a custom metadata unless you have the relevant permissions. In order to write the meta data in an Apex code, you must assign the proper privilege to the user. This permission set will allow you to write and read metadata in your database. In addition, the getInstance() method will return the custom metadata in an SQL query.
In the Apex code, you can use the getinstance() method to access the custom metadata of an object. These methods have the same permissions as their SOQL counterparts, so they should be faster than the getInstance() method. For more information, see the documentation provided by your development team. The ‘getInstance’ function will help you retrieve the metadata of the object.
The getInstance() method has two advantages. The first is that it can return the custom metadata of an object. It also supports the creation of API keys. It is faster than using the getinstance() and setall() methods. In contrast, the ‘getInstance’ method should return a sObject. These methods are more efficient than the SOQL counterpart. If you need a custom metadata, you should define it before calling the other methods.
In apex code, you can use the getinstance() and ‘getall()’ methods to retrieve the custom metadata. The latter two methods are faster because they don’t depend on the SOQL engine. Moreover, they are faster than the SOQL counterpart and don’t need a lot of configuration. The best way to get this metadata is to call it from a C# application.
In Spring ’21, Oracle introduced two new custom metadata types and updated the associated methods and SOQL queries. The getinstance() method is now the fastest way to return the custom metadata. In addition, this method can return the sObject’s label and developer name. Hence, the developer name and Label fields of the object are used to identify it. These methods have the same names as the SOQL equivalents, but they don’t require a SOQL engine.
In Spring ’21, the Apex getInstance() and ‘getAll’ methods can be used to retrieve the custom metadata from a Web service. However, the getAll() method is more efficient, and it doesn’t need the SOQL engine. The ‘getinstance’ method is also more flexible and can return the sObject details directly from the sObject.