Use unique fields as a proxy for updating rather than ignoring/inserting a new record.

_Originally posted by @dylanh724 in

Eg:


Name: Foo,
Last Name: SomeLastName

Then on 2nd import:

Name: Foo,
First Name: Bar, // New field to create
Last Name: SomeNewLastName // Existing field with data to update

I expected either a dupe to happen (before the patch) or to update if !null (after the patch), but nothing actually happened (no dupe, no update).

If I were to reimport "Foo", I expected accompanying data to create or update sibling fields (in the example above, First Name, that previously didn't exist).