Using Source to Master to update a Contact's Account based on Enrollment History
- Navigate to the Source to Master Objects tab.
- Click the New Source to Master Object tab.
- Enter the following:
- Source Object = TargetX_SRMb__Enrollment_History__r
- Order By = LastModifiedDate DESC
- Save your changes.
- Select the New Tracked Field button:
- Set the Source Field to the Account (School) field on the Enrollment History object, which is TargetX_SRMb__Account__c.
- Set the Target Field to the Account(School) on the Contact field, AccountID.
- Save your changes.
- Navigate to the RM Preferences tab.
- In the Profile Builder Rollups section, select the Contact rollup from Enrollment History checkbox.
- Save your changes.
Configuring the Source to Master 'Order by' clause
Depending on your needs, you can customize the 'Order by' clause. A common field to use is LastModifiedDate, which can be sorted to return the 'latest' record. As a Best Practice, you should add more than LastModifiedDate criteria in your order by clause for Source to Master: LastModifiedDate DESC
When ordering by multiple fields, the order by clause should not contain spaces before and after the comma.
Example: TargetX_SRMb_Stage_c ASC,LastModifiedDate DESC
DESC will arrange the records in Descending order:
- For number fields - largest to smallest
- For Date fields – the most recent dates will be listed first.
- For Text fields – Z to A
ASC will arrange the records in Ascending order:
- For number fields - Smallest to largest
- For Date fields – the oldest dates will be listed first.
- For Text fields – A to Z
Notes:
- Use unique field data for Enrollment History records, such as the Attended Start Date of the most recently attended school.
- When using LastModifiedDate on the Application object, be aware that the Application's LastModifiedDate will get updated if a student 'Withdraws' an application. In that scenario, the withdrawn application could end up as the 'rolled up' information. When rolling up information from the Application field, consider using 'Submit Date' in your 'Order by.'
Accounting for 'Null' records
Sometimes, you may want to configure the 'Order By' clause to disregard any records with no data (i.e., 'Null'). System fields, such as LastModifiedDate, would not have a NULL as the system requires and updates this automatically. However, if you are using a Custom field which could be Null, you may want to have those records disregarded so that the data rolled up is valuable to your users.
Here's an example using the 'Start Term Year' field:
TargetX_SRMb__Start_Term_Year__c DESC
To Account for records with nulls, add 'NULLS LAST' (this puts nulls at the bottom so that they won't be used for the rolled-up data):
TargetX_SRMb__Start_Term_Year__c DESC NULLS LAST