SFDC Interview Questions
13. Which two parameters are configured using the locale setting?
- Time and Number display format
- First Name/Last Name and Date format
14. What permission is required to edit the record in the list view?
- Enable Inline Editing
- Enable Enhanced Lists.
15. What are two reasons a user can not be deactivated?
- The user is the recipient of the workflow alerts.
- The use is a customer community administrator
16. How can multiple campaign records be associated with a single opportunity?
We can configure influential campaigns to be automatically added to opportunities. When the automatic association is enabled, influential campaigns are added to opportunities when a campaign is related to a contact that is assigned a contact role on an opportunity prior to the close date of the opportunity.
17. What features track how often a file is viewed?
Content Deliveries – this allows you to convert documents such as Microsoft PowerPoint and word files into an optimized web-based version for easy online viewing, you can track how often the file is viewed if you send the file URL to any recipient.
18. What is the profile and permission set?
Profiles and permission sets are collections of settings and permission that determine what a user can do in the application.
Profiles are typically defined by the user’s job functions.
We can use the permission set to grant more permission and access settings to users.
19. What is field-level security?
Sometimes we want users to have access to an object while limiting their access to individual fields in that object. Field permission/security is also controlled in profiles and permission sets.
20. What is record-level security?
Record level security lets you give users access to some object records but not others. Every record is owned by a user or a queue.
The owner has full access to the record. In a hierarchy, users higher in the role hierarchy always have the same access as users below them in the hierarchy. This applies to records owned by users and records shared with them.
To specify record level security, set your organization-wide sharing, define a hierarchy, and create sharing rules.
21. What is an organization-wide sharing setting?
The first step in record-level security is to determine the organization-wide sharing setting for each object. OWD sharing settings specify the default level of access users have to each other’s records.
We can use OWD sharing settings to lock down our data to the most restrictive level and other record-level security and sharing tools can be used to give access to other users.
22. What is role hierarchy?
A role hierarchy, in conjunction with sharing settings, determines the levels of access users have to your Salesforce data. Users have access to the data of all users directly below them in the hierarchy.
Users who need to see a lot of data (such as the CEO, executives, or other management) often appear near the top of the hierarchy.
Regardless of the org-wide default settings, a manager always has access to the same data as his or her employees.
Users who tend to need access to the same types of records can be grouped together. We’ll use these groups later when we talk about sharing rules.
Roles can control the level of visibility that users have into your Salesforce data, depending on your sharing settings. Unless your sharing model for an object specifies otherwise, users at any role level can view, edit, and report on all data owned by or shared with users below them in the role hierarchy.
If the Grant Access Using Hierarchies option for a custom object is disabled, only the record owner and users granted access by the org-wide defaults have access to the object’s records.
By default, the Grant Access Using Hierarchies option is enabled for all objects. It can only be changed for custom objects.
23. Who can manually share records?
- The record owner
- The record owner’s manager
- The record owner’s manager’s manager
- The system adminstrator
Object Relationship Overview
24. What is a Master-detail relationship?
Master-detail relationship closely links objects together such that the master records control the behavior of detail and sub-detail records.
- Deleting a child/detail record moves it to the recycle bin and leaves the master record intact.
- Deleting a master record also deletes related details and sub details records.
- Undeleting a detail record restores it and undeleting a master record also undeletes related detail and sub-detail records.
- If you delete a detail record and later separately delete its master record you can’t undelete the detail records as it no longer has master records to relate to.
- By default, the record can’t be reparented in a master-detail relationship. Administrators can, however, allow the child records in a master-detail relationship on the custom object to be reparented to different parent records by selecting the “allow reparenting” option in the master-detail relationship definition.
- The owner field on the detail and sub-detail records isn’t available and is automatically set to the owner of the master record.
- Custom Objects on the detail side of a master-detail relationship can’t have sharing rules, manually sharing, or queues as these require an owner field.
- Detail and sub-detail records inherit security settings and permission from the master records. You can’t set permissions on the detail record and sub-detail record independently.
- The master-detail relationship field is required on the page layout of the detail and sub-detail records.
- Each custom object can have up to two master-detail relationships.
- If the child entity has “Modify All” or “View All” >> The “View All” permission will be enabled on the parent entity.
- If the child entity has the “View All” or “Read” >> The “Read” permission will be enabled on the parent entity.
25. What are many-to-many relationships?
Master-detail relationships can be used to model many-to-many relationships between any two objects. Each record of one object can be linked to multiple records of another object via a many-to-many relationship, and vice versa.
26. What exactly is the lookup relationship?
Links two objects together, lookup relationships are similar to master-detail relationships, except they don’t support sharing or rollup summary fields.
If the lookup field is optional, you can specify one of the 3 behavior to occur if the lookup record is deleted
- “Clear the value of this field” This is the default.
- “Don’t allow deletion of the lookup record that part of a lookup relationship”
- “Delete this record also” is available only if a custom object contains the lookup relationship not if it’s contained by a standard object.
27. Tell me about the external lookup relationship.
An external lookup relationship links a child’s standard, custom, or external object to a parent’s external object.
When we create an external lookup relationship field the standard external Id field on the parent external object is matched against the value of the child’s external lookup relationship field.
28. What is an indirect lookup relationship?
An indirect lookup relationship links a child’s external object to a parent standard or custom object.
29. How to create the hierarchical relationship in the salesforce?
A special lookup relationship is available only for the user object. it lets users use a lookup field to associate one user with another that does not directly or indirectly refer to itself.
30. Which objects support business processes?