We use defaults to add addressee/salutations and 3 account attributes (custom fields) at one time. Saves a lot of clicking, searching and confusion for end users!

This is a must! Our data entry team hasn't moved to add new constituents in webview yet for this reason. Hopefully it's in the works!

I use this all the time in database view. We have specific information that we add to all new donors. When they make their first gift through the online donation form and NXT automatically creates a record for them, I have to then go into database view and load the defaults to the record. As database view goes away, it will be very important for us to be able to have this functionality directly in NXT. We do not want to have to go into each new constituent and click around to find all the fields (especially since there is no longer simply the Bio 1 and Bio 2 tab and you have to go into different parts of the record to change the name, name format, constituent code, etc.). Having the ability to simply load a default that has the correct information is definitely needed.

Defaults are vital to keeping data clean and accurate rather than having to click into various tiles to complete different tasks. Much information will be missed along the way.

See also RENXT-I-8568 which is similar to this idea.

A couple of use cases for constituent default sets:

• Constituents were added and are missing both the organization's primary and custom addressee and salutations. Default sets for these salutations, but single and married couples are easily applied to the standard forms on a one-off basis during gift entry or general constituent work.

• A constituent is being added for a new employee at the organization: A default set is applied to add standard addressee/salutations, constituent codes, email type, and attributes/custom fields that are used for employees. This prevents data entry errors and standardizes many of the data points that are tracked for employees.

This function was vital when we went through a hug addressee/sals update at my last school. It was my only option to mass change this kind of data. I still had to manually enter the primary addressee/sal because it didn't override those, but it did the other 5-6 per record for me. Say a single class of students is 300 people - that's over 1,800 manual edits I was saved by this function. This is a function that can really make some impossible lifts possible.

When then are added - and I'm trusting they will be as they are so important I would love to be able to sort them. Currently they can only be listed in the order they are created. While I have most of my addr/sal default sets next to each other some other needs have come up of the years where I have needed to add more. While I would love parity, this would be an improvement - and another time saver for those that don't use the defaults every day like I do.

This is very helpful and something our staff use in DB view. Not having it in web view would be an unfortunate loss.

This is extremely helpful with addressee/sals. Great for consistency and less errors.