Also see idea #6223. This is a major barrier for adopting web view.

There are multiple threads on this. 100 % needed for accurate and timely data entry and the ability for all users to add constituents and include the proper coding. (Volunteers and staff who are rarely in the database)

We use default sets for so many processes: speedy & consistent constituent default sets to add standard addressees/salutations from a list of many. Action default sets for regularly used actions. Relationship default sets for properly set up org contacts, spouses, so they are easily completed with relationship/reciprocal types and addressees & salutations

Consistent data entry makes our reporting cleaner and ensures that all the needed data is entered and boxes are checked (often literally!)

Default sets for addressee/salutations save so much time when adding new constituents and ensuring data consistency.

I agree this functionality is needed in Web View. It enables quicker and more consistent data entry when entering new constituents.

This is badly needed!

Default sets reduce time, data entry errors, and help us adhere to our data standard policies. They are a necessity for us for constituents, gifts and action records.

We do a lot of importing with default sets and cannot afford time to reconfigure each record for the what we need on them. PLEASE add this function.

I use this for Constituents all the time! PLEASE ADD to NXT!!!

Also see idea RENXT-I-6223. This would be very helpful.

We will also need a set of Attributes to be included in the load default when adding constituents as this is how we currently record contact preferences.