Please advise of update on when fields in NXT will be updated to reflect the required fields in the database view. 

Admins: This is idea corresponds with idea RENXT-I-405.  Can we please get an update and an ETA on this?  As of 11/9/2017, Trit said this was being planned.  In idea RENXT-I-405, on 1/1/2018, she said it was targeted for Q1.  Presumably, that meant Q1 of 2018.  We are now about to roll into Q3 of 2019. 

I'm not sure about everyone else, but I'm increasingly panicking over the fact that NXT users are adding records with incomplete data to the system.

Any updates on this?? I agree with others that 18 months of "planned" is way too long! Really tough on admins that we have to work back and forth constantly.  The inability to have required fields is an epic fail. When will this be added?

Could someone at Blackbaud please provide an update? This idea was changed to planned in October of 2017 and it is now the middle of 2019. All required fields on the database side should translate over to NXT.

RE NXT should never have been released with the ability to input without the ability to establish required fields!  This is pure negligence by Blackbaud to allow this to continue when they have known about the issue for years!  All RE NXT trainers should be required to mention this deficiency in all RE NXT training sessions immediately.

Unless and until you engineers can get the required fields implemented in webview as we have in database view we will never work with NXT other than to passively look at data. We still cannot enter constituents or gifts. This is almost a joke, waiting over 4 years for this system to function. As of last week we can't enter any gifts unless we leave off the letter. Yikes. You need to hire some help with the money we are paying you! Please get this going.

Any update on this from NXT?

Any update on when this will be changed?  Required fields are very important for ensuring accurate and consistent data.

Surely all fields that are mandatory\required fields should be the same regardless of which view you are using otherwise it creates inconsistencies!  The whole point of having a "Mandatory" field is to ensure data is in uniform format! Can someone please update when we can expect this functionality to be available on NXT!

I'll second Sarah S-B on this.  We need this ASAP.  Can someone from Blackbaud please give us an ETA on when this might be available?  Someone from support chat actually told me that I should restrict my development staff from being able to add new constituents in the web view and make them do their entry only in database view.  That's not an option.  That would kill any confidence they have in the web view (and me!).

Just adding another voice into this - it costs so much extra time trying to clean up our data because NXT doesn't honour the required fields that we have in Database View. This is an update that needs to happen ASAP. 

I agree, my job is infinitely much more difficult without the ability to have required fields in NXT.  Especially since I'm the only database administrator and support manager for 156,000 constituents!

In our organisations we have a business rule that each constituent should have a constituency code. Database view does not allow you to save a record without, NXT does. This is creating so many issues with data integrity!

Any updates???  This is wreaking havoc with being able to keep my data clean.....

Yes, please add this soon.  I'm having to do so much more cleanup and management.

I know this is planned but I just wanted to add that I'd like the required fields to be kept throughout NXT.  We have required fields in our Proposals and need to keep them required in Opportunities too.

Hi there,

We are planning to add this functionality.  I'll provide updates on timing as we learn more.  

Thanks!

Trit

Product Management