Fields of two Picklists can be made dependent on each other. As an example consider an application with customers in US and Canada. If there are two picklists - one for country and the other for state. Based upon user's selections of country, the state settings need to get updated. This is implemented by defining controlling and dependent picklists. In the above scenario, country becomes the controlling picklist and state becomes dependent picklist. The controlling and dependent picklists are defined using "Field Dependency" button in "Custom Field and Relationship" section.
There are a two types of object relationships that Salesforce supports - Lookup relationship - Master-detail relationshipThese relationships are used to implement one-to-many relationship. They are created as fields in the child record. As an example in a recruitment application if one applicant can have many interviewFeedbacks, we could create a lookup (or master detail) relationship in the interviewFeedback object pointing to the applicant object. In Master Detail relationship, if the parent record is deleted, then all its children records are deleted. Child records in master-detail relationship do not have owners. They inherit ownership from the parent record.In Master detail relationship, the parent field is required. Also the parent field once specified cannot be changed.Standard Object cannot be on detail side of Master-Detail relationship.
The first master-detail relationship you create on your junction object becomes the primary relationship. This affects the following for the junction object records: Look and feel: The junction object's detail and edit pages use the color and any associated icon of the primary master object.Record ownership: The junction object records inherit the value of the Owner field from their associated primary master record. Because objects on the detail side of a relationship do not have a visible Owner field, this is only relevant if you later delete both master-detail relationships on your junction object.Division: If your organization uses divisions to segment data, the junction object records inherit their division from their associated primary master record. Similar to the record ownership, this is only relevant if you later delete both master-detail relationships.The second master-detail relationship you create on your junction object becomes the secondary relationship. If you delete the primary master-detail relationship or convert it to a lookup relationship, the secondary master object becomes primary.
Data model in salesforce
Data Model in Salesforce
Software Engineer (Force.com)
Object In Salesforce
Equal to Database Table
Defined by Developer
Equal to Database Table
Defined by Developer
Object Fields In Salesforce
System Assigned but can be initialized during record
Referred to User/ User Group
Custom Fields in Salesforce
Can be made dependent
among two fields
of values allowed in
controlling field is
Custom Pick List
Only in User Object
Master=Parent | Detail=Child
Standard objects can't be on the detail side
don't exceed 10,000 child records for a master-detail relationship
Undeleting the master record also undeletes detail and subdetail records
To create multilevel master-detail relationships, you need the "Customize Application"
up to three custom detail levels
Comparison of Object Relationships
Child field value
Ownership & sharing
Inherited from parent
Maximum relationship per
Roll-up summary in parent
Yes (Depend the number
on the object is Standard
Two Master-Detail Relationships
Required 3rd object called junction object
cannot become the master object in a multilevel master-detail relationship
workflow rules and approval processes are allowed
Outbound messages no allowed
Inherits sharing from both masters
cannot delete a parent record if there are more than 200 junction object records AND
if the junction object has a roll-up summary field that rolls up to the other parent.
1st M-D Primary Relationship
2nd M-D Secondary Relationship
On both master objects
Roll-up summary fields that summarize data from the junction object can be created
Formula fields , validation rules on the junction object can reference fields
Limit the Search result for users
Create on lookup, master-detail and hierarchical fields
Compare fields to static value or to other field
Can be required
Define informational messages
• What is a custom object?
– User Defined objects
• List example of custom field types.
– Text, Number, email, URL, pick
list, checkbox, phone, currency, percent. Auto number
• List the 4 types of custom relationships that can be built on
force.com platform. Describe the differences of them.
• What are the two types of lookup filter?