therishabh/salesforce-admin

Notes

Salesforce Basic

• Salesforce Classic Experience (CEX)
• Salesforce Lightning Experience (LEX)
• 9 dots - App Launcher
• Department = Profile
• Database table = Objects
• Dropdown list = Picklist

Important for job :
If anything we get by default in Salesforce software = "Standard"
If anything we create in Salesforce software by our own efforts = "Custom"

Q. What is the new field in Salesforce that you worked ? (Tesla Motors, USA)
A. Time

Field Tracking

Q. What are the benefits of field tracking in ur job?
A.

Q. Can we track standard fields ? (TCS)
A. Yes, Only 2 fields we can track [Owner and Name (Auto Number)]

Q. Which standard fields we can not trackt and why ?
A. CreatedBy and LastModifiedBy
Reason: creation record happens only one time thats why Salesforce not provide that facility to track createdBy lastModifiedBy will change complete data we can not track by lastModifiedBy like who change which data and second reason is data is changing very frequently so lastModifiedBy will change many time so Salesforce think there will be no sense to track lastModifiedBy

Q. What are the issues you face when you depend on data of "Last modified by" to track the data change? Is that totally reliable?(IBM)
A. Last modified by only show who change or modify the fields but with that field we can not track which field is changed, so it's not reliable.

Q. If your junior is asking you that he is not able to see field tracking details in related section, what u will do?
OR
By what all reasons we can not track the field changes?
A.

Q. Field tracking helps us to see only "xxx changes". Not "yyy changes".
A. xxx = data, yyy = settings

Q. History tracking feature tracks new and old value for most of the fields but for some fields, it will not do such check. It will only show "Changed xxxxx." (xxxx = field name)
A. Formula Fields, Encrypted Fields, Rich textfield, long textfield, multiselect picklist, more than 255 character field

Q. For which custom field (below 255 length) we can not have field tracking?(Infosys)
A. Formula Field, Auto Number, Role of summary.

Q. Data in history table, how long we can retain that data (Disney)
A. 18 months without coding, with coding we can retain 24 months.
Field history tracking data doesn't count against your Salesforce org's data storage limits.

Q. How many fields we can track per object? (Chase Bank)
A. 20 fields

Field Deletion consideration

Q. Recycle Bin of records Vs Recycle Bin of fields : (Amazon)
1.Difference
2.Common thing
A. delete of any record we can see in recycle bin while delete of any field we can see in deleted field under Fields & Relationships section. as you delete any record or field then they both go to into recycle bin area and wait for 15 days after that data or field will be permanently deleted.
After 15 days, data is permanently deleted from the Recycle Bin

• if you want to free some space by deleting the field then you have to delete those field by permanently otherwise space will not free. (best practice)
• you can check limitation and usase of custom field by go to Object Limits under object manager.

Q. After undelete of fields, are values recovered? (Puma)
A. Yes values recovered.

• When a field is deleted, it will not show on the detail page, nor will it appear in the history section.
• After recovering any field from deletion, all data will be maintained in the history section. (dell)
• Object deleted, Field deleted - we can recover.
• App Deleted - we can not recover.

Important Rules

• If we create a field with text and set its behavior to 'unique,' it will work fine as expected. However, if someone accidentally deletes that field and then recovers it, it will lose its uniqueness property.
• If we have a field with the required property, it will work fine as expected when creating a new record. However, if someone accidentally deletes that field and then recovers it, it will lose its visibility and required property. This means that the field will not be visible after being undeleted, and we will have to set its visibility from the Set-Field-Level-Security section and mark it as required from the Edit section.
• If we have a custom field, it will work fine. However, if someone accidentally deletes that field and later changes the page layout, when the user recovers that field from deletion, it may not be visible in the form as expected. To fix this issue, we need to check the page layout and drag and drop the field to a suitable place.

Global Picklist

• Global picklist or Global value set or Picklist value set

How to decide when we need to create a local or a global PL?

• Becoming proactive in ur project
  
• Check requirement doc neatly
  
• Asking BA

Q. Can we convert local PL to Global PL?
A. Yes.

Q.Major difference while working on local and global PL? (Nokia)
A. in local picklist we can enable

Important Notes:-

• Limit | Useful Points for global picklist:
  
  • 1 Org = 500 GPL
  • 1 GPL = Upto 1k active/inactive values
  • Number of local PLs for 1 GPL = No limit

Field Dependency

In Salesforce, field dependency refers to the relationship between two fields on a Salesforce object where the values available in one field depend on the value selected in another field. This feature allows you to create dynamic behavior in your Salesforce application based on the selections made by users.

In field dependency, there will be only 2 types of fields:

1. Controlling field (primary)
   
2. Dependent field (secondary)
   

Q. Which all are valid fields for field dependency?
A. Picklist, Picklist (multiselect), Checkbox

Q. Which fields can be used as Controlling field? (Infosys)
A. Picklist and Checkbox

Q. Which fields can be used as a Dependent field? (Infosys)
A. Picklist and Multiselect Picklist

Notes :

• If you'll delete controlling field or dependent field and then undelete that field then field dependency will not retain.
• Hide or show Field is not possible.
• Hide or show values is possible.
• A picklist which are controlling can contain max 300 values, but a picklist which are dependent can contain max 1000 values.
• LOV = List of values (all values which will show in dropdown or you can say in picklist)
• if customer provide you a excel file than you can easly add all LOV by copy paste only.
• A picklist which is standalone that means not connected with any other fields then max value it can contain is 1000 only.
• In Salesforce, the maximum character limit for a single picklist value is 255 characters.
• In Salesforce multilevel dependencies are possible (Ex: Country -> State -> City )

Q. What are the limitation of field dependency features ?(Disney)
A. 1. all process need to done manually and when we have large amount of data like 200-300 records then this is not a easy solution.
2. It is limited to only 3 types of fields (picklist, multiselect picklist, checkbox)
3. after undelete dependency gone.
4. Only control value of the field not able to control field itself.

Q. Country is controlling State. State is controlling City.
Country = limit?
State = limit?
City = limit?
A. Country = 300
State = 300
City = 1000

Q. If ur junior is facing limit issue while creating picklist of large data in ur project, then what can be the possible issues?
(the field is NOT dependent of anything. no connection.)
A. 1.LOVs going above 1000 count

2. Characters exceeded more than 15k (IMP IQ)
   (Many people in market dont know this!!!)
   

Means, assume, we have country PL with below values.
India
USA
Canada

(India(5) +USA(3) +Canada(6) ..etc ==> total char limit must be below 15k)

current situation = 14/15000

Q. Have u seen this error in ur project?
"the field you chose is directly or indirectly dependent on itself."
When?
A. when user will select controlling field and dependent field same.

Formula Fields

• There is no such scope for user to enter the data in formula field, Formula field always copy the data from other field.

• In formula field target fields / Output filed can not be picklist and textarea.

• In formula field soruce field from where you are taking data can be picklist or textarea.

• Picklist = ISPICKVAL()

• Picklist Multi Select = INCLUDES()

• we can convert entire content into text with the help of TEXT() function.

• Today() -------> only current date

• Now() ---------> current date and time

• Formula fields can contain up to 3900 characters, including spaces, return characters (ENTER), and comments.

• Q. What is formula field?
  A.

  • This is a special type of field or advanced field
  • User can not make entry in this field.
  • data will be auto populated.
  • Data will be come from another field of from our business logic or some calculations but not directly from user.
  • This is also called as readonly field.
  • we can use cross object formula field. (COFF), when we copy data where the field present in other table, this is also possible

• Which type of field can NOT become a Formula Field ?
  (select 2 wrong options)
  Text
  Number
  Percentage
  Picklist
  Text Area
  A. Textarea and Picklist

• Q. What is limit of spanning relationships per object ?
  A. 15 (spanning relationship means a bridge between two objects)

Relationship in Salesforce

Master Detail Relationship

A master-detail relationship in Salesforce is a type of relationship that tightly links two objects together, where one object (the master) controls certain behaviors of the other object (the detail). Here are the key points of a master-detail relationship in Salesforce:

Key Characteristics of Master-Detail Relationships

1. Parent-Child Relationship: The master object is the parent, and the detail object is the child. The child object is always tightly linked to the parent.
2. Cascade Delete: If a record in the master object is deleted, all related detail records are also deleted.
3. Ownership and Sharing: Detail records inherit the owner and sharing settings of the master record. You cannot have different owners for the master and detail records.
4. Roll-Up Summary Fields: You can create roll-up summary fields on the master object to perform calculations (sum, count, min, max) on the related detail records.
5. Field Limits: Each object can have up to 2 master-detail relationships
6. Standard Objects: You cannot create a master-detail relationship where a standard object is the detail object. Standard objects can only be masters in master-detail relationships.
7. Reparenting: By default, detail records cannot be reparented (i.e., assigned to a different master record). This behavior can be modified to allow reparenting by setting the "Allow reparenting" option during the relationship creation.

• Relationship is to connect objects with each others in Salesforce
• In RTP (Real time project) very rarely you will create any isolated object in your career, most of the time you have to create relationship between them.
• Apart from 5 relationship in salesforce there is one more relationship in salesforce that is External Lookup Relationship which we will use to connect salesforce object with any external object or table (like Dotnet Software table)
• Below 2 lines will help you to make things clear
  • Student (Secondary Object) ---> Many Records
  • Mentor Teacher (Primary Object) ---> One Record
• Salesforce by default supports one to many connection, we need to do some extra efforts for one to one and many to many connection.
• In Lookup Relationship if we'll delete primary record then there is no effect on secondary record but in Master Detail Relationship if we'll delete primary record then secondary record will automatically deleted.
• If you'll delete any record from master detail relationship then as we know secondary record will delete, then the interesting thing is when we'll check recycle bin then we'll find only primary record which we have deleted secondary records are not visible there but in backend it is stored, because when you'll restore that deleted record from recycle bin then primary record will restore as well as all associated record which was deleted due to tightly coupled relationship will also restored.
• In MDR child record will be controlled by parent record. Owner field will not available in child record in MDR because parent record owner will be the owner of child record.
• In one object we can create either max 40 LR or max 2 MDR.
• In LR there is no concept of Roll-up Summary but in MDR there is a concept of Roll-up Summary.
• Reparenting feature is available in MDR with some extra effort by clicking a checkbox of Allow Reparenting. but in LR it is not required because in LR we can change it any time.
• Roll-Up Summary only activated for select when there is MDR and object should be Primary Object of MDR. else it will be show in readonly mode.
• In One object we can contain 40 Roll-up summary.
• We can not have Leads or Users at Master side in a Master-Detail relationship.
• If you want to check what type of relationship between two or more objects then you have to check that with the help of Schema Builder option which is available in setup.
• We can create or modify new object from Schema Builder, even we can add or delete fields of any object with the help of Schema Builder.
• 

Q. What is Relationship in Salesforce ?
A. Connecting two different objects with each others in salesforce.

Q. What are the types of Relationships in SF?
or
How we can connect objects in Salesforce? (IQ:Dell, Nokia, Puma)
A. Lookup Relationship
B. Master-detail Relationship
C. Many to many Relationship
D. Hierarchical Relationship
E. Self Relationship

Q. What are Lookup Relationship features ?
A. - it use to connect objects in simple way

• it works on standard object as well as custom objects
  
• it works to loosly connect two objects.
  

Q. What are the problems with LR (Lookup Relationship)
A. - if we want strong connection or mendatory connection then lookup relationship is not good.

• There is loose bond between objects.

Q. What are the features of MDR
A. - connect two objects with strong connection.

• If primary record deleted then secondary record will be automatically deleted. (this is called Cascading Delete)

Q. What is Roll-up Summary ?
A. - Roll up summary is a special field to show summary of child records.

• we can show summary like total count (total child records), max, min and sum.
• Only works with MDR and Parent object.
• in One object we can contain 40 roll up summary.

Q. What is data skew / data skew error in Salesforce?
A. This is a performance issue which comes into picture due to "limitation of Salesforce software", when one parent record will have more than 10k child records.

Q. What types of fields we can have in the field to aggregate in Roll-up Summary ?
A. Numerical Value (to be precise : number, currency, date, date and time, percentage)

Rule in Salesforce:
STANDARD OBJECTS CAN'T BE ON THE DETAIL SIDE WHEN IN MASTER SIDE ANY CUSTOM OBJECT IS PRESENT, IN MASTER-DETAIL RELATIONSHIP.
(Read above line and tell me which scenario is NOT POSSIBLE in Salesforce projects!!)
Scenario 1:
Master = a custom object
Detail = a standard object

Scenario 2 :
Master = a custom object
Detail = a custom object

Scenario 3 :
Master = a standard object
Detail = a standard object

Scenario 4 :
Master = a standard object
Detail = a custom
A. Scenario 1

Q. What can be done using Schema Builder ?
A.

Q. How to identify MDR or LR in Schema Builder ?
A. MDR and LR we can decide by color of thread which are present between two objects, and three lines means child and one line means parent.

Q. What is the relationship between Account and Contact object ? (Famous question based on exception in SF)
A. Acc and Contact will have Lookup relationship by default.
BUT,
if u connect any record of Account to Contact, then they start behaving like MDR, because if Primary record is deleted then Secondary record will also get deleted. (this is managed by SF internally, so we dont need to do anything for this feature)

Custom Labels Vs Custom Settings Vs Custom Metadata

What is Custom Label in Salesforce?

Custom labels are custom text values that can be accessed from Apex classes, Visualforce pages, or Lightning components. They are typically used for any text that needs to be translated into different languages, or custom text that might need to change frequently.

For example, you could use a custom label to store the error message text that’s displayed to users. If you need to change that message, you can just change the label, rather than editing and re-deploying your code.

What is Custom Setting in Salesforce?

Custom settings are similar to custom labels, but they’re used to store data that your org might need to reference frequently. They can store any kind of data, like numbers, strings, or dates, and can be used to create org-wide settings.

Use cases might include things like controlling behavior of your code (for instance, enabling or disabling features without changing the code), storing information that is used across multiple classes or triggers (like thresholds or constants), and reducing SOQL queries as data is cached and available across the org.

1. It is a way through which anyone can get easier and faster access to data.
2. The main advantage of using Custom Settings is that the data is cached, which enables efficient access without the cost of repeated queries to the database.One doesn't have to use SOQL queries which count against the governor limits.
3. Custom settings data can be used by formula fields, Visualforce, Apex, and the Web Services API.

List Custom Setting

1. It provides a reusable set of static data which can be accessed across your organization.
2. The data in List Custom Settings is directly visible to any user in the org. Eg: Let's suppose we want to add custom settings of phone codes of countries. For example, if someone chooses India, automatically a +91 number initiates in the form, thus, it is not necessary to fetch from the database by using SOQL query in the backend. So, let's fill the label and object name accordingly. We will choose the setting type as List.

What is Custom Metadata in Salesforce?

Custom Metadata Types stores the records in a memory cache which allows faster retrieval of data when you execute a query.

Custom Metadata Types in Salesforce are similar to custom objects. It has a suffix of “__mdt” instead of “__c” in the API namespace. Let’s say if you create a Custom Metadata type with name “Apex Hours”, the API name of the metadata type would appear as – “Apex_Hours__mdt”.

• This doesn’t count against Governor limits.
• It are deployable from one environment(Org) to another environment. You can package your metadata along with data or deploy it easily from one Org to another.

For more detail : https://www.apexhours.com/custom-metadata-types/

Lightning Flow

• Flow is very powerful tool which is available in salesforce.
• Flow Provides declarative process automation.
• In Salesforce there are two types of development
  • Declarative development
  • Custom development
• Declarative development is also known as low code development.
• Lightning Flow provides this point and click automation tool i.e. Flow Builder
• Lightning Flow is a product, process build and flow builders are name of the tools.
• If you talk about the product then it's Lightning flow and if you talk about the tool with which you'll be implement the flow so that is flow builder.
• Work flow and process builder are getting retired, they are deprecated now.

Security

• Security topic = (this is not a single topic, this is group of topics!!!)
  • External Security
  • IP setting
  • Password reset
  • Audit trail
  • User Management
  • Internal Security
  • OWD
  • Profile
  • Permission set
  • Roles
  • Sharing Rules
  • Manual Sharing
  • Field Level Security
  • Queue
  • Public Group

User License

• In Salesforce we have multiple licenses but 2 license is very famous i.e. Salesforce License and Salesforce Platform License.

• Salesforce software for learning purpose so obviously giving limited Licenses, salesforce provide only 2 license for Salesforce and 3 license for Salesforce Platform.

• User License is main License and there are few checkbox in user setup those are secondary License or we can say featured License.

  

• How many License we have ? we can check that by typing Company information in quick search in setup, then scroll down and there is a section of User Licenses in that section we can check all available Licenses and used Licenses.

  

• What are the difference between Salesforce and Salesforce Platform License ?

  • Answer

    Salesforce License	Salesforce Platform License
    Any Standard Object	Can work on few Standard Object
    Can work on any custom Object	Can work on any custom Object

• Which is the most costly License salesforce or salesforce platform ? (Answer : Salesforce License)

• What situation you will recommend your client to use salesforce platform License ? (Answer : Budget issue, and entire requiment will be fullfill by custom object then salesforce platform License is sufficient)

• What are the different ways to reset the password in salesforce ?

  • Answer :
    • Company Level
    • Department Level
    • User Level

• In the real time project how many licenses do we need to purchance to inform client ? (Answer : We should ask with client that how many people are there, as per that we need to do the needful)

• can we delete the user in salesforce ? (Answer : No)

• Why we can not delete user from salesforce ?

  • Answer :
    • Salesforce user have connection with various possible settings in salesforce software which can collapse if user will deleted
    • User connection to various business responsibilities which can damage salesforce org integrity
    • if user changes some data and if we delete that user then how we can track who delete what data.

• For example, salesforce licence cost $50 to $300 per user per month and there are 10 people resign today so how we can save money as you said we can not delete user ? (Answer : just deactivate user by edit user option and remove checkbox from active then save)

• There is a option available in user section that is Freeze, which is similar to deactive user not exact same, by Freeze we can block a user to login, from making entry into the salesforce org.

OWD (Organization Wide Defaults)

• OWD is a initial level of setting we do for every object while doing Security. In other words OWD is a setting by which we can decide how records of a specific object can be availble for all the users in the company except the owner.

• What are "key" types of OWD settings in Salesforce ?

  • Answer
    • Public Read and Write
    • Public Read Only
    • Private

• In OWD we will perform action which will impact complete organization.

• Admin can login any user from users section in setup, firstly admin need to be activate Login Access Policy then login link will be visible in users section.

  

• When any user will login from users section as maintioned above and after logout that user admin should be still login, but by default when you'll logout from user then admin will also logout, to maintain this session we have to change in session setting section under setup. (You have to uncheck "Force relogin after Login-As User")

  

• Most of the companies salesforce Unlimited addition using. (all the features of salesforce)

• In salesforce project creator of any record is not such useful, compared to Owner of that record. Owner is responsible of his record, creator will not responsible.

• We can change OWD setting from Sharing Settings section to change object Default Internal Access. By default Defaul Internal access is Public Read and Write.

  

• In OWD delete facility is not possible only view and edit facility is possible.

• Issue :

  • whatever setting we do, it applies for everyon in the company we can not set things for few people.
  • We can not give delete facility by OWD.

Profile

• What is Profile, and when we have things like OWD, why we need Profiles ?
  • Answer : In OWD, we can make selective sharing of data accessibility hence we need to use Profile. Profile is a collection of some rules which help us to improve some Implement some restrictions some rules and regulations in a group of people and it's not going to make a flat impact on entire company in short we have flexibility which is absence which is absent in OWD.

Permission Sets

• In profile we are doing clone of profile with another profile but in permission sets we don't need to clone it, we can create fresh permission sets
• What is Permission Sets ?
  • Permission Sets are the extensions to the Profiles !
  • Permission sets is only for giving not for taking out the access which user already has.
• What are the benefits of Permission Sets ?
  • We can have only one profile for one user by default but here in permission set we don't have that problem, one person can have 3 permission sets, 300 permission sets and so on.
  • In Profile we can add only that user which having matching license but in permission sets we can add, a person which have Salesforce License also, a person which have Salesforce Platform license also.
  • In Profile is something we use to give a same level of setting for all the users in the department but in permission sets is for different different settings for different different users.
• In one saleforce Org how many permission set we can create ? (Answer : Approx 1000)
• Salesforce decided in future more focus on Permission sets and less focus on Profile.
• if you want to disable setup option on any user then there is an option in profile "View Setup and configuration" you should deselect that option.
• Fill in the blanks: (20 sec)
  • OWD = impacts "entire xxx" FOR THAT OBJECT (xxx = organization)
  • Profile = impacts "entire yyy" FOR THAT OBJECT (yyy = department)
  • P'set = impacts only "specific zzz" from a dept FOR THAT OBJECT (zzz = user)
• Object should be private in OWD (99.99% objects)

Role

• If you'll close the door (remove permissions) for any user from OWD, then profile and Permission sets and by Role we can give permission to that user to access the data.

• What is significance of role?

  • In a project if OWD of object is private as well as there is no admin level access like profile, permission sets still the senior level person can access the record owned by Junior, how by role facility.

• What is the access level the senior can get on records shared by Roles? (Answer : RED Read-Edit-Delete)

• Suppose there is a user (A), and he has one junior person (B) under his role although person A is not able to see records of his junior person. for this, main reason is under OWD there is an option Grant Access Using Hierarchies should be enabled.

  

• Any Salesforce org created in 2022 or later, the count of role became 10000, for older org, the maximum number of roles allowed is 500 only.

Sharing Rules

• While working on sharing rules currency field is not supported.

• 

• What is sharing rules ?

  • To share the records, based on some conditions, we use SR. (dynamic sharing) [This is called as selective sharing]

• What are the different types of Sharing rules ?

  • Owner based and criteria based.

• Permission available in sharing rules (Read and Read/Write)

• In sharing rules, previous records also shared based on criteria which you have selected.

• problems with sharing rules ?

  • we have some selected fields in sharing rules (suppose we can not select criteria base on currency field)
  • Sharing rules does not give permission to delete the record only edit or view permission we can provide.
  • We can not share record with a single person.

---

Levels of Data Access

• Organization
• Objects
• Fields
• Records

Organization

• Maintain a list of authorized users
• Set password policies
• Limit login to certain hours and locations
  • Limit IP Addresses from which users can log in
  • Limit the times at which users can log in

Object Level Security

• You can control object level permissions for both Standard and Custom Objects.
• You can set permissions for a particular object.
• You can give permissions to view, create, edit and delete any records of that object.
• You can control object permissions using profiles and permission sets.

Field Level Security

• You can restrict access to certain fields in Salesforce, even if user has object level access.
• You can make a field visible to a particular user and can hide that from another user.
• You can give Read or Edit permission to a field, if you don't give both then that field will not be visible.
• Field Level Security can be controlled using Profiles and Permission Sets.

Profile

• A profile is a collection of settings and permissions.
• Profile settings determine which data the user can see, and permissions determine what the user can do with that data.
• A profile can be assigned to many users, but a user can have only one profile at a time.
• To create new profile you need to clone existing profile.

Permission Set

• A permission set is a collection of settings and permissions that give user access to various tools and functions.
• Permission sets extend users functional access without changing their profile.
• Through Permission sets permission can be granted and any time it can be taken away as well.
• Users can have only one profile, but they can have multiple permission sets assigned.

Permission Set Group

• Permission Set group bundles different permission sets together based on a persona.
• A permission set group includes all the permissions available in the permission sets.
• One permission set can be included in more than one permission set groups.
• A user can be assigned one or more Permission Set Groups.
• Also we can assign Permission Set and Permission Set Groups together to users.

What is MUTE in Permission Set Group?

• One can mute some permissions in Permission Set Groups so that they won't be given to the user.
• If you mute particular permission in Permission Set Group then it won't impact individual Permission Set, they remain intact.
• You can anytime unmute the permissions in permission set group.

Record Level Security

• You can restrict access to records for users, even if user has object level permissions.
• For example, a user can view his own records but not others.
• You can manage Record Level Access in following ways: • Organization-wide defaults
  • Role hierarchies
  • Sharing rules
  • Manual sharing
  

Organization-wide defaults

• It specified the default level of access of records.
• Org-wide sharing setting lock down the data to the most restrictive level.
• Here you have three access level: • Private
  • Public Read-Only
  • Public Read/Write
  
• You can use other Record Level security and sharing tools to open up the sharing of records.

Role Hierarchies

• It gives access for users higher in the hierarchy.
• That user can access all records owned by the users below them in the hierarchy.
• Each role in the hierarchy should represent a level of data access that a user or group of user needs.

Sharing Rules

• These are exceptions to Org-Wide defaults.
• Through sharing rules you can share records to a group of users.
• So that, they can get access to the records they don't own or can't manually see.

Manual Sharing

• It allows owners of particular records to share them with another userS.
• Manual sharing is not automated like Org-wide defaults, Role hierarchy or sharing rules.
• It can be useful in some situation where you manually want to share a record with another user.