This key is critical for data integrity. Used so many times to validate accuracy of address based on where it's coming from.

I see it in NXT when reviewing, but we can't edit it or add it in NXT. Adding Info source would be a big step in allowing us to add/update addresses in the webview. It is viable for not only data quality, but also data integrity particularly with sourcing as mentioned in other comments.

As Helen Lowery said, please allow us to set this field as a particular option when coming from online donations and event registrations. It would help us to flag when an incoming address might be incomplete as compared to the address that was existing on the record prior to automatically being overwritten/updated.

These fields are vital to keeping our data clean!

This is so important, and needs to be added asap, along with the Regions field as we use this to record and pull different postal areas required for our mailings

This is valuable information that helps us understand why information was added. By not having it in web view, we are losing this audit feature on hundreds if not thousands of records as addresses are updated.

This field is critical to knowing why an address was updated and with what source. If it comes automatically through an NXT form, that should be added at processing. If it's a manual change, users should be able to use the field to explain WHY they are changing the information. This is also important for Gift Aid as we need an auditable record of address changes.

This field is really needed and I hope added to the webview soon.

As is the COUNTY and I know there is a voteable option for that topic so please all, vote for that one as well! Thanks

So important!

totally agree with JohnDeMarce

Make all the Database View fields available in Web View. It's really that simple.

Documentation and transparency are critical when it comes to making data updates, and this is a piece of data that should be structured into a picklist. Omission of this field forces users to add notes and other unstructured data that is more time consuming and causes more challenges to isolate.

As we use DBV less and less to prepare for its retirement, this is important for working through mailing issues and conflicting data. Right now, our workaround is to clutter Actions or Notes with address update notes since these critical backend fields can not be viewed or added/edited in Unified View. Using this workaround is not a long-term solution and is subpar to the functionality that is in DBV.

This is key info for where address came from and reliability.

If address is from registrar at graduation, is likely now parents'. If address came from a dev staff it is more reliable than one from an online source. Want to know when it's from an NCOA update.

Needs this for effect use of address info.

This is big for us. It helps us in many ways, including integration with other databases/applications.

This is critical information and lets me know when to dig deeper on finding accurate contact information.

No “Info Source” on Addresses should be a critical issue and should be added. We need this information to understand how an address is entered into the system. This is standard good data management practices and essential for evaluating data quality. Thank you!!

Also, the fields populated NCOA are useful for additional research on the property itself.

We use this as one of the metrics to track engagement. If a constituent takes the initiative to provide this information, that's valuable information. Please add a place for this in the address section.