SFDC Interview Questions
SFDC Interview Questions
SFDC Interview Questions
Profiles and Permission Sets provides security for meta-data (Structure) components.
No, once we create an user in sales force we cannot delete the user record. We can only deactivate
the user record.
2. What is 'Grant Account Login Access'? How to enable 'Grant Account Login Access'
If we enable 'Grant Account Login Access' for a user then we can see 'Log in' button on the detail
page of that user. By clicking on that 'Log in' button without giving that user's username and
password we can log in.
To enable the 'Grant Account Login Access' follow the below steps -
At top right corner click on name (Which should be left to Setup) > My Settings
Left side, click on Personal Information > Grant Account Login Access
In Access Duration column select '1 Year' for all the records and click on 'Save' button.
Log out and Log in as any other user in the organization then click on Manage Users > Users.
User should be able to see list of records and verify the user to whom we enabled the Grant
Account Login Access
User should be able to see the Login link beside Edit link.
Click on Login then user should be able to login as that user mode
Observe at top right corner, user should be able to see Logged in as 'Name of the user' which
should be high light in black colour.
Click on Logout
User should be come back to original user's mode, Observe at top right corner, user should not be
able to see Logged in as 'Name of the user'
1
4. What is Profile?
Profile deals with CRED (Create, Read, Edit and Delete) permissions over Apps, Tabs, Objects, Fields,
Record Types, etc...
We can map only one profile for one user and without mapping the profile we cannot create the
user.
To improve the permissions for the users over profiles we should go for Permission Sets.
Example- To give additional permissions to few users who belongs to different profiles over Apps,
Tabs, Objects and fields.
6. How to give permissions to two fields for different users who belongs to different profiles?
Permission sets.
7. How many users are there in your project sales force instance?
1000 (It will depends upon the number of licenses taken by the client, it will be like up to 4000 like
that based on the client)
Roles
Sharing Rules.
Manual Sharing
View all.
Modify all.
9. What is role?
OWD is the default access level on records for any object in sales force.
2
For custom objects we can see below access levels -
Private
Public Read/Write
By default after creating custom object OWD access level is Public Read/Write.
Private: only owner and above hierarchy users can have Read/Write access and below hierarchy
users don't have any access.
Public Read only: only owner and above hierarchy users can have Read/Write access and below
hierarchy users can have only Read Only.
Public Read/Write: Irrespective of role hierarchy every one can have Read/Write permissions on the
records.
Role A
Role B
Role C
If the Role A user through Manual Sharing or Sharing Rules, shares the record to Role C user who is
in lower hierarchy, then the Role B user who is above in hierarchy to Role C user can see the records,
if we enable Grant Access Using Hierarchies at sharing settings else Role B user cannot see the
record.
3
To process bulk records.
In import wizard we can't see few objects (ex: if there is master detail relationship between two
objects then child object we can't see).
Data Loader is a stand-alone tool to process bulk records. With Data loader we can process
maximum of 5 million records. Most of the time we use only Data loader. Default batch size of the
Data loader is 200.
Up set (To Up set we should have one external ID field on the object, based on the external id field
if the value already exists it will update, if doesn't exist then it will insert)
Delete (Delete the records based on the id provided, to delete we need only id, deleted records
can be found in recycle bin)
Hard delete (Delete the records based on the id provided, to delete we need only id, deleted
records can't be found in recycle bin, Note: If we enable bulk API in data loader settings then only we
can perform Hard delete.)
Export (From any object we can export records based on the SOQL query, Note: We can't export
deleted records which are there in the recycle bin)
Export all (From any object we can export records based on the SOQL query, Note: Using Export all
we can export deleted records which are there in the recycle bin also)
.SDL
4
6. How to insert null values into data loader?
In data loader settings we should enable 'insert null values' checkbox otherwise we can't insert null
values.
Suppose we have account table in Sales force and account table outside of the Sales force (ex: .csv
file, sql database). In Sales force all the records can be identified with record id and outside of the
Sales force we can't recognize records with Sales force id that is the reason to compare outside table
and sales force table in Sales force for one of the field we have to enable external ID (we can enable
external id for text, number, auto number and email). If we enable external id we can compare that
particular column with the column which is available in external table. While comparing if the both
column values are same then it will update otherwise it will insert.
2,000 records.
Created
2. What is the difference between Created and every time edited to meet the criteria and Created
and edited to subsequently meet the criteria?
If we select 'Created and every time edited to meet the criteria' whenever we create a record or edit
a record if the criteria of the workflow rule meets then it will trigger every time. If we select 'Created
and edited to subsequently meet the criteria' -
While creating the record criteria meets so that workflow will fire and while editing the record
again criteria meets workflow won't fire (meeting the criteria to meeting the criteria)
5
While creating the record criteria doesn't meet so workflow won't fire and while editing the
record workflow criteria meets then workflow will fire (not meeting the criteria to meeting the
criteria)
Conclusion: Previous state of record should be not meeting criteria and current state of record
should be meeting the criteria then only in current state workflow will fire.
Criteria meet (field - operator - value, if there are multiple criteria’s then in filter criteria we can
give conditions like ( 1 or 2) and 3, field to field comparison is not possible, we can't fetch the
previous state information of the field )
Formula evaluated (we can write formulas with this we can do field to field comparison and we
can fetch previous state value of the record)
The action which will be performed immediately after the record criteria meets.
The action which will be performed in future based on the any of the date field. To create time
dependent workflow action we should create one time trigger. in time trigger we can give either
days or hours with the maximum of 999 value and we can select either before or after.
New field update (we can update a field of the same object or the fields of the parent objects
which are at master side in master-detail relationship, only for master-detail parent objects we can
update the field and for lookup we can't update)
New email alert (we can send emails if the criteria meets)
Text
6
Visual Force
9. There is a time based workflow which will update one of the fields if the criteria meet. User
submits the record with valid criteria, workflow triggered so that the field update is queued in the
'time based flow' queue which will fire after one day. If the user modifies the record which is
submitted before the scheduled date, after modification, a record criterion is not meeting.
Whether the field will be updated or not in schedule date?
It won't trigger in the schedule date because if we modify the record to not meeting criteria that
queued field update will be removed from the 'time based flow' queue.
10. For the same scenario explained in the above question what happens when we deactivate or
modify the criteria of the workflow to different criteria? Whether the field will be updated or not
in schedule date?
11. Scenario: There are two workflow rules on the same object say namely wf1 and wf2. If wf1
fires then a field will be updated on the same object, if the field updated and due to this wf2
criteria meets then what will happen, wf2 will fire or not?
It won't fire. To fire wf2 we should enable 'Re-evaluate Workflow Rules' checkbox of the field update
which is there in wf1.
12. What is recursive workflow rule? How to avoid recursive workflow rules?
Whenever we enable Re-evaluate Workflow Rules after Field Change checkbox in the Field Update of
a workflow rule, due to this field update other workflow rules on the same object will be fired if the
entry criteria of those workflow rules satisfied.
In case in other workflow rules also if we enable Re-evaluate Workflow Rules after Field Change
checkbox in the Field Update recursive workflow rules will come in some scenarios.
For the workflow Evaluation Criteria if you choose created, and any time it’s edited to
subsequently meet criteria option, we can avoid recursive workflow rules.
If you don't enable Re-evaluate Workflow Rules after Field Change checkbox in the Field Update of
a workflow rule we can avoid.
If the criteria of the record meets then by clicking on submit for Approval button user can submit the
record for approval (Note: Approval history related list should be displayed on the record detail
page)
7
14. How to configure Approval Process?
Before creating the Approval Process we should select the object after that we should follow below
steps -
Select the email template (If we don't select any email template sales force by default send an
email notification to the target approver else with our selected email template target approver will
be notified)
Select the users who can submit for the approval (If we do not select any user by default all the
users who can access to that record can submit)
Initial submission actions ( after submitting the record for approval immediately whatever the
actions included in the initial submission actions section will be triggered)
For each and every step we can see 'Approval actions' and 'rejection actions' sections where we
can add actions to be performed
If the Approver approves the record then actions which are under 'approval actions' section will be
triggered
Final approval actions section (If all the steps approved then actions which are under 'final
approval actions' section will be triggered)
Final rejection actions section (If any one of the step rejected then actions which are under 'final
rejection actions' section will be triggered)
Recall approval actions ( After submitting record for approval if you want to revoke we click on
recall approval action on the detail page, after clicking on that button actions which are under recall
approval actions section will be triggered )
15. Scenario: After activating the approval process, I want to add one more step. Is it possible?
It’s not possible, to add one more step deactivate the approval process and clone the deactivated
approval process and add the new steps.
8
To summarize the information.
1. What is Report?
Matrix (we can summarize the information in two dimensional manner, both rows and columns)
Join (we can summarize information in different blocks on the same object and the related
objects)
5 blocks.
4. How many maximum groupings we can do for summary, matrix and join reports?
3 groupings
We can display up to 2000 records on a page. If more records are there to display we cannot see
those through user interface. If you export the records to a excel sheet then you can export all
records.