Global Change/Import?

Tess Hirschkorn

In the process of updating our addressee/salutation types. I updated the “nickname” field to “preferred” and am making this a required field. I successfully did this with all the constituents, but am struggling with how to implement this change for the non-constituent relationships. How do I pull the (non-constituent) records with a blank nickname/preferred field, copy the first name to this field, and then import them back into the database?

Joe Moretti 3

@Tess Hirschkorn Why would you change the nickname field, which is a field used for nicknames, which many people do have? And if you wanted to do a preferred name, why not use one of the additional addressees. I would not want the nickname field changed like that. Tp me it sounds like a lot of work to do and if you leave, the next person to take over would wonder why was that even done, I know I would.

Alex Wong

@Joe Moretti
I think she's just aligning the webview's field name with database view.

database view nickname = webview preferred name

so she is just renaming the field name in database view from nickname to preferred name.

@Tess Hirschkorn you can use a relationship query to query on the relationship's nickname being blank and this individual is a constituent=no and get the import id needed to do an import to make the change

JoAnn Strommen

@Joe Moretti I read Tess's post differently. I think she did what we recently did: changed the display name of the field in db view from “Nickname” to “Preferred Name.” This is the name used for the field in web view and made conversations about names a bit clearer.

I did not see that she was removing it. I'm working on an add/sal clean up project and have to have nickname/preferred name field filled for relationships as well. The smart function in formatting addressee/salutation does not pull in the relationship first name field when nickname is blank. It only does for the constituent from what I can find.

Tess Hirschkorn

@Alex Wong Yes, you are correct--aligning database fields with NXT. So, I have the query made but how would I go about doing a relationship import? I don't do imports all that often, and I cannot seem to figure out how this import would work!! THANKS

Alex Wong

@Tess Hirschkorn
In your output, you will need to output the Individual Relation Import ID

Using import > individual relationship import, you will use the “Update existing records option”.

You only need to map Individual Relation Import ID and Individual Relation Nickname

Joe Moretti 3

@JoAnn Strommen Again another issue between Database View and RE NXT, using different names for various items.

Tess Hirschkorn

@Alex Wong THANK YOU FOR YOUR HELP!! Just ran the import, and updated 18,000+ records

Alex Wong

@Tess Hirschkorn
Great, good to hear.

By the way, please help the community out by marking reply that has help you come to an answer to your original problem. Reply marked as Answer will come up to the top so others who have same question in future and got to your post can quickly see the post that will resolve the issue.

Catherine Burns

@Joe Moretti
Also if you are sending emails from web view then the Salutation fields are not available as merge fields but Preferred Name is. So if you want to use NXT emails you need a workaround like this. Of course if Salutation was available as a merge field this would not be required and the nickname/preferred name field could be used just for nicknames.

The risk of this work around is that if a person changes their name e.g. corrects spelling, the Preferred name field needs to be manually updated but Salutation updates automatically.

Please vote for https://renxt.ideas.aha.io/ideas/RENXT-I-2285