Consolidate Records and the effects of Master vs. Alias

The master record is the record that is retained, while values for the alias record are merged into the master record.

The addresses and devices (contacts) for the alias record become associated with the master record, and those addresses and devices are given a low priority (unless they are inactive, in which case they remain inactive).

Materials, applications, schools, devices, tests, interactions, form or event registrations, etc., are moved to the master record.

The person status of the master record is updated to match the most advanced status of the two records. For example, person statuses follow the order: Prospect -> Inquiry -> Applicant. If the master record was a Prospect, and the alias record was an Inquiry, then the master record is updated to "Inquiry". If the master record was an Applicant, then it remains an Applicant even if the alias record was a Prospect.

Any standard or custom field values that already exist on the master record are retained.

Standard Fields

If the master record has a value for a standard field, such as name, birthdate, sex, or citizenships, then the master record value is retained. If the alias record has a value for a standard field that the master record does not have, then the value from the alias is saved to the master record. For example, if the alias record has a Slate Override ID, and the master record does not, the Slate Override ID for the master record is updated to match the alias record's Slate Override ID. 

Custom Fields

If the alias record has values for fields that store a single value that the master record did not have, then those values are merged into the master record. 

If the master record already has a value for a field that is configured to store a single value, then the master record keeps that value, and the alias value is not used. 

If the alias record has values for fields that store multiple values, any values that the alias record has that the master record does not have are appended to field values associated with the master record.

Exceptions to the Custom Field Behavior

If the master record has an application in the active period, then the merge acts like a "Safe" data import, where the custom fields are not updated unless the field itself is marked as "Unsafe." This setting can be updated for specific custom fields in the Fields section of the Admin Tool. This "Unsafe" setting on a field overrides the "Safe" setting for imports through Upload Dataset, form/event registrations, and Consolidate Records for just the specific field.

Manual Data Transfer Between Records

Individual data points can be manually transferred between records. Access the Transfer Objects tool through the Database, or by selecting "Advanced" in the lower-right corner when comparing two records in Consolidate Records. 

Important

Slate is an active, transactional database, and records cannot be completely unmerged as activity occurs on a merged record.
Was this article helpful?
5 out of 5 found this helpful