Examples:

Get the describe for an object without ever running an expensive Schema.globalDescribe() call

// using object api name string param:
Schema.DescribeSObjectResult accountDescribe = FieldUtils.getDynamicDescribe('Account');

// using SObject record param:
Schema.DescribeSObjectResult accountDescribe = FieldUtils.getDynamicDescribe(accountRecord);

Get the field map for an object without ever running an expensive Schema.globalDescribe() call

// using object api name string param:
Map<String, Schema.SObjectField> accountFieldMap = FieldUtils.getFieldMap('Account'); 

// using SObject record param:
Map<String, Schema.SObjectField> accountFieldMap = FieldUtils.getFieldMap(accountRecord); 

Get the properties for a particular field set:

List<Schema.FieldSetMember> accountFieldSet = FieldUtils.readFieldSet( 'My_Field_Set',  'Account');

Get just the api names of the fields belonging to a particular field set:

List<Schema.FieldSetMember> acctFieldSetApiNames = FieldUtils.getFieldSetFieldAPINames( 'My_Field_Set',  'Account');

Determine if SObjectField is createable using object and field string params:

Boolean isCreateable = FieldUtils.isFieldCreateable('Account', 'Industry');

Determine if SObjectField is accessible using object and field string params:

Boolean isAccessible = FieldUtils.isFieldAccessible('Account', 'Industry');

Determine if SObjectField is updateable using object and field string params:

Boolean isUpdateable = FieldUtils.isFieldUpdateable('Account', 'Industry');

Get the field type for an SObject field using object and field string params:

String industryFieldType = FieldUtils.getFieldType('Account', 'Industry'); //PICKLIST

Get a list of all field api names for a given object:

List<String> acctFields = FieldUtils.getAllFieldsForSobj('Account');

Get a list of all createable fields for a given object:

List<String> acctCreateableFields = FieldUtils.getCreateableFields('Account');

Get a list of all accessible fields for a given object:

List<String> acctAccessibleFields = FieldUtils.getAccessibleFields('Account');

Get a list of all updateable fields for a given object:

List<String> acctUpdateableFields = FieldUtils.getUpdateableFields('Account');

Get a list of all fields (except within a specified blacklist) for a given object:

List<String> acctFieldsExceptBlacklist = FieldUtils.getAllFieldsExceptBlacklist('Account', new List<String>{'PersonPronouns', 'PersonGenderIdentity'});

Parse last object from field path:

// sample data:
Contact contact = [SELECT Id, Name, Account.Owner.Name FROM Contact LIMIT 1];

// dynamically get the last object within a multi-level path (in this case, User/Owner):
SObject deepestRecordFromPath = ApexUtils.parseLastSubObjectFromPath(contact, 'Account.Owner.Name'); // get the user record

Parse value from field path:

// sample data:
Contact contact = [SELECT Id, Name, Account.Owner.Name FROM Contact LIMIT 1];

// dynamically get the field value as an Object for a multi-level path:
Object fieldValueObj = ApexUtils.parseValueFromFieldPath(contact, 'Account.Owner.Name'); // get the value stored in the Name field

Source

Credits: Kevin Antonioli

Source: https://live.playg.app/play/field-utils

The below examples are for the standard “Account” object. However, this will work for any other standard or custom object – don’t forget to add __c for the custom objects.

Get All Parent objects.

for(Schema.SobjectField strFld: Account.SobjectType.getDescribe().fields.getMap().Values())
{
    if(strFld.getDescribe().getType() == Schema.DisplayType.REFERENCE)
    {
        system.debug('==parent object='+strFld.getDescribe().getReferenceTo());
    } 
}

Get All Child objects.

Schema.DescribeSObjectResult R = Account.SObjectType.getDescribe();
for (Schema.ChildRelationship cr: R.getChildRelationships()) 
{
  system.debug('====child object==='+cr.getChildSObject());
}

Getting Relationship Names

Schema.DescribeSObjectResult R = Account.SObjectType.getDescribe();
for (Schema.ChildRelationship cr: R.getChildRelationships()) 
{
  system.debug('====child object relation Name==='+cr.getRelationshipName());
}

Source: https://salesforce.stackexchange.com/questions/117050/get-all-parent-and-child-objects-related-to-the-current-object
Credit: https://salesforce.stackexchange.com/users/18731/ratan-paul

The “Apex heap size too large” error occurs when too much data is being stored in memory during processing. The limit depends on the type of execution (E.g., synchronous vs asynchronous calls) and current value. 

Best practices for running within the Apex heap size,

• Don’t use class level variables to store a large amount of data.
• Utilize SOQL For Loops to iterate and process data from large queries.
• Construct methods and loops that allow variables to go out of scope as soon as they are no longer needed.

Ref: https://help.salesforce.com/articleView?id=Apex-Heap-Size-Best-Practices&language=en_US&type=1

In order to resolve Heap size error issue, you need to revamp the code following the above best practices so that you don’t hit these limits.

Please refer to the following link which discusses different strategies to manage the heap size.

• http://blog.jeffdouglas.com/2010/08/16/managing-the-heap-in-salesforce-com/
• https://success.salesforce.com/questionDetail?qid=a1X30000000ddWJEAY

Troubleshooting approach to fix heap size error,

1) Add the following debug method to the affected class:

void checkHeapSize(String tag) {
system.debug(tag + ': Heap size is ' + limits.getHeapSize() + ' enforced is ' + limits.getLimitHeapSize());
}

2a) Call the method at various points in the code using a “tag” parameter so that you know where it’s called in the code. For example: checkHeapSize(‘constructor1’);

2b) In order to check the heap limit, put the check in the loop and then run the check every 1000th iteration. This is done by adding a local variable called “i” (i.e. “integer i;”), increment it for each iteration, and then running the following code:

if (math.mod(i, 1000) == 0) } { call the method }.

3) Review the debug logs to find the heap size to see if it’s exceeding the limit. For issues with scheduled batches, testing in the Developer Console will run code synchronously and show the limit as 6 MB but the heap size limit for scheduled batches is the asynchronous limit of 12MB.

4) If heap size doesn’t exceed the limit, repeat steps 1-3. If the limit is exceeded, the debug logs should point out the problematic section of code that will need to be fixed.

Source: https://developer.salesforce.com/forums/?id=9062I000000DHPCQA4
Credit: Sweta (Her profile is not available anymore – 404 error)

List<SObject> toSave = new List<SObject>();
for(integer i = 0; i < 100; i++ )
{
    BB_A__c bba = new BB_A__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 5)
    {
        bba.x__c = 'bartek';
    }
    toSave.add(bba);
     
    BB_B__c bbb = new BB_B__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 7)
    {
        bba.y__c = 'bartek';
    }
    toSave.add(bbb);    
}
insert toSave;

You receive the following error:
Execution Failed. System.TypeException: Cannot have more than 10 chunks in a single operation. Please rearrange the data to reduce chunking.

but after execution of this script:

List<SObject> toSave = new List<SObject>();
for(integer i = 0; i < 100; i++ )
{
    BB_A__c bba = new BB_A__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 5)
    {
        bba.x__c = 'bartek';
    }
    toSave.add(bba);
}
 
for(integer i = 0; i < 100; i++ )
{   
    BB_B__c bbb = new BB_B__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 7)
    {
        bbb.y__c = 'bartek';
    }
    toSave.add(bbb);
     
}
insert toSave;

everything goes smoothly. This is because when you insert a list with multiple objects, the data type cannot change more than 10 times. Do not ask why, this is SALESFORCE.
But there is a simple solution:
You have to sort the list that you want to add. Because the standard List.sort() method sorts collection by SObject labels then you will have all objects grouped by SObject label that equals to sobject type:). Here is a working example:

List<SObject> toSave = new List<SObject>();
for(integer i = 0; i < 100; i++ )
{
    BB_A__c bba = new BB_A__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 5)
    {
        bba.x__c = 'bartek';
    }
    toSave.add(bba);
     
    BB_B__c bbb = new BB_B__c(
        x__c = 'testx',
        y__c = 'testy'
    );
    if(i == 7)
    {
        bba.y__c = 'bartek';
    }
    toSave.add(bbb);
     
}
 
toSave.sort(); // <-- this line fixes our issue:):):)
 
insert toSave;

Conclusion

Here is the method I found one of the answers from the Salesforce developers community by Julien Castelluci

Source:
https://bartoszborowiec.wordpress.com/2014/06/15/execution-failed-system-typeexception-cannot-have-more-than-10-chunks-in-a-single-operation-please-rearrange-the-data-to-reduce-chunking/

At some point, we had an idea of collecting leads by sending out the investor materials, such as company marketing presentations for an exchange to their contact information.

This task required us to perform the following actions:

1. Create the Lead object if he does not exist yet
2. Query all the specified attachments and send them via email to the Lead to make sure that the email is correct
3. Save sent email as the Lead activity for the sales team
4. Subscribe Lead to the MailChimp list if he checked the GDPR field
5. Remember Lead’s browser so that he could download attachments without filling the form in future to improve the user experience

Of course, this is quite a lot of things to do to make the life of marketers and sales team easier and automate the process. But I would like to focus on the second step and show how you could send out the email with dynamic attachments from the Apex class.

TL;DR;

Please, find the final version of the code at the end of the post.

Single Email Message

Let’s pretend that we have an Apex controller for downloading attachments. It could be the REST API endpoint or just the regular class for the sake of simplicity.

global class DownloadAttachments {
 /**
  * @param {String} startupId The Id of the target startup object, which files we should attach to the email
  * @param {String} emailAddress The email address of the recipient
  */
  global static void download(String startupId, String emailAddress) {
    ...
  }
}

In this case, to send the email, we will use the Messaging.SingleEmailMessage class.

It has the method called setFileAttachments which we will use attach the files we want to send along.

This method accepts the list of Messaging.EmailFileAttachment objects.

Finally, each of this attachment objects should have the name, body, and content type to correctly display it in the email.

To begin with, let’s create the new instance of the SingleEmailMessage class and set the recipient address.

Messaging.SingleEmailMessage message = new Messaging.SingleEmailMessage();

message.setToAddresses(new String[] { emailAddress });

Then, the exciting part begins. Salesforce allows us to do a lot of things with the messaging class.

Email File Attachments

Before jumping into the mailer class, let’s query all the required information from the object’s attachments.

Note: We can use inner joins in queries to get the list of attachments straight away, but Salesforce does not allow us to retrieve Body file data inside them.

Therefore, we need to perform two queries. First of all, we will get the list of attachment Ids and then retrieve the rest separately.

List<Startup__c> startups = [SELECT Id, (SELECT Id FROM Attachments) FROM Startup__c WHERE Id = :startupId];
if (!startups.isEmpty()) {
  Set<Id> attachmentIds = (new Map<Id, SObject>(startups[0])).keySet();
  List<Attachment> files = [SELECT Name, Body, ContentType FROM Attachment WHERE Id IN :attachmentIds];
}

As the result of the code above, we would get the list of the files with all the information we need to proceed further.

Now, we need to generate the list of the actual email attachments out of the files that we have and attach them to the email.

List<Messaging.EmailFileAttachment> attachments = new List<Messaging.EmailFileAttachment>();
for (Attachment file: files) {
  Messaging.EmailFileAttachment efa = new Messaging.EmailFileAttachment();
  efa.setFileName(file.Name);
  efa.setBody(file.Body);
  efa.setContentType(file.ContentType);
  attachments.add(efa);
}
message.setFileAttachments(attachments);

You can configure whenever you want to attach files as links or actual data in Setup > Email > Email Attachments.

Here we have the attachment list ready. Next, we can continue with the single email message.

Email Templates

We can compose the email content both in the plain text and HTML right in the Apex class.

However, that is not the best practice.

We want to keep it clear and dynamic. We do not have to edit and deploy our code on every text change. Plus, we might want to customize the email so that it will follow the company branding style guides.

Here come email templates for rescue.

In Salesforce, you can build own email templates which are very versatile. To do so, go to the Setup > Email > Classic Email Templates and click New Template. Choose Custom (without using Letterhead), select folder, check the Available For Use box, give it a name and subject.

Then provide the HTML and plain text content.

In conclusion, we have the email template ready to use. We can query it by the DeveloperName and then set its Id, Subject, and HtmlValue to our message.

For instance, you might query templates dynamically based on the Lead language to send out personalized emails.

EmailTemplate template = [SELECT Id, Subject, HtmlValue FROM EmailTemplate WHERE DeveloperName = 'InvestorMaterial'];
message.setTemplateId(template.Id);
message.setSubject(template.Subject);
message.setHtmlBody(template.HtmlValue);

As a result, the code above will apply the custom template to the email we are planning to send.

Organization-Wide Email Addresses

Besides the custom templates, Salesforce provides the functionality to set the sender email address as well via the organization-wide email address settings.

Otherwise, the email will have the System Administrator user’s address by default.

In addition to templates, organization-wide address settings give us the opportunity to customize the message further.

Go to Setup > Email > Organization-Wide Addresses and click New.

Enter the display name, email address, and choose which Profiles could use this address.

Next, we can query this address and set is as the sender.

List<OrgWideEmailAddress> addresses = [SELECT Id FROM OrgWideEmailAddress WHERE Address = 'info@digitalflask.com'];
if (!addresses.isEmpty()) {
  message.setOrgWideEmailAddressId(addresses[0].Id);
}

If you know the Lead or Contact Id, you can record the email out as the object’s activity like

message. setTargetObjectId(lead.Id);
message.setSaveAsActivity(true);

Send Email

After all, the only part left is actually to try to send the message.

try {
  Messaging.sendEmail(new Messaging.SingleEmailMessage[] { message });
} catch (Exception e) {
  throw e;
}

If you execute the method via the REST API, Throw will return the 500 Http server error response with the detailed description so that we could handle it on the client side.

In summary, I hope that I helped you learn more about the Salesforce email settings and how to you could use the Messaging class to extend and customize the standard functionality to send out dynamically generated and personalized emails.

In conclusion, here is the complete sample of the messaging method.

Credits: Nikita Verkhoshintcev
Source: https://digitalflask.com/blog/send-email-attachments-salesforce-apex/

Typically, you know it already, but you need it when you’re writing your apex dynamically.

Here is a simple method which accept API Names in STRING and returns the labels. You can modify as per your need:

Happy Coding!

As of now, you can GET custom metadata records in flows but you cannot create or update them.

Using this invocable class you can create/update custom metadata records in Flows.

You can access the repository here:

https://github.com/mhamzas/Flow-Create-Update-Custom-Metadata

The code is self explanatory but I have tried my best to do better commenting for others to understand what’s going on here.

/**
 * @description       : This invocable class will allow you to update/create customMetadata using Flow/Process Builder.
 * @author            : M Hamza Siddiqui @ mhamzas.com
 * @group             : Cloudjunction Advisors, Inc.
 * @last modified on  : 01-21-2021
 * @last modified by  : M Hamza Siddiqui @ mhamzas.com
 * Modifications Log 
 * -----------------
 * Ver   Date         Author                             		Modification
 * 1.0   01-22-2021   M Hamza Siddiqui @ mhamzas.com		   Initial Version
**/
global class UpdateCMD implements Metadata.DeployCallback {

    /*An invocable variable used as input or output variables in the process builder*/
    global class ActionRequest {
        @InvocableVariable(required = true)
        public List<sObject> data;
    }
    //This invocable method is used for processing the business by taking the input from process builder/flow
    @InvocableMethod(label = 'Create/Update Custom Metadata')
        global static void invokeService(List <ActionRequest> requests) {
          for (ActionRequest requestObj: requests) {
              //Accessing the values from process builder/flow when record is inserted
              for(sObject obj : requestObj.data){
                  //System.debug('requestObj.sObject@@:' + obj);
                  //System.debug('requestObj.ObjectType@@:' + obj.getSObjectType());
                  // Getting all the Populated fields in a Map
                  Map<String, Object> fieldsToValue = obj.getPopulatedFieldsAsMap();
                  Map<String, Object> metadataFieldValueMap = new Map<String, Object>();
                  String MetadataDevName; // To Store Custom Metadata Record API/Developer name
                  String MetadataLabel; // To Store Custom Metadata Label name
                  // Looping on all the populated fields
                  for (String fieldName : fieldsToValue.keySet()){
                      System.debug('field name is ' + fieldName + ', value is ' + fieldsToValue.get(fieldName));
                      // We don't want to add system fields to the Map for update, so here is some simple logic
                      if(fieldName == 'Label'){
                          MetadataLabel = (String)fieldsToValue.get(fieldName);
                      } else if(fieldName == 'DeveloperName'){
                          MetadataDevName = (String)fieldsToValue.get(fieldName);
                      } else if(fieldName != 'Id' && fieldName != 'Language' && fieldName != 'MasterLabel' && fieldName != 'NamespacePrefix' && fieldName != 'QualifiedApiName') {
                          // Populating Map for Processing later
                          metadataFieldValueMap.put(fieldName, fieldsToValue.get(fieldName));
                      }
                  }
                  
                  System.debug('Label is ' + MetadataLabel + '& DeveloperName is ' + MetadataDevName);
                  // Making sure to have either Label or Developer Name for the CMD record to process
                  if(String.isBlank(MetadataDevName) && String.isBlank(MetadataLabel)){
                      throw createCustomException('Make sure to add "Label" attribute in assignemnt for Create and "DeveloperName" for update.');
                  } else { 
                      //if MetadataDevName available, which means the record exists already - Processing UPDATE
                      if(!String.isBlank(MetadataDevName)){
                          UpdateCMD.updateCustomMetadata(String.valueof(obj.getSObjectType()),MetadataDevName, MetadataLabel,metadataFieldValueMap);
                      } else { // Creating a new Custom Metadata record
                          //if ID not available - CREATE
                          UpdateCMD.createCustomMetadata(String.valueof(obj.getSObjectType()), MetadataLabel, metadataFieldValueMap);
                      }
                  }
                  // END
              }
          }
    }
    
    /* Custom Metadata Deploy Methods */
    /* ============================================================*/
    //Inteface method 
    public void handleResult(Metadata.DeployResult result, Metadata.DeployCallbackContext context) {
        if (result.status == Metadata.DeployStatus.Succeeded) {
            //Success
            System.debug('Success Result-' + result);
        } else {
            //Failed
            System.debug('Failed Result-' + result);
            throw createCustomException(String.valueof(result));
        }
    }
     
    //Create Custom Metadata record
    public static void createCustomMetadata(String metdataName, String label, Map<String, Object> metadataFieldValueMap){
        String recordDevName = label.replaceAll(' ', '_');
        Metadata.CustomMetadata cMetadata = new Metadata.CustomMetadata();
        cMetadata.fullName = metdataName + '.' + recordDevName;
        cMetadata.label = label;
         
        for(String key : metadataFieldValueMap.keySet()){
            Metadata.CustomMetadataValue cMetadataValue = new Metadata.CustomMetadataValue();
            cMetadataValue.Field = key;
            cMetadataValue.Value = metadataFieldValueMap.get(key); 
            cMetadata.values.add(cMetadataValue);
        }
         
        Metadata.DeployContainer mdContainer = new Metadata.DeployContainer();
        mdContainer.addMetadata(cMetadata);
        UpdateCMD callback = new UpdateCMD();
        Id jobId = Metadata.Operations.enqueueDeployment(mdContainer, callback);
    }
     
    //Update Custom Metadata record
    public static void updateCustomMetadata(String metdataName, String recordDevName, String label, Map<String, Object> metadataFieldValueMap){
        Metadata.CustomMetadata cMetadata = new Metadata.CustomMetadata();
        cMetadata.fullName = metdataName + '.' + recordDevName;
        cMetadata.label = label;
         
        for(String key : metadataFieldValueMap.keySet()){
            Metadata.CustomMetadataValue cMetadataValue = new Metadata.CustomMetadataValue();
            cMetadataValue.Field = key;
            cMetadataValue.Value = metadataFieldValueMap.get(key); 
            cMetadata.values.add(cMetadataValue);
        }
         
        Metadata.DeployContainer mdContainer = new Metadata.DeployContainer();
        mdContainer.addMetadata(cMetadata);
        UpdateCMD callback = new UpdateCMD();
        Id jobId = Metadata.Operations.enqueueDeployment(mdContainer, callback);
    }

    /* Flow Exception Handling */
    /* ============================================================*/
    public class CustomException extends Exception {}
    
    static CustomException createCustomException(String message) {
        CustomException ex = new CustomException(message);
        ex.setMessage(message);
        return ex;
    }
}

Happy Coding!

Developers can build a filter or sort action that works with any collection of records, from accounts and contacts to custom objects. Previously, developers couldn’t use polymorphic Apex structures in invocable actions because generic data types weren’t supported.

Create a custom action, or edit an existing one. Use the sObject or List<sObject> data type in invocable methods and attributes.

Previously, the example class would have been tied to the Account or Contact or myCustomObject__c object. But now developers create one action, and the Flow Builder admin chooses the object each time they use that action.

Source

• https://releasenotes.docs.salesforce.com/en-us/spring20/release-notes/rn_forcecom_flow_fbuilder_dynamic_types.htm?edition=&impact=

Here we’ll discuss how you can insert records in multiple objects in a single dml call.

Let’s assume you need to add records in Account, Contact and AccountContact (Custom Object). By using the below code, you add records in all 3 objects in a single DML call.

Source : https://salesforce.stackexchange.com/questions/141897/insert-multiple-sobjects-in-single-dml-call