SOSL (Salesforce Object Search Language) is a search language in Salesforce, we can search in multiple objects at same time using SOSL. In SOQL, we can query only one object at a time but in SOSL, We can search for some specified string in multiple objects at the same time.
SOSL query begins with the required FIND clause.
The search string should be at least two characters long.
SOSL is used if we don’t know in which object the data is present.
We can mention in which fields of all the sObjects,we want to search for the string specified. Suppose you have to performed search on two objects Account & Contact. Then you can mention like, for list returned with Account results only (Name, Industry) fields should be returned, and for Contacts results (firstName, lastName) should be returned.
We can retrieve multiple objects and field values efficiently when the objects may or may not be related to each other.
We can query only on fields whose data type is text, phone and Email.
The result of SOSL is a list of lists of sObjects.
The returned result contains the list of sObjects in the same order as order mentioned in SOSL query.
If a SOSL query does not return any records for a specified sObject type, then search results include an empty List for that sObject.
We can use SOSL in classes but not in Triggers.
We cannot perform DML operation on search result of SOSL.
Here in below example, there is a input text box and a command button which will search for the entered string in two Objects Accounts and Contacts and returned result will be shown in the page block tables.
We can have a requirement to show master object record and the respective child records in a Visualforce Page. So, for that we don’t have to write code to retrieve child object record. We can show the child records without query it.
Here is an example I’m rendering a Visualforce Page as “pdf” with Account information and the respective contact records information.
Standard List controllers allow you to create Visualforce pages that can display or act on a set of records. We can access Standard List controller with the help of recordSetVar which is the attribute of apex:page component.
Note: When you use the standardController attribute on the tag, you can’t use the controller attribute at the same time.
Standard List Controller Actions:
Action
Description
apex:commandButton
This tag is used to create a button
apex:commandLink
This tag is used to create a link.
apex:actionSupport
This tag is used to make an event such as onclick and onmouseover.
apex:actionPoller
It periodically calls an action.
apex:actionFunction
It defines a new JavaScript function.
apex:page
Calls an action when the page is loaded.
Standard List Controller Actions Methods:
Method
Decription
save
Inserts new records or updates existing records that have been changed. After this operation is finished, the save action returns the user to the original page, if known, or the home page.
quicksave
Inserts new records or updates existing records that have been changed. Unlike the save action, quicksave does not redirect the user to another page.
list
Returns a PageReference object of the standard list page, based on the most recently used list filter for that object when the filterId is not specified by the user.
cancel
Aborts an edit operation. After this operation is finished, the cancel action returns the user to the page where the user originally invoked the edit.
first
Displays the first page of records in the set.
last
Displays the last page of records in the set.
next
Displays the next page of records in the set.
previous
Displays the previous page of records in the set.
Here in below example, Visualforce Page is using the standard Controller “Contact”, and recordSetVar is set to “accounts”.
public class SampleController
{
//Wrapper class variable
public Wrapper obj {get;set;}
//Constructor
public SampleController(){
obj = new Wrapper();
obj.name = 'Biswajeet';
}
//Wrapper class
public class Wrapper
{
public String name {get;set;}
}
}
