When you import something into Slate, Slate tries to prevent duplicates from being created. To prevent a duplication, Slate evaluates matching criteria. It does so in a specific order that correlates to the quality of the data being evaluated. Yo...

When importing to the Person or Application destination using a form or Upload Dataset, Slate attempts to find a matching person record to update to prevent the creation of duplicate records. Once a record matches a mapped item, Slate considers ...

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

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 appl...

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...