Hi everyone,
We're in the process of trying to implement the new Contact Permissions Migration to move from the 3 IND fields in T_CUSTOMER to the mapping table for Contact Permissions.
We're struggling with several "architectural" issues with the way this new system is designed because based on our IND field selection values and how we used them, there's no way I can find to create new Permission Types that would reliably represent the data in the new scheme.
For example, we have several choices for Email that can't be easily represented like:
When I first created the mappings, I actually started by adding Permission Types that would map to some of those choices that didn't mean a strait NO the way "No Email Marketing" would. But then I found that you could very easily get lost in a long list of Yes/No/NA choices that could be set up to conflict with each other.
I changed it to just use the same 6 types that were used in the Webinar, plus 2 more for SMS:
We can map the majority of our old dropdowns to these as No, but there are some like "Bad Email Address" that don't really map well.
TASK made a suggestion that maybe we were confused about this, and that Contact Point Purposes should be used. To me that made no sense because you can't create a Contact Point Purpose for "Bad Email Address".
What I would really love to be able to do is add new choices to the gooesoft_dropdown table so there are more choices than Yes, No, and NA. That's where I believe the "Bad Email Address" selection should go. Or something along those lines.
Has anyone else successfully migrated the Contact Permissions with anything other than the standard Email, Mail, and Phone mappings? I would love to talk to you. You can reach me directly at gerald.boutot@strazcenter.org.
Thanks!