Hi everybody,
We have not been using different login type names to indicate whether a given login belongs to N1 or N2 in V10, so in V11 our logins will all migrate to the household. We may want to move some of them to the individual level after the conversion. Does anyone know if there's a cleaner way to do this then the old "delete it here and reset it over there" technique, which will wipe the password that the customer may have set?
Thanks,
Beth
I was just thinking about something similar to this the other day, but in a "before conversion" scenario. This may or may not be a useful suggestion, depending...
We have been inconsistent in marking logins' n1n2_inds, but we do use different eaddress types that indicate n1n2edness on the eaddresses. So I wrote a quick script that sets the n1n2 ind to n2 for logins tied to n2-type eaddresses. In a bit of cleanup I also wrote a script with the soundex function to check for n1-typed eaddresses that sound like n2 to review those. So if name2 is "Jim Smith" and the eaddress is jimsmith@gmail, and name1 is Margaret Smith, we just flip the eaddress type to a name2 type, and subsequently flip the login based on the eaddress. Not useful for people with funky emails not remotely similar to a human name, but it can make a dent.