Agenda

 Roll-Up Summary Field

 Field History Tracking
 Record Types
Rollup Summary field

 Rollup Summary field is a read only field which is used to calculate the count of child
records, Sum, Minimum, Maximum of a field on the child object. It is enable for
master in Master – Detail Relationship.

 Roll-Up Summary field means working on the child object.

 Rolling up the child records and computing the value on the Parent record.

 Rollup Summary Field  can not be created in lookup relationship.

 Using Apex Trigger we can create Rollup Summary field in Lookup relationship.

 In Salesforce.com, we can make four function to work with Rollup
Summary field. They are

 Count – Number, Currency.

 Sum – Number, Currency.

 Minimum – Number, Currency, Date.

 Maximum – Number, Currency, Date.

Roll-up summary field functions:

Count():
Count displays the record count. It calculates the number of child records in the
master-detail relationship.

Min() :
Min calculates the least values for a specified field on the child records. Number,
currency, percent, date and date/time the fields are available for Min calculations.

Max() :
Max calculates the highest values for a specified field on the child records. Number,
currency, percent, date and date/time the fields are available for Max calculations.

Sum() :
Sum Calculates the sum of the values of a specified field on child record. Number,
currency and the percent fields are available for sum calculations.
Q&A
 Field History Tracking :
 Salesforce field history tracking is a method that can be used to track changes associated with each specific field. It can
be used for both standard objects as well as custom objects that are specific to your company.
 For a particular field, the process is straightforward. The field to track is selected, and the field history is displayed in
the history-based list of the object. This field history data is placed for up to 18 months through the organization and 24
months via the API.
 With Field History tracking, the field history of custom objects, as well as standard objects, can be tracked.

 Limitations Of Using Field History Tracking

1. You can only track 20 fields per object.
2. For some fields like Text Area (Long), Text Area (Rich), and Picklist (Multi-Select) and Changes to fields with
more than 255 characters are tracked as edited, and their old and new values are not saved. 
3. If a trigger causes changes to objects for which the user does not have permission to edit, the change is not
tracked. Field history takes into account current user permissions.
 Enable Field history tracking:
1) enable feed for standard object or custom objects in Salesforce
 Now we have to define which are the fields that to be tracked.
 3) Now add related list to the page layout.
 To check field history tracking in Salesforce create any new record in sample and change the
quantity field. Basically, in this example we changed quantity field from 100 to 110. So, it
tracked the field as well as the old values and new values. These values are stored only
for fields less than 255 characters.
Q&A
Record Types:
“Record types let you offer different business processes, picklist values, and page layouts to different users. You might
create record types to differentiate your regular sales deals from your professional services engagements, offering different
picklist values for each. Or you might display different page layouts for your customer support cases versus your billing
cases.”
Implementation:
1) Create below 2-page layout with diff field and picklist value
a) userOnepageLayout
b) userTwopageLayout

2) Create two profile or use existing one

c) UseroneProfile
d) usertwoProfile
3) Create 2 record Type and assigned to respective profile and page layout
e) userOneRecordType
f) userTwoRecordType
 4) Assign above profile to user1 and user 2
 A) user1 = userOneProfile
 B) user2 = userTwoProfile

 Now see you can be able to see different layout to each user with different picklist value and page
layout field.

 They are used to drive which page layouts users see when viewing records, based on their user profile.

 Record Types are used to assign the different Page layouts to different users based on their profiles.
And to enable different sets of Standard/Custom Picklist values for two different users using the same
page layout.
Thank You