Why haven’t all the votes from the duplicate Ideas been combined to give a true count of the number of votes for this?!

One of the hurdles to adopting RE NXT, if you're used to the database view, is the lack of data entry controls. If a field is marked as "required" in the database view, it should be required in NXT.

Any update on when this feature will be added? It's very frustrating to hound fundraisers in web view to do this when it's mandatory required in database view but they don't use that view.

@Ken Cantu, can we get an update on whether this is moving up the priority list? Any chance you can give it another nudge?

As a gift officer I do not want, nor have the time, to do some entries in NXT and the database

We should include the 505+ votes from the previous Idea(s). It is obvious to eveyone in Community and on the Idea Banks (all of them) that this is a huge issue for users. Let's make it happen!

The fact that this hasn't happened is bad enough and then on top of it there's the inefficient process of having to ferret out duplicate Ideas, put time and energy into indentifying them all, voting for them all, adding notes to them all & then lobbying for people to voe for them all just makes it over the top frustrating! I worked so hard to get the votes up and now were back down to 105!

The number of votes is misleading. When this was part of RENXT-I-405 it had 490 votes asking to make required fields consistent across platforms. It is marked as shipped but apparently only the portion that relates to actions and not all the requests and comments about opportunities. Now required fields for Opportunities has a new idea and we are back at 87 votes.

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 before we can begin reporting.

I don't know if Idea Bank can get any more convoluted or complicated but maybe, yes it can.

Thanks for providing the update. This is dissapointing to here , though because as mentioned gift officers are responsible for entering Opportunities, but because we can't have required fields that were easily managed in the database, officers too often save in complete Opporunities. They don't want to go back to using the database to enter their Opportunities & I don't want them to do that either. It is great that they prefer the webview for their work. I am stunned that this Idea has just 74 votes. I know there are many orgs out there that struggle with this same issue.

Hi Rene and all, this isn't on the current near term roadmap to deliver but required fields in multiple areas has been something we've been talking about recently to evaluate and bring in if we have capacity that free's up soon. If we make change to add it to the roadmap we'll be mentioning it in the product update briefings (PUBs) in spring and fall.

Any progress? Please update. Our gift officers continue to forget to enter fields that are required for regular reporting. We need to be able to make more Opportunity fields required just as they are set in the database view. Our gift officers are using RENXT Web view, & we want them too! Please create the option to configure required Opportunity Fields. Please!

Any progress on this?

Agreed with the comments posted already. This is needed urgently!

Required fields are essential to enable us to report accurately.  We have 20+ gift officers entering their own Opportunities and we need to be able to rely on the data without having to review/correct/push back.  

THANK YOU!

This is a much needed fix! Appreciate that required fields are coming over for Actions now. Please make the fix for Opportunities too! Thanks!