Recent changes in Organization contact email/phone records?

Options

I've recently started to see some strange behavior from Organization contact email records.

Web view showing a contacts primary email only on the organization record (2 email shown when looking at the contact's own record).

Import validation is throwing exceptions that email records that I just exported and can plainly see in the record don't exist.

Has something changed recently about these records?

Tagged:

Comments

  • @Jordan Yarr Can you clarify which record the email addresses live on and which one you are trying to import them to? Organization Constituent, Individual Constituent, Individual Relationship (Contact), etc.

  • @Christine Robertson Everything I am doing currently pertains to Individual relationship records.

    In the case of the import I'm working on updating old records that don't have an email marked as primary so that every record will have a primary email.

  • @Jordan Yarr Are you moving email addresses from one record to another or trying to update the existing ones with the Primary check box?

    To update the existing, you have to have all of the relevant Import IDs. One of the more annoying things in DB view is that you can't access Phone Import IDs in Query, so you have to use Export (which doesn't always format the file as you would want for this type of clean-up project).

  • @Christine Robertson

    I am trying to update the primary checkbox.

    What I've done is export a csv with Import ID and the primary checkbox change some of the “No”s to Yes based on various criteria then bring them back into RE with the import tool. Its working for about a third of the records.

    the others have exceptions:
    Some say that relationships phone/emails can't be primary (which I don't fully understand but I'm seeing this behavior when updating records manually)

    The rest say this record does not exist which is simply incorrect and I just exported these records minutes before.

  • Alex Wong
    Alex Wong ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Jordan Yarr
    when you say “import id” what import id are you talking about, based on what you said, you might be using the wrong import id.

    Constituent Import Id is used to change constituent data (one to one data, such as name, title, gender, etc)

    relationship import id is used to change a relationship's data, as there can be more than one relationship with a constituent, so you need to specify which relationship to update

    phone import id is used to change a phone (or email) data, as there can be more than one phone/email, you need to specify which phone/email to update.

    So for an individual relationship's phone that you want to change using import, you will need the relationship import id AND the phone import id.

  • Alex Wong
    Alex Wong ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Christine Robertson
    export is harder here due to what you said, doesn't format right.

    You can use the Admin>Import module to export the various import id, which will come out formatted properly, one row per phone record.

  • @Alex Wong
    Yes the import ID for the relationship record and the phone/email are both part of the import. I'd assumed I'd done that more or less correct as about a third of my changes were able to import

  • I've been experimenting more with entering individual relationship emails in web view. Has web view always been limited to entering only one email on these records?

    I'm used to Database view where entering multiple has been the norm (and is currently possible)

    Edit: This was just the UI for adding a new individual relationships. Once they're created adding multiple emails works fine. My mistake

  • Alex Wong
    Alex Wong ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Jordan Yarr
    i have no issue entering more than one email on webview for a non-constituent individual relationship

    f325d4a1da8b42acd533973b90ac3288-huge-im
  • Alex Wong
    Alex Wong ✭✭✭✭✭
    Ninth Anniversary Facilitator 4 Name Dropper Photogenic

    @Jordan Yarr
    As for what is working vs not, check if what isn't working and what is common between them.

    I suspect the difference is between non-constituent individual relationship vs constituent individual relationship.

    constituent individual relationsihp's email may not be changeable using the individual relationship phone import, you have to use the the constituent's phone import on the constituent record that is the relationship.

Categories