Make Mandatory Fields in the Database View transfer to Web View
Currently when you make a constituent record field required in the database view (for example: Action Status), it doesn't transfer that requirement over to the Web view. There's no way to make the field mandatory in the Web view either. It'd be great to either be able to make certain fields in the Web view required, or have the requirement transfer from the database view to the web view.
-
Guest
- Apr 27 2017
- Reviewed: Voting Open
Related ideas
Parity is essential regarding system-wide configurations. Fields our organization has required need to be required in both views. Lack of enforcement of these configurations results in unnecessary data maintenance to be required.
This is so important for good data! Many people have good intentions and just don't have the required fields memorized. Forcing required fields makes your data cleaner and helps people do their data entry more effectively.
Literally today I've been cleaning up half-entered relationship fields because it's not possible to make them mandatory in webview and the search box on relationships obscures the first relationship field, so they are easily missed.
We have discovered that our data is incomplete because the required field settings that we established in Raiser's Edge are not reflected in RENXT. This has caused inaccurate reports and additional work to clean up the errors in the database. The RE NXT product should not have been released if no required fields may be established to ensure data integrity! Please escalate the importance of this issue to be included in the next release.