I've pasted this on a couple of related posts, and feel strongly about it. So here it goes, again:

The address field needs to be a required field for BBMS Forms/Online Giving!!! First of all, when the address field is not required, "Automatic Constituent Matching" is less efficient, resulting in the likelihood of creating duplicate records. There is now less criteria to match on. Secondly, not having a donor's address negatively affects fundraising strategies and data analysis (mailings, personal notes, geographic segmentation and reporting.) It's just nice to know where your donors reside. Lastly, since when does a website not require an address for an online transaction.

I'm still seeing required fields not reflected in web view so don't understand why this is marked as shipped. I've added a new idea for this, please vote for RENXT-I-8664

Coming from an org with 400+ funds, we really need to have fields like "Fund" required in Actions, Gifts, etc.

This may be noted in someone elses comments but constituency code has been selected as 'required' in NXT - which works when adding a new individual, however when adding a new organizational constituent at the present time it is not required and we're having staff forget to make a selection. Please update System Fields so that it will work for both constituent record types!

establishing required fields assists in compliance with our data entry standards, would appreciate a fix on this issue.

Records are being added into our database through RE NXT web view forms without the required fields being populated (ie addressee/salutation). This is a huge issue.

We need preferred name to be added as a required field in web view- when we create records in database view it's required but it's not an option in web view yet. This is an issue because we use the preferred name field in all of our personalized emails.

We've just made the switch to RE and I configured gift entry in DB view to make Campaign and Appeal required only to find a load of gifts without it - apparently these don't convert over to web view! I hope this is resolved soon!

Multiple required fields in congfiguration in DBV are not showing up as required in web view including: Relationship fields, fundraiser type, fundraiser reason, fundraiser dates, just to name a few. Makes it difficult at best to enforce best practice on all users which subsequently reduces the intergrity and quality of the database. I honestly can't understand why required fields in web view are selectively enforced. Makes my job as a DBA that much more complicated.

I need to make preferred name/nickname, not first name, required in web view, as it is in database view; is this possible ??

Also, this is tagged "shipped." Great. What does that even mean.

This was posted 2016 and it's eight years later. They've just completely run away with the bag of money and are laughing at this point.

This might be the last straw for us.

Worse, found out the gift object does not have CRED. This means if I want to force users to enter in database view, I can't just take away their ability to create new gifts in NXT - I would have to shut off their access to gift records entirely. So they might operate on the assumption a donor has never given, if they're used to looking at NXT and forget those records no longer appear.

That means the only solution to users not entering certain fields is regular data cheking and cleaning, re-training and causing tension with our team. That's completely asinine for a problem that has been solved for decades with a basic feature: allow required fields and have basic CRED securities.

I feel bad for Blackbaud support employees, having to constantly tell users that basic features are not there, but "you can go vote for it on this forum." How do you even justify that?

Yes - please add to gift entry so gifts can't be added with no campaign/fund/appeal, this has caused us some headaches during a recent campaign

How many votes are required for something like this to be considered please? Thank you.

Yes - please add to gift entry so gifts can't be added with no campaign/fund/appeal

Please add this to gift entry! It's a major hurdle to adoption of the NXT view!

In our database we made "Nickname/Preferred name" required: yet it is not required in webview. What does it mean that this idea has "shipped"?

How has this feature not been added yet? Or maybe it has... Does anyone have any hints?

This has not been shipped for Opportunities - only Actions

What does "Shipped" mean? I do not see this being solved or operational. Is there some detail behind Shipped - like date shipped, date anticipated, date active? It's been 10 months since last comments. Heavy sigh...