This feature was available in DemandTools by Validity (which I used for 10 years).
In an excel file, duplicate records could be flagged as master or non-master in a single row. When the file was imported, only those 2 fields needed to be mapped as master or non-master. Then we could merge the records.
We need something similar here as I have a subset of duplicate records where I've had to identify the master record (using a snowflake query based on count of populated fields for specific fields). In almost half the records, the master record identified from this query do not match the master record identified in datagroomr when setting the master record based on certain criteria.
Steve Pogrebivsky can provide more insight since he was previously employed with Validity.
So now, I'm having to take multiple steps to have the correct master record flagged and then run my merge.
Pamela Giovanelli
Hi there,
This feature was available in DemandTools by Validity (which I used for 10 years).
In an excel file, duplicate records could be flagged as master or non-master in a single row. When the file was imported, only those 2 fields needed to be mapped as master or non-master. Then we could merge the records.
We need something similar here as I have a subset of duplicate records where I've had to identify the master record (using a snowflake query based on count of populated fields for specific fields). In almost half the records, the master record identified from this query do not match the master record identified in datagroomr when setting the master record based on certain criteria.
Steve Pogrebivsky can provide more insight since he was previously employed with Validity.
So now, I'm having to take multiple steps to have the correct master record flagged and then run my merge.
Thanks!
Pam