Explore topic-wise InterviewSolutions in .

Master-Detail relationship is the Parent-child relationship. In which Master represents Parent and detail represents Child. If Parent is deleted then Child also GETS deleted. Roll-up summary fields can only be created on Master records which will calculate the SUM, AVG, MIN of the Child records.

• Up to 2 ALLOWED to object.
• Parent FIELD on child is required.
• Access to parent determines access to children.
• Deleting parent AUTOMATICALLY deletes child.
• A child of one master detail relationship cannot be the parent of another.
• Lookup field on page layout is required.

Master-Detail relationship is the Parent-child relationship. In which Master represents Parent and detail represents Child. If Parent is deleted then Child also gets deleted. Roll-up summary fields can only be created on Master records which will calculate the SUM, AVG, MIN of the Child records.

LOOKUP and Master-detail relationships are ONE too many relationships. We can create many – to – Many relationships by using a junction OBJECT. Junction object is a CUSTOM object with two master-detail relationships.

Lookup and Master-detail relationships are one too many relationships. We can create many – to – Many relationships by using a junction object. Junction object is a custom object with two master-detail relationships.

• No, directly we cannot create master-details relationship if a custom object CONTAINS existing records.
• Following are the steps to create to create a master-detail relationship when records are available in a custom object.
• First create FIELD with lookup relationship.
• And then ASSOCIATE LOOK field with parent record for every record next change the DATA type of the field from look up to Master detail.

Tab is a user interface component to user creates to display CUSTOM object data.

There are three type of TABS:

• Custom Tabs
• Visual FORCE Tabs
• WEB Tabs

Tab is a user interface component to user creates to display custom object data.

There are three type of tabs:

Action function: 

Invoke the controller method from JAVA script using AJAX and we can USE action function from different places on visual force page.

Action support:

Invoke the controller method using AJAX when even occurs on page like onMouseOver, onClick, ect… and we can use action support for particular SINGLE apex COMPONENT.

Action function: 

Invoke the controller method from java script using AJAX and we can use action function from different places on visual force page.

Action support:

Invoke the controller method using AJAX when even occurs on page like onMouseOver, onClick, ect… and we can use action support for particular single apex component.

• VISUAL FORCE PAGE
• WEB Service
• TRIGGERS
• Email services

If USER have only Read ACCESS on PARTICULAR record but he wants to change the owner name of that record, then in profile level TRANSFER Record enables he can ABLE to change the owner.

If user have only Read access on particular record but he wants to change the owner name of that record, then in profile level Transfer Record enables he can able to change the owner.

Yes possible. Controlling field should be CHECK box or pick LIST.

Yes possible. Controlling field should be Check box or pick list.

RECORD Types are RESTRICT the PICK list VALUES and assign to the different page layouts for different Record Types.

Record Types are restrict the pick list values and assign to the different page layouts for different Record Types.

There are 4 TYPES of REPORTS in Salesforce:

• Tabular Reports
• SUMMARY Reports
• Matrix Reports
• Joined Reports

There are 4 types of reports in Salesforce:

We are having TWO TYPES of RELATIONSHIPS, they are:

• LOOKUP RELATIONSHIP
• Master-Detail Relationship

We are having two types of relationships, they are:

• Objects are database TABLES that allow you to store data specific to your organization in salesforce. You can use CUSTOM objects to extend salesforce.com functionality or to build new application functionality.
• When you create a custom object, we can create a custom tab, customized related lists, reports, and dashboards for USERS to interact with the object data. You can ALSO access custom object data through the Force.com API.
• NAVIGATION to create an object in sales force: Setup-->Build-->Create-->Object--> Click on new object and create object according to your requirement.

• An app is a group of tabs that work as a unit to provide FUNCTIONALITY. Users can switch between apps using the Force.com app drop-down menu at the top-right corner of every page.
• You can customize existing apps to match the way you work or build new apps by grouping standard and CUSTOM tabs.
• NAVIGATION to create an app in Salesforce: Setup ->Build ->Create->App-> Click on new and create your application according to your requirements.

While you can instantiate a class based on its name using the Type SYSTEM class, you can’t dynamically locate a method and EXECUTE it. The best that you can do is to dynamically CREATE an instance of a class that IMPLEMENTS an interface and EXECUTES one of the methods on the interface.

While you can instantiate a class based on its name using the Type system class, you can’t dynamically locate a method and execute it. The best that you can do is to dynamically create an instance of a class that implements an interface and executes one of the methods on the interface.

A Batch class allows you to define a single job that can be broken up into manageable chunks that will be processed separately.

One example is if you need to make a field update to every Account in your organization. If you have 10,001 Account records in your org, this is impossible without some way of breaking it up. So in the start() method, you define the query you’re going to use in this batch context: ‘select Id from Account’. Then the execute() method runs, but only receives a relatively SHORT list of records (default 200). Within the execute(), everything runs in its own transactional context, which means almost all of the governor limits only apply to that block. Thus each time execute() is run, you are allowed 150 QUERIES and 50,000 DML rows and so on. When that execute() is COMPLETE, a new one is instantiated with the next group of 200 Accounts, with a brand new set of governor limits. Finally the finish() method wraps up any loose ends as necessary, like sending a status email.

So your batch that runs against 10,000 Accounts will actually be run in 50 separate execute() transactions, each of which only has to deal with 200 Accounts. Governor limits still apply, but only to each transaction, along with a separate set of limits for the batch as a whole.

Disadvantages of batch processing:

• It runs asynchronously, which can make it hard to troubleshoot without some coded debugging, logging, and persistent STATEFUL reporting. It also means that it’s queued to run, which may cause delays in starting.
• There’s a limit of 5 batches in PLAY at any time, which makes it tricky to start batches from triggers unless you are checking limits.
• If you need access within execute() to some large part of the full dataset being iterated, this is not available. Each execution only has access to whatever is passed to it, although you can persist class variables by implementing Database.stateful.
• There is still a (fairly large) limit on total Heap size for the entire batch run, which means that some very complex logic may run over, and need to be broken into separate batches.

A Batch class allows you to define a single job that can be broken up into manageable chunks that will be processed separately.

One example is if you need to make a field update to every Account in your organization. If you have 10,001 Account records in your org, this is impossible without some way of breaking it up. So in the start() method, you define the query you’re going to use in this batch context: ‘select Id from Account’. Then the execute() method runs, but only receives a relatively short list of records (default 200). Within the execute(), everything runs in its own transactional context, which means almost all of the governor limits only apply to that block. Thus each time execute() is run, you are allowed 150 queries and 50,000 DML rows and so on. When that execute() is complete, a new one is instantiated with the next group of 200 Accounts, with a brand new set of governor limits. Finally the finish() method wraps up any loose ends as necessary, like sending a status email.

So your batch that runs against 10,000 Accounts will actually be run in 50 separate execute() transactions, each of which only has to deal with 200 Accounts. Governor limits still apply, but only to each transaction, along with a separate set of limits for the batch as a whole.

Disadvantages of batch processing:

There are a couple of decent Dreamforce presentations here:

Team Development:

Possible, Probable, and Painless and Continuous Integration in the Cloud.

We ran into some issues with this in practice and there was no way to get TRUE automation (i.e., set it and forget it). We were also set it up with Selenium.

Here were the issues that I remember:

• Some features aren’t supported in the metadata API and cannot be moved via the ant migration. If you have any unit tests that work with those features, you have to manually work on your CI ORG.
• Deletions are harder to maintain. You have to manually update and apply a destructiveChanges.xml file or replicate the deletion in the CI org.
• We ran into a situation where some metadata XML files had ‘invalid’ data in them. The suggested solution was to build a post checkout script that manipulates the offending XMLs into valid XMLs. Not ideal.
• On PROJECTS, we wanted to track just our changes and push out just our changes in source control. In THEORY, this would allow much easier rebase lining. This would have required more manual maintenance of XML files (e.g., 2 NEW fields added on Account and only want to push those 2 fields not all (*) fields).
• My conclusion is that it is worth doing if you can get it set up, but if you are working on shorter-term projects and don’t have a decent amount of time budgeted in for it, it probably isn’t worth setting up.

There are a couple of decent Dreamforce presentations here:

Team Development:

Possible, Probable, and Painless and Continuous Integration in the Cloud.

We ran into some issues with this in practice and there was no way to get true automation (i.e., set it and forget it). We were also set it up with Selenium.

Here were the issues that I remember:

Apex-lang is about as close to a Java-style library as you can get. Contains several string, database, and collection utilities that mimmick Java functionality. Be aware though, some stuff including Comparing and Sorting collections is out of date with the ADVENT of the Comparable interface in Apex.In addition to apex-lang, and like you suggest, I typically create or reuse static helper methods throughout my projects. Static helper methods are very CONVENIENT for reusing CODE in Chatter functionality, DML handling, EXCEPTION handling, Unit TESTING, etc.

Apex-lang is about as close to a Java-style library as you can get. Contains several string, database, and collection utilities that mimmick Java functionality. Be aware though, some stuff including Comparing and Sorting collections is out of date with the advent of the Comparable interface in Apex.In addition to apex-lang, and like you suggest, I typically create or reuse static helper methods throughout my projects. Static helper methods are very convenient for reusing code in Chatter functionality, DML handling, Exception handling, Unit testing, etc.

• You can create sObjects in memory with arbitrary CreatedDate values by using JSON.deserialize. This doesn’t enforce the normal read-only field attributes that prevent you from setting a createdDate value. However, you can’t commit arbitrary CreatedDate values to the database (or else it would be a serious security issue).
• Detecting GOVERNOR limits through apex
• First of all, the EXCEPTION thrown by HITTING a limit, System.LimitException is uncatchable and means that your script will be killed, EVEN if it happens inside a try/catch block. There is a class, Limits, that contains a number of static methods that allow you to CHECK your governor limit consumption.

Role Hierarchy:

• If we ADD a user to a role, the user is above in the role hierarchy will have read access.
• Setup --> MANAGE USERS --> roles --> setup roles --> click on ‘add role’ --> provide name and save.

OWD:

• DEFINES the BASE line setting for the organization.
• Defines the level of access to the user can see the other user’s record
• OWD can be Private, Public Read Only, Public Read and Write.
• Setup -> Security Controls -> sharing settings -> Click on ‘Edit’

Manual Sharing:

• Manual Sharing is sharing a single record to single user or group of users.
• We can see this button detail page of the record and this is visible only when OWD setting is private.

Criteria Based Sharing rules:

• If we want to share records based on condition like share records to a group of users
• Whose criteria are country is India.
• Setup -> security controls -> sharing settings -> select the object and provide name and Conditions and save

Apex sharing:

Share object is available for every object(For Account object share object is AccountShare ). If we want to share the records using apex we have to create a record to the share object.

Role Hierarchy:

OWD:

Manual Sharing:

Criteria Based Sharing rules:

Apex sharing:

Share object is available for every object(For Account object share object is AccountShare ). If we want to share the records using apex we have to create a record to the share object.

If we want to give ACCESS to other USERS we USE sharing RULES.

If we want to give access to other users we use sharing rules.

A SETTING that DEFINES when time-dependent WORKFLOW ACTIONS should FIRE.

A setting that defines when time-dependent workflow actions should fire.

We can customize DIFFERENT things on PAGE layout like, Fields, BUTTONS, Custom LINKS and Related Lists. We can ALSO create sections.

We can customize different things on page layout like, Fields, Buttons, Custom Links and Related Lists. We can also create sections.

YES,user can upload their custom LOGO in documents and then they choose that logo for ORGANIZATION.

Yes,user can upload their custom logo in documents and then they choose that logo for organization.

Trigger:

• Trigger is a piece of code that executes before or after a record is inserted or updated.
• We can access the trigger across the object and RELATED to that objects.
• We can use 20 DML operations in one trigger.
• We can use 20 SOQL from data base in one trigger.

Workflow:

• Workflow is automated process that fired an action based on EVALUATION criteria and rule criteria.
• We can access a workflow across the object.
• We cannot perform DML OPERATION on workflow.
• We cannot query from DATABASE.

Trigger:

Workflow:

YES. Just LIKE S-Controls. VISUALFORCE PAGES support embedded merge fields.

Yes. Just like S-Controls. Visualforce pages support embedded merge fields.

• Use the future annotation to specify that these methods that are EXECUTED asynchronously.
• Methods with future annotation must be STATIC methods
• Methods with future annotation can only RETURN a void type.

Syntax: 

global CLASS class_name

{

@future

Static void methodname(parameters)

{

//body of the METHOD

}

Syntax: 

global class class_name

{

@future

Static void methodname(parameters)

{

//body of the method

}

We can use DATABASE.executebatch ( ) method to PROGRAMMATICALLY begin the BATCH job.

Syntax:

Public static ID execute batch ( sObject class name)

Public static ID execute batch (sObject class name, INTEGES SCOPE) 

The above two methods are static methods of database class. We can use any one of the method to execute the batch job.

We can use database.executebatch ( ) method to programmatically begin the batch job.

Syntax:

Public static ID execute batch ( sObject class name)

Public static ID execute batch (sObject class name, integes scope) 

The above two methods are static methods of database class. We can use any one of the method to execute the batch job.

The TRANSIENT KEYWORD prevents the data from being saved in to view STATE. This should be used for very temporary variables.

The transient keyword prevents the data from being saved in to view state. This should be used for very temporary variables.

 STANDARD CONTROLLER, select option, pagereference, messages,ETC.

 Standard controller, select option, pagereference, messages,etc.

A WEB directory where hundreds of appexchange APPS are available to salesforce customers to review, demo, comment upon, and /or install. Developers can submit their apps for LISTING on the appexchange directory if they WANT to SHARE them with the community.

A web directory where hundreds of appexchange apps are available to salesforce customers to review, demo, comment upon, and /or install. Developers can submit their apps for listing on the appexchange directory if they want to share them with the community.

Public websites and applications that are directly integrated with your SALESFORCE organization without REQUIRING users to LOG in with a USERNAME and PASSWORD.

Public websites and applications that are directly integrated with your salesforce organization without requiring users to log in with a username and password.

An APP DEVELOPMENT MODEL that allows apps to be defined as declarative "blueprints”, with no code required. Data Models, objects, forms, WORKFLOWS, and more are defined by METADATA.

An app development model that allows apps to be defined as declarative "blueprints”, with no code required. Data Models, objects, forms, workflows, and more are defined by Metadata.

An application MODEL in which all users and apps SHARE a SINGLE, COMMON infrastructure and code base.

An application model in which all users and apps share a single, Common infrastructure and code base.

Page BLOCK:

For DEFAULT salesforce standard format.

DATA table:

To design CUSTOM FORMATS.

Page Block:

For default salesforce standard format.

Data table:

To design custom formats.

To use javascript remoting in a vf page , add the REQUEST as a java SCRIPT INVOCATION with the following from.

[namespace.] CONTROLLER.method ( 

[PARAMETERS….,]

Call back Function,

[configuration]

);

• Name space is the namespace of the controller class
• Controllers is the name of your apex controller.
• Method is the name of your apex controller method you are calling.
• Parameters is the comma-separated list of parameters that your method takes.
• Callback function is the name of the javascript function that will handle the response from the controller.
• Configuration configures the handling of remote call and response.

To use javascript remoting in a vf page , add the request as a java script invocation with the following from.

[namespace.] controller.method ( 

[parameters….,]

Call back Function,

[configuration]

);

• Use JAVASCRIPT remoting in visualforce to call methods in APEX controllers from javascript.
• Javascript remoting has 3 parts.
• The remote METHOD invocation you add to the visualforce page, written in javascript.
• The remote method definition in your Apex controller class.
• This method definition is written in apex, but there are few differences from NORMAL action methods.
• The response handles callback function you add to or include in your vf page, written in javascript.

SOSL STATEMENT evaluate to a list of sobjects , where each list contains the search results for a particular sobject type, The result lists are always returned in the same order as they were specified in the query.

If a SOSL query does not return any records for a specified sObject type , the search results include an empty list for that sObject.

For example, you can return a list of accounts, contacts, opportunities and leds that begin with the phase map.

Note : 

The syntax of the classon Apex differs from the syntax of the FIND clause in the SOAP API.

In Apex, the VALUE of the FIND cause is demarcated with single quotes.

Example:1

FIND 'map*' IN ALL FIELDS RETURNING account (Id, Name], Contact, Opportunity, Lead.

In the Force.com API, the value of the FIND Clause is demarcated with braces.

Example:2

FIND {map*} IN ALL FIELDS RETURNING account [Id,name], contact ,opportunity,lead.

From search list , you can create arrays for each object returned.

Account [ ] accounts = (( list < accounts &GT; ) search list [0] );

Contact [ ] contacts = [( list ) search list [0]) ;

Opportunity [ ] opportunities = ((list < opportunity> ) search list [2]) ;

Lead [ ] leads = (( list < lead> ) search list [3]);

SOSL statement evaluate to a list of sobjects , where each list contains the search results for a particular sobject type, The result lists are always returned in the same order as they were specified in the query.

If a SOSL query does not return any records for a specified sObject type , the search results include an empty list for that sObject.

For example, you can return a list of accounts, contacts, opportunities and leds that begin with the phase map.

Note : 

The syntax of the classon Apex differs from the syntax of the FIND clause in the SOAP API.

In Apex, the value of the FIND cause is demarcated with single quotes.

Example:1

FIND 'map*' IN ALL FIELDS RETURNING account (Id, Name], Contact, Opportunity, Lead.

In the Force.com API, the value of the FIND Clause is demarcated with braces.

Example:2

FIND {map*} IN ALL FIELDS RETURNING account [Id,name], contact ,opportunity,lead.

From search list , you can create arrays for each object returned.

Account [ ] accounts = (( list < accounts > ) search list [0] );

Contact [ ] contacts = [( list ) search list [0]) ;

Opportunity [ ] opportunities = ((list < opportunity> ) search list [2]) ;

Lead [ ] leads = (( list < lead> ) search list [3]);

• When you WANT to call apex class in visualforce page we have to declare in the FOLLOWING format.
• < Apex : page controller = “class NAME “ &GT;
• Whenever we call a visualforce page in which controller attribute is defined it will first CREATE an object for the apex class which is defined in controller.
• When object is created for the apex class first it involves the constructor.

Triggers Are divided into 2 types:

•  Before Triggers
•  After Triggers

1. Before Triggers:

Before Triggers can be used to update or validate values of a record before they are SAVED to the database.

2. After Triggers: 

After Triggers Before Triggers can be used to ACCESS field values of the records that are the stored in the database and USE this values to make changes in other records.

Syntax:

Trigger trigger_name on Object_Name(trigger_events)

{

Code BLOCK

}

WHERE trigger_events can be comma separated list of events.

Triggers Are divided into 2 types:

1. Before Triggers:

Before Triggers can be used to update or validate values of a record before they are saved to the database.

2. After Triggers: 

After Triggers Before Triggers can be used to access field values of the records that are the stored in the database and use this values to make changes in other records.

Syntax:

Trigger trigger_name on Object_Name(trigger_events)

{

Code block

}

WHERE trigger_events can be comma separated list of events.

It will invokes the Apex CLASS to run at specific TIME.

Anybody who want to schedule their class they have to implement schedulable interface.

Schedule Interface:

The class that implements this interface can be scheduled to run at DIFFERENT intervals. This interface has several METHODS.

They are:

Public void EXECUTE(schedulablecontext sc) etc.

It will invokes the Apex class to run at specific time.

Anybody who want to schedule their class they have to implement schedulable interface.

Schedule Interface:

The class that implements this interface can be scheduled to run at different intervals. This interface has several methods.

They are:

Public void execute(schedulablecontext sc) etc.

Batch APEX:

Batch Apex allows you to DEFINE a single job that can be BROKEN up into manageable chunks, WHEREAS every CHUNK can be processed separately.

Batch Apex:

Batch Apex allows you to define a single job that can be broken up into manageable chunks, whereas every chunk can be processed separately.

Salesforce Object Query Language is used to query that records from the database.com based on the requirement.

There are 2 TYPES of SOQL Statements:

• Static SOQL
• Dynamic SOQL

1.Static SOQL:

• The oStatic SOQL Statement is written in [] (Array Brackets)
• This statements are similar to IINQ(Ion Integrated Query)

2.Dynamic SOQL: 

• It is used to REFER to the creation of a SOQL string at run time with Apex CODE.
• Dynamic SOQL enables you to create more flexible application.
• To create Dynamic SOQL query at run time USE Database.Query() method, in ONE of the following ways.
• Return a single sObjects when the query returns a single record. ex:sObjects s = Database. Query(String_limit_l);
• Return a list of sObjects when the query returns more than a single record.

Salesforce Object Query Language is used to query that records from the database.com based on the requirement.

There are 2 types of SOQL Statements:

1.Static SOQL:

2.Dynamic SOQL: 

• Map Class Contains methods for the Map collection type.
• A Map is collection of key values PAIRS where each UNIQUE key maps to a single value. 
• Map keys and values can be any DATA type primitive types, COLLECTIONS, sObjects, users defined types, and built in Apex Types.

EMAIL SERVICES is an automated process that use Apex classes to process the CONTENTS, Headers, ATTACHMENTS of INBOUND Email.

Email services is an automated process that use Apex classes to process the contents, Headers, Attachments of Inbound Email.

• All APEX programs RUNS entirely ON-Demand on Force.com Platform.
• FIRST the platform application server compiles the code into abstract set of instructions that can be understood by Apex runtime interpreter.
• The compile code is stored to metadata.
• When the end users triggers the execution of Apex by clicking button or visualforce PAGE the application servers retrieves the compiled instructions from the metadata and send them to runtime interpreter before returning the result.

• To create Email services
• Create WEB services
• Perform COMPLEX VALIDATION over multiple objects
• To create complex business processes that are not supported by WORKFLOW
• Create custom transaction logic
• Attach custom logic to another OPERATION

• Integrated: It PROVIDES built-in SUPPORT for DML CALLS
• Inline SALESFORCE Object Query Language
• Easy to Use
• Easy to Test
• Version
• Multi Tenant Aware Application

• Apex is a strongly typed object-oriented programming language.
• It allows the developer to execute FLOWS and TRANSACTION control statements.
• Apex enables developers to add BUSINESS logic to most system events like button CLICKS RELATED record updates and visualforce pages.