Agree, this is much needed along with the important data management fields of Date From, Date To, Region Code and Source.

To NOT roll this out in webview is short-sighted. It is absolutely best practice to preserve address history and I have relied on it many, many times to merge duplicate records, prevent old addresses from resurfacing, and clarify other mailing list concerns.

Because this is tagged as "Reviewed: need further info", I'm curious to know what further info is desired? If there are specific questions that need answers, I'm sure the community would be happy to provide!

I agree, that we need to be able to do this in NXT. If this is added, we do need to be able to restrict access so everyone does not have the ability to update address information in NXT like what we can do in database view now. At our organization, there are only a few of us that can update address/contact information.

Ron, The request is for a function in NXT that is similar to the the function in the database view for Copy Preferred Address to Alternate. I use this function when we have a new address. I doubt many users use this function just to make a simple edit or correction to an address.

I have a report built on the Date to and the Address type of the former address, which is automatically populated from the "Copy preferred address to alternate". When there are multiple steps in NXT to do the same thing, there is more room for human error. 

Yes, you can manually achieve the same as 'copy address to alt', but as Drew mentioned, this falls down for shared addresses.  Response from my customer success manager about it, indicating better workflow coming:

It’s the same sort of process, but without the one click option to copy to alternate (yet 😊)

You would need to:

1. Copy (manually) the old address and add it as a “new” address (with the type of “former”, or similar), then
2. Overwrite the original address record, at which point RE NXT will ask you if you want to change it for all records who share that address.

I guess I don't understand why you need further information. 

If someone goes into an address and updates it in NXT, the previous address is lost....which is why we make all address changed in database side of RE, to keep history.  We keep the history of addresses because we frequently are told a person's address and in looking in the history of addresses, the address we've just been given is really an old address.  As we are going through this process now with reconciling addresses in Core with RE.  Our Core addresses in some cases, had not been updated in several years, while the RE address has been kept up.  If we didn't save address history in RE database version, we'd keep entering the same incorrect information by putting in the old address, because we could not see the history of addresses.  Why the is the history automatically kept in Core profile changes but not in RE.  Or is there a way to see address change history of address changes made in NXT that I have missed?  Thank you.

Becky - I am trying to understand the scenario. I think this is for "I found out Robert Hernandez has moved and has a new preferred address", not a simple edit. I think this is just an ask for some replacement of the "Copy Preferred Address to Alternate".

In RE7 that copy feature lets you take "Address Record X" and create a copy of it "Address Record X(1)" (essentially, kept for history), then you edit "Address Record X" to make it "Address Record Y" and preferred. In web view, you can simply add Address Record Y, mark it as preferred, and you've achieved the same end. So, I am guessing there is some more subtle nuance to this request.

If I am reading the suggestion, it says that RE NXT over-writes the current address, therefore there would be no 'old' address to put an end date on.

To the Admin,  are you saying NXT automatically copies the preferred address to alternate without manually doing it? 

If by "change" you mean the constituent has moved and we need a new address: If this is the case, the expectation would be to just add the new address, mark it primary, then go to the old address and put a valid end date on it. This preserves the address history.

If by "change" you mean there is a typo on the address and we need to fix it: Is this just an ask for audit trail info to know who last edited an address?

Please clarify. Thanks!

Additionally - need the function (like in database view) to make the change on all shared addresses. This is important when updating the primary address for an organization and the business address for all of the contacts (that share the org primary) needs to change as well.