Objects And Applications Flashcards
What is the difference between a lookup and master-detail relationship?
Both allow one object to be related to another in a one-many relationship. However, in a master-detail, the detail record wouldn’t exist without the master and usually when the master is deleted, the detail records are deleted.
How is a many-to-many relationship created?
Using a Junction object. This object sits between the 2 objects in the many-to-many relationship, and has 2 master-detail fields, one for each of the objects to be related.
What is the appropriate relationship type if one record would not exist without the other?
A master-detail relationship is used when one record would not exist without the other, such as Order Line Items would not exist without Orders
When should a many-to-many relationship type be used when relating custom objects?
When a record from one object can be linked to multiple records from another object and vice versa
If there is a possibility that a detail record should be linked to a different parent record be linked to a different parent record when the master is deleted, should a master detail relationship be used?
Yes, master-detail relationship types have a reparenting option to allow detail records to be associated with another master record.
Which relationship type could be used to link one contact with another?
Self relationship (thru Lookup Relationship field)
Which relationship is if the security and ownership of the child custom object records should depend on the parent standard object record?
Master-detail relationship
Which relationship type is available on the user object record to associate one user with another?
Hierarchical relationship
What needs to be created to define a many-to-many relationship in Salesforce?
A junction object with two master-detail relationship fields
Which standard objects are not supported for master-detail relationships?
User and Lead
Which option is available to allow a detail record to be linked to a different parent record in a master-detail relationship?
Allow reparenting
What needs to be true in order to convert a master-detail relationship to a lookup relationship?
There should be no roll-up summary field on the master object.
What is an important consideration for converting a lookup relationship to a master-detail relationship?
The lookup field in all detail records should contain a value.
Which type of field can be created to count and display the number of records of a child object that is related to a parent object though a master-detail relationship?
Roll-Up Summary Field
