Learn Salesforce Certification with Free Lessons & Tips

Hello Subash,

My name is Devika. I have total of 4.5 Yrs of Experience as Salesforce Consultant. I have worked on Several Projects. Its good if you want to start your career in Salesforce. Its very high in Demand now a days. 

Currently I am working as Freelancer as Salesforce Trainer and Training 5 Candidates Online. If you are interested you can revert me with your email ID on this.

Thanks

Imagine you have two users. Both are in the same profile, which allows them to Create, Edit object XYZ. But these two users are in different parts of the role hierarchy.

If User A Creates an XYZ, can user B edit it? The answer is only if the record is shared with him. If the Org Wide Default is Private then he will not even be able to see the record that User A has created (unless it is explicitly shared with him). He can still create his own XYZ records and edit those. Likewise, if the Org Wide Default is public read only, User B could see it, but not edit it despite what his profile allows. He can edit only his own records or those shared with him.

Sharing also works up the role hierarchy. So User A's boss can see the XYZ record that User A created. If his profile allows, he can edit it, but his profile may not.

You can think of the profile as "What can a user do with the XYZ object" and the sharing as "Which particular XYZ records can he or she do it with"

If OWD is Public Read / Write but the profile does not have access to Read or to Edit then you cannot Read or Edit.

If OWD is Public Read / Write on object XYZ and profile has Read permission but not Edit, then the user with that profile can only Read XYZ (all of them).

If a user doesn't even have Read access to object XYZ then they cannot see any object XYZ regardless of the Org Wide Default.

Not correct : The owner who is higher on the role hierarchy has shared access to all the XYZ that his subordinates own. However, if the higher user has a profile which doesn't include read or edit then he cannot read or edit those records.

• By default all the variables and methods are non-static.

• Scope of the non-static variables or methods is within the scope of the same object.

• We can declare variables and methods as static by using static keyword.

• Scope of the static variables and methods is throughout the transaction.

• Static variables and methods, we can directly call with class name (we cannot access static variables and methods with object name).

//Map holds key and value pair.

//Syntax: Map mapName = new Map();

/*Map countryISTCodeMap = new Map();

countryISTCodeMap.put('India','91');

countryISTCodeMap.put('USA','001');

countryISTCodeMap.put('India','911');//replaces old value with new value.*/

Map countryISTCodeMap = new Map{'India'=>'91','USA'=>'001', 'India'=>'911'};

system.debug('countryISTCodeMap result: '+countryISTCodeMap+' with size '+countryISTCodeMap.size());

system.debug('countryISTCodeMap keys: '+countryISTCodeMap.keyset());

system.debug('countryISTCodeMap values: '+countryISTCodeMap.values());

system.debug('countryISTCodeMap search: '+countryISTCodeMap.containsKey('India'));

system.debug('countryISTCodeMap fetching value based on key: '+countryISTCodeMap.get('India'));

//map keys are case-sensitive.

keyset(): To fetch only keys from the map.

values(): To fetch only values from the map.

containsKey(value): To search a key from the map.

get(key): By supplying the key we can fetch the value.

put(key,value): To add key and value in a map.

1. SOQL: Salesforce Object Query Language

• SOQL: Salesforce Object Query Language

• SOQL Purpose: To fetch info. from an object and related objects.
• We can write query on one object while querying on those objects we can fetch the child object info. or parent object info. (we cannot capture un related objects info.)
• SOQL queries per transaction: 100.
• SOQL query rows returned: 50000.

2. SOSL: Salesforce Object Search Language

• SOSL: Salesforce Object Search Language.
• SOSL Purpose:We can search for a value in multiple objects (no need of any relationship).
• Results of SOSL query can be stored in List of List.
• SOSL queries per transaction: 20.
• SOSL query rows returned: 2000.

insert/update

Database.insert/Database.update

Assume that you are inserting 100 records. If any one of the record fail due to error then entire operation will fail. None of the records will be saved into the database. with insert/update if we use try-catch then we can capture only one error which will cause to stop the operation.

Assume that you are inserting 100 records. If any one of the record fail due to error then it will perform partial operation (valid records will be inserted/updated) if we use Database.insert(list,false)/ Database.update(list,false).

.with Database.insert/Database.update we can capture all the errors by saving result in Database.saveResult[].

 ChildObject__c

ParentObject__c

Click to see the full question.

Relationship between ChildObject__c and ParentObject__c objects is Lookup relationship.

In case of lookup relationship if we delete the parent object record in child object only the relationship field value will be removed (child records won't be deleted).

But client has a requirement to delete the child object records. How to achieve this?

Write an apex trigger to achieve this functionality.

We should take before delete event. If we take after delete relationship will broke up b/w parent and child object records.

Trigger ParentTrigger on ParentObject__c(before delete) {

   /*

Note:

• For delete events only trigger.old and triggger.oldMap will be available.

• trigger.old holds old versions of the records but if we mention that in SOQL query salesforce will automatically convert those records into ids.

   */

   List childLst = [select id, Parent_Object__c from ChildObject__c where Parent_Object__c in: trigger.old];  

   delete childLst;

  }

1. We can call the apex code by creating object for the class (or) if the variables or methods are static then we can call with class name.

• Apex Code in the trigger will execute automatically for the DML operations.

• If you want to execute apex code on a specific time then we should write batch class.

• With Batch Apex we can process maximum of 50 million records.

• Batch Apex is asynchronous (execute in future context).

• While writing the batch class we should inherit Database.Batchable interface.

• Database is a built in global class which contains inner global interface.

2. What are the Batch Apex methods?

Since we are inheriting Database.Batchable interface we should implement all the method prototypes declared in the interface.

 We should implement the following global methods:

• Start: It will prepare the records to process and execute only one time.

• Execute: It will take the records prepared in start method and split those records into batches and it will execute multiple times. For example if the start method is returning 1000 records then execute method executes 5 times if you don't mention the batch size (Default Batch Size is: 200). Maximum batch size is: 2000.

• Finish: We can perform post commit logic like sending emails with the success or error information. It will execute only one time.

Batch Class Syntax:

//Database is Class provided by Salesforce.

//Batchable is an global interface which is inside of the Database class.

 //Batchable include 3 method prototypes: 1. Start 2. Execute 3. Finish

 //start and finish methods will execute only one time.

 //execute method executes multiple times.

 global class BatchUsage implements Database.Batchable , Database.Stateful {

  //at a time we can inherit multiple interfaces but we cannot inherit multiple classes.

  //By default batch class is stateless (variable info. store in one method cannot be remembered in other method),

  //to make it stateful we should inherit Database.Stateful interface.

  String name = '';

  global Database.queryLocator start(Database.BatchableContext bc) {

  //From asynchronous to asynchronous we cannot call

  //(from batch class we cannot call future mehthod vice versa.).

  name += 'start';

  system.debug('@@@Start Method: '+name);

   //Collects the records to process. It will forward these records to execute method.

   //If we use Iterable as return type for this start method it can hold

   //max. of 50k records only.

   //If we use Database.queryLocator as return type for this start method it can hold

   //max. of 50 million records.

   return Database.getQueryLocator('select id, name, Location__c from Department__c where Location__c = \'\'');

  }

  global void execute(Database.BatchableContext bc, LIST sObjLst) {

   name += 'execute';

   system.debug('@@@Execute Method: '+name);

  //Split the records forwarded by start method into batches.

  //Default batch size is: 200.

  //Max. batch size is: 2000.

  List depUPdLst = new List();

  for(SObject sObj: sObjLst) {

  Department__c dept = (Department__c) sObj;//Type Casting.

  dept.Location__c = 'Bangalore';

  depUPdLst.add(dept);

   }

   if(depUPdLst.size() > 0)

    update depUPdLst;

  }

  global void finish(Database.BatchableContext bc) {

   name += 'finish';

   system.debug('@@@Finish Method: '+name);

   //Post Commit logic like sending emails for the success or failures of the batches.

   AsyncApexJob a = [select id, Status, NumberOfErrors, JobItemsProcessed,

   TotalJobItems, CreatedBy.Email from AsyncApexJob where id =: bc.getJobId()];

   Messaging.singleEmailMessage mail = new Messaging.singleEmailMessage();

   mail.setToAddresses(new String[]{a.CreatedBy.Email});

   mail.setSubject('Batch Class Result');

   mail.setHtmlBody('The batch Apex job processed ' + '' + a.TotalJobItems + '' +

   ' batches with '+ '' + a.NumberOfErrors + '' + ' failures.');

   //sendEmail methods

   Messaging.sendEmail(new Messaging.singleEmailMessage[]{mail});

   /*** Scheduling in minutes or hours ***/

   /*//Create object for schedulable class

   SchedulableUsage su = new SchedulableUsage();

   //Preparing chron_exp

   Datetime sysTime = System.now();

   sysTime = sysTime.addminutes(6);

   String chron_exp = '' + sysTime.second() + ' ' + sysTime.minute() + ' ' +

   sysTime.hour() + ' ' + sysTime.day() + ' ' + sysTime.month() + ' ? ' + sysTime.year();           

   System.schedule('Dep Update'+sysTime.getTime(),chron_exp, su);*/

  }

 }

To schedule the batch class in minutes/hours, in the finish method we should use System.schedule method which will take 3 parameters Job Name, Chrone Expression and schedulable class instance name respectively.

   /*** Scheduling in minutes or hours ***/

 //Create object for schedulable class

 SchedulableUsage su = new SchedulableUsage();

 //Preparing chron_exp

 Datetime sysTime = System.now();

 sysTime = sysTime.addminutes(6);

 String chron_exp = '' + sysTime.second() + ' ' + sysTime.minute() + ' ' +

 sysTime.hour() + ' ' + sysTime.day() + ' ' + sysTime.month() + ' ? ' + sysTime.year();           

 System.schedule('Dep Update'+sysTime.getTime(),chron_exp, su);