Salesforce Solutions: September 2019

Saturday, September 7, 2019

How To Store Count of Child Records in Parent Record

If the Parent & Child object is related with Master-Detail Relationship, we can easily get

the count of Child records and store it in the Parent object by using Roll-up Summary

field. But if the relation is Lookup between the Parent & Child, we don't have any other

option except writing Trigger. So for example I am taking Account & Contact object as these

are related with Lookup. So we need to Count all the Contact records and store it into

the respective Parent Account record.

Question: In Which Object should I write the Trigger?

Answer: Ofcourse the answer would be Contact object as when we are performing any

DML Operation on Contact record, the count of contact records will be affected and by

implementing a Trigger on Contact object, we can easily capture the Count and update it

to the respective Parent Account record.

So the answer is we have to implement the Trigger obviously in Child Object.

Please find the Trigger code below:

    trigger totalContactsTrigger on Contact (After Insert,After Update,

    After Delete,After Undelete) {        

    Set<Id> setAccIds = new Set<Id>();

    //Using Trigger.new to get the Account Id for Insert & undelete Operation

    if(Trigger.isInsert || Trigger.isUndelete){    

        for(Contact con : Trigger.new){

            setAccIds.add(con.AccountId);

        }

    }    

    //Using Trigger.new & Trigger.old to get older & newer version of Account Id

    if(Trigger.isUpdate){

        for(Contact con : Trigger.new){ 

            //Condition to check if the Account lookup field is updated or not

            if(con.AccountId!=Trigger.oldMap.get(con.Id).AccountId){

                setAccIds.add(con.AccountId);

                setAccIds.add(Trigger.oldMap.get(con.Id).AccountId);

            }        

        }

    }

    //Using Trigger.old to get the Account Id for Delete Operation  

    if(Trigger.isDelete){ 

        for(Contact con : Trigger.old) {  

            setAccIds.add(con.AccountId);

        }

    }    

    List<Account> accList=new List<Account>();  

    for(Account acc :[Select id,Total_Contacts__c ,(Select id from contacts) from 

    Account where Id in : setAccIds]){

        acc.Total_Contacts__c = acc.contacts.size();

        accList.add(acc);

    }

    if(!accList.isEmpty()){ 

        update accList;

    }        

   }

Monday, September 2, 2019

SOQL To Fetch All Tasks Related to Account & Opportunity

When we write query to get details from Parent object also from a child object SOQL, we

know that the particular child record is surely associated with a specific Parent Object. For

Example we know there is a relationship between Account(Parent) &

Opportunity(Child) Object. So that means every Opportunity is related with an

Account object for sure.

But in case of Task Or Event object, As these objects are related with multiple objects like

Account,Contract,Campaign,Opportunity,Product,Asset,Case,Solution,Quote

and Any Custom Objects we can't guarantee that a Task/Event record is related with

which of the previously mentioned objects. So for Task/Event object, the parent object

relationship is not static. This type of relationship is known as Polymorphic

Relationship.

Requirement : SOQL to fetch all Tasks Related to Account & Contact

Solution: As we know Task records can be created with multiple objects including

Account & Contact, we need to take help of WhatId field used in Task object. Using Type

qualifier on WhatId, we can achieve the same. The Type qualifier determines the Parent

object Type which is associated with any Task Or Event record.

Sunday, September 1, 2019

Different Type Of Sandboxes in Salesforce

Developer Sandbox: Developer sandbox is a copy of production, it copies all application

and configuration information to the sandbox. This type of sandboxes are limited to

200mb of test and sample data, which is enough for many development and testing tasks.

You can refresh type of sandboxes once per day.

Developer Pro Sandbox: Developer Pro sandboxes copy all of your production

organizations's reports, dashboards, pricebooks, products, apps and customizations under

setup but exclude all of your organization's standard and custom object records,documents

and attachments. This type of sandboxes are limited to 1gb of test and sample data. We can

refresh this type of sandbox once per day.

Partial Data Sandbox: A Partial Data Sandbox is a developer sandbox plus the data you

define in a Sandbox Template. It includes the reports, dashboards, pricebooks, products,

apps and customizations(including all of your metadata). Additionally as defined by your

sandbox template, Partial Data Sandboxes can include your organizations' standard and

custom object records, documents and attachments upto 5gb of data and a maximum of

10000 records per selected objects. A Partial sandbox is smaller than a full sandbox and a

shorter refreshment interval of 5 Days.

Sandbox Templates allow you to pick specific objects and data to copy to your sandbox,

so that you can control the size and content of each sandbox. Sandbox templates are

available only in Partial Data and Full sandboxes.

Full Sandbox: Full copy sandbox are exact copy of Production including standard and

custom object records, attachments and documents. You can refresh full copy sandbox after

29 days.

Type	Refresh Interval	Storage Limit	What’s Copied	Sandbox Templates
Developer	1 Day	Data Storage: 200mb File Storage : 200mb	Metadata Only	Not Available
Developer Sandbox	1 Day	Data Storage: 1gb File Storage : 1gb	Metadata Only	Not Available
Partial Data Sandbox	5 Days	Data Storage: 5gb File Storage : 5gb	Metadata and Sample Data	Required
Full Sandbox	29 Days	Same as Production Org	Metadata and All Data	Available

Salesforce Solutions

Navigational Menu

Sunday, September 8, 2019

Service Cloud Sample Questions Part 2