When you import something into Slate, like a person record or an application, Slate tries to prevent duplicate records from being created. To prevent duplicates, Slate evaluates matching criteria . Slate does this in a specific order that cor...

When person data comes in through a form or Upload Dataset, Slate tries to find an existing person record for this data, so as not to make a duplicate. Slate looks for matching records based on a hierarchy of data called matching criteria . When ...

When importing to a Dataset destination (such as Organizations, Funds, or Companies and Foundations) using a form or Upload Dataset, Slate attempts to prevent the creation of duplicate records by finding an existing, matching dataset record. As soon...

When importing application data, Slate not only attempts to match an existing person record, but it also sometimes matches an existing application.  This is the case if any of the application matching items are mapped and they match an existing...

When importing data to populate standard system objects such as schools, tests, and devices, Slate attempts to prevent duplicating system objects associated with the person, application, or dataset record. In many cases, matching system objects are ...

When importing data to populate standard system objects such as gifts, addresses, and devices, Slate attempts to prevent the duplication of system objects associated with the person or dataset record. In many cases, matching system objects are updat...