SFDC Q&A - Ignite Your Salesforce Journey

SFDC Interview Questions

1. What is the difference b/w Public groups and Queues?

Public Group: If you want to share some information in your organization among some users, we make a public Group. The Public Group is the group of some selected users, then we can share information or assign some work to the group. e.g – We can send an email alert to a public group.

Queues are used when you want to assign a record to a bunch of users. With the help of queues, you can assign a record to multiple users (using queues) so that any member of the queue can work on the record. e.g – Assign record (Change owner) to queue.

2. How to store dynamic Record URL In Formula Field?

We can use the formula below if we need the record URL in the formula field. This URL will change based on the salesforce organization (sandbox, Production).

LEFT($Api.Partner_Server_URL_260, FIND( ‘/services’, $Api.Partner_Server_URL_260))+ Id

3. How to identify object names based on Salesforce record IDs?

We can know the object name based on the record id. getsObjectType() method tells us the object name.

Id sampleRecId = '0012x000003dKqg';
System.debug('Object Name =  '+ sampleRecId.getsobjecttype());
//Object Name = Account

4. What is the “Big Deal Alerts” feature in Salesforce?

This feature automatically sends an email to users whenever an opportunity reaches a threshold of amount and probability. For example, set the threshold to trigger an alert when the opportunity of more than $10000 and the probability of 90%. The alert sends the plain text message in the email.

In Setup, use the Quick Find box to find Big Deal Alert.
Name the alert.
To activate the alert when you save it, select Active or leave the option deselected and activate the alert later. When you activate the alert, emails are immediately triggered for all open opportunities that meet the threshold.
Enter a threshold: a trigger amount in the corporate currency, and a triggering probability.
Enter Sender settings
1. Enter the name and email address you want to show in the From field of the email. The email address must be your own Salesforce email address (as shown in your Salesforce profile) or a verified org-wide email address.
2. In the User field, select yourself.

6. Enter the email addresses of recipients, separated by commas. If you’ve enabled compliance BCC emails, the BCC: field isn’t available.

7. To send alerts to opportunity owners, select Notify Opportunity Owner.
8. Click Save.

5. What is “Opportunity Update Reminder”?

We can enable update reminder in Salesforce org to let managers automatically send a report of the team’s open opportunities to their direct reports in the role hierarchy.

6. What options are available for Custom and Standard object OWD settings?

FIELD	DESCRIPTION
Controlled by Parent	A user can perform an action (such as view, edit, or delete) on a contact or order based on whether he or she can perform that same action on the record associated with it.
Private	Only the record owner, and users above that role in the hierarchy, can view, edit, and report on those records.
Public Read Only	All users can view and report on records but not edit them. Only the owner, and users above that role in the hierarchy, can edit those records.
Public Read/Write	All users can view, edit, and report on all records.
Public Read/Write/Transfer	All users can view, edit, transfer, and report on all records. Only available for cases or leads.
Public Full Access	All users can view, edit, transfer, delete, and report on all records. Only available for campaigns.

7. What are the available options for Pricebook OWD setting?

Price Book Access Levels

FIELD	DESCRIPTION
Use	All users can view price books and add them to opportunities. Users can add any product within that price book to an opportunity.
View Only	All users can view and report on price books but only users with the “Edit” permission on opportunities or users that have been manually granted use access to the price book can add them to opportunities.
No Access	Users can’t see price books or add them to opportunities. Use this access level in your organization-wide default if you want only selected users to access selected price books. Then, manually share the appropriate price books with the appropriate users.

8. What are the available options for the Activity OWD setting?

FIELD	DESCRIPTION
Private	Only the activity owner, and users above the activity owner in the role hierarchy, can edit and delete the activity; users with read access to the record to which the activity is associated can view and report on the activity.
Controlled by Parent	A user can perform an action (such as view, edit, transfer, and delete) on an activity based on whether he or she can perform that same action on the records associated with the activity. For example, if a task is associated with the Acme account and the John Smith contact, then a user can only edit that task if he or she can also edit the Acme account and the John Smith record.

9. What are the available options for the User object OWD setting?

FIELD	DESCRIPTION
Private	All users have read access to their own user record and those below them in the role hierarchy.
Controlled by Parent	All users have read access to one another. You can see all users’ detail pages. You can also see all users in lookups, list views, ownership changes, user operations, and searches.

10. What is the relationship between Account and Contact?

Account and contact behave as master details in business logic, but as lookup relationships on the UI.

You can create a contact without filling the account i.e it shows that there is a lookup relationship between account and contact.

If you have created contact with an account and you delete that account then contact will be deleted, this shows that it is in a Master-Detail relationship. This is standard behavior.

It is a little like lookup, a little like Master-Detail, but fundamentally behaves exactly the way that salesforce.com wants it to behave to fit the particular purpose of that standard thing. So we can say it is a Standard Relationship.

11. What is Data Skew in Salesforce?

Data Skew generally refers to a condition where data is distributed unevenly in a large data set. Data skew happens when more than 10,000 child records are associated with the same parent record within an org.

Account Data Skew: Certain Salesforce objects, such as accounts and opportunities, have unique data relationships that allow parent and child record access to be maintained in private sharing models. In one of these relationships, having too many child records associated with the same parent object causes account data skew. Say you have a bunch of unassigned contacts and park them under one account named “Unassigned.” This can create issues with record locking and sharing performance.
1. Record Locking: You’re updating a large number of contacts under the same account in multiple threads. For each update, the system locks both the contact being changed and its parent account to maintain integrity in the database. Even though each lock is held for a very short time, because all the updates are trying to lock the same account, there’s a high risk an update will fail because a previous one is still holding the lock on the account.
2. Sharing Issues: When it comes to sharing, the dynamic is similar. When you do something seemingly simple, such as changing the owner of an account, you may need to examine all of the account’s child records and adjust their sharing as well, depending on how you have sharing configured. It may be necessary to recalculate the role hierarchy and sharing rules. And when dealing with hundreds of thousands of child records, that can take a long time.
Ownership Skew: When a large number of records with the same object type are owned by a single user, this imbalance causes ownership skew.
Lookup Skew: Lookup skew happens when a very large number of records are associated with a single record in the lookup object (the object you’re searching against).