Meera R Nair - Salesforce Insights

 Salesforce Orgs -  which are existing for more than 5 years, it is very common that some functionalities become obsolete after a certain period of time. Let us see why and how we need to remove these retired functionalities and related components.  Why we need to Remove retired functionalities   1. Better Salesforce Governor Limits Like you know, Salesforce is having many limits with respect to the number of fields, the number of objects, code storage, validation rules, formula fields, etc. per Org. When we remove/delete unwanted components from an Org, it gives us additional space for new functionalities 2. Improve Performance  There might be associated back end logic which is still getting executed on a record save, even if that feature is not in use. It will consume execution time, SOQL/DML limits of your current transaction. So removing this logic will help with better transaction performance 3. Avoid Unexpected Exceptions Obsolete backend functio...

When your Salesforce instance is growing with lots of customization, there are high chances that you might hit performance issues with respect to Record save time. Salesforce is providing with out of the box approaches to track and find out time consumed by each of your operation. Let us see how we can track that - with the help of a sample scenario - Contact record save operation. Scenario - Customization On Contact Object Let us consider 2 Customization on Contact Object. 1. Assign Task to Account Owner - Process Builder When a new Contact is created, assign a task to Account Owner asking to reach out to that Contact to get some additional details about him. This can be achieved through a Process Builder as shown below: 2. Update Account Country from Contact to Country field in Account - Contact Trigger Example : Account - Account ABC Contact 1 -> Country ->India Contact 2-> Country->United States Once the contacts are saved, Account Country value should be ->...