1
Q
Master-Detail Relationships
A
- The detail object inherits the sharing and security settings of the master object; it cannot have its own sharing rules.
- When master record is deleted, detail record is also deleted
- Owner of the detail record is automatically set to the owner of its associated master record. The owner field is not available. Custom objects on the detail side cannot have sharing rules, manual sharing, or queues, as these require the Owner field.
- Custom object cannot be on the master side of a Master-Detail relationship with a standard object.
- User and Lead objects cannot be the master in a master-detail relationship
2
Q
Schema Builder
A
FUNCTION:
- Dynamic environment for viewing and modifying objects and relationships
- Create and delete custom objects and fields
- Define relationships between objects
PERFORMANCE:
- Objects can be hidden from canvas, fields cannot
- Filter can be used to only display objects of interest
- Map can be used to navigate to objects of interest
- Performance is improved by selecting “Hide Relationships” option
- Cannot import or export schema definition
3
Q
Many-to-Many Relationship
A
- Allows each record of one object to be linked to many records of another object and vice versa
- Create a custom junction object with two master-detail relationships; one to each main object
- Ex: Two custom objects = Project and Team Member. A Project will have multiple Team Members and a Team Member will be assigned to multiple Projects. Create a junction object (Assignments) with two master-detail relationship fields: Project and Team Member. Both the Team Member and Project page layouts will have a related list of Assignments, which can be edited to display only the relevant data.
4
Q
External Lookup Relationship
A
- CHILD = Standard, custom, or external object
- PARENT = External object
- External ID field on parent matches against value of child’s external lookup relationship field
- External object field values come from an external data source
5
Q
Indirect Lookup Relationship
A
- CHILD = External object
- PARENT = Salesforce object (standard or custom)
- EXTERNAL ID & UNIQUE ATTRIBUTES
- When you create an indirect lookup relationship field on an external object, you specify the parent object field and the child object field to match and associate records in the relationship. Specifically, select a custom unique, external ID field on the parent object to match against the child’s indirect lookup relationship field, whose values come from an external data source.
6
Q
How can you relate records using an External ID as an alternative to using the record ID?
A
- Use a custom external ID field on the parent record
- You can only do this if a relationship (lookup or master-detail) has already been defined for the objects
- This can be performed with insert, update, or upsert operations. *The External ID must be unique for upsert operations
7
Q
Considerations for External ID fields
A
- Supported DML = insert, update, or upsert
- External ID field can optionally be set to Unique, but must be unique for upsert operation
- Can be configured as text, number, or email data types
