ImportOmatic - Birthdate

Derek Todd

With birthdate now being an encrypted field in Patch 34 for Raiser’s Edge NXT and Raiser’s Edge, it makes duplication criteria in ImportOmatic more limited, making the processes nearly fully manual and laborious. Has anyone found a workaround that allows ImportOmatic to run through the import quickly? Perhaps a different field from RE like email or phone? Has anyone found that moving birthdate to an attribute field is a good workaround?

Alex Wong

@Derek Todd
we do not use birthday as part of duplicate search criteria. I'm not sure if your org is more able to get birthday from constituent or not, for us, we have very little birthday.

So our IOM dup search is based on 2char first name, 8char last name, address and email.

Jeannie Goings

@Derek Todd
to confirm, this is regular ImportOmatic and not the cloud version?

Derek Todd

Hi @Jeannie Goings
That is correct.