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...

Do you know how hard it is to report on Opportunities by fundraiser when fundraiser isn't a required field in NXT? It is required in database view along with all the other fields that drive our reporting - but not in NXT where ALL our gift officers work. This is a monthly nightmare of a clean up especially when reporting on Opportunities is utterly challenging in an of itself.

Thank goodness it's not just me. This is such a problem for us. Plus continually having to explain this to my team is exhausting....

Agree - this needs to be consistent all over the database. This is also happening with gifts recorded in NXT. There are fields that are required in database view that don't even appear on NXT. The security settings in DBV should reflect accordingly in WBV.

This has only been "Shipped" for Actions. It needs to happen for Opportunity Fields. Please provide an update on the status of that. Thanks!

Hi Ron,

If you are still accepting early adopters, please also include me joelle@foodbankscanada.ca

Thanks,

Joelle

Any updates on this?

Hi Ron, if you are still accepting requests fro EAP, please add CSUF.

sanatt@fullerton.edu.

Yeah, this feature would be nice to have now.  With our current processes, we use the required attributes fields to be entered in actions Actions.  It's quite silly that you can only make required attributes in the database view, and not in the Webview.