Agreed, this should have been part of the system from the start. This is why we refuse to use the new portal yet. Why should our grantees be the test subjects. It's one thing for staff to have work arounds, but issues like this create only frustration for our grantees who are already stressed.

I am very worried about moving over to the new system if this level of functionality has to be called out to Blackbaud. This is so basic it should have been programmed as basic functionality and picked up by their own testing people.

It is basic form building functionality that there should be field validation ascertaining that fields contain correct values before submission. Blackbaud is a huge software company. This is utterly ridiculous.

Agreed! We are finding ridiculous things like fields that have a max of 50 characters that we can't change, can't show character counts, and would have to request a revision on.

The other thing I have found related to this is the 'second error' - so an application is submitted and it has an error so we cannot process it (like the character limit mentioned before), we publish it for resubmission and have the application change the field and resubmit - only for the system to show another error that did not show the first time around (like the project end date being before the project start date). Then we have to repeat the already cumbersome and frustrating process again.

This is absolutely vital. It's unacceptable to have to ask the applicant to adjust & resubmit their application because of a technical restriction on the field at our end. We cannot always see what that technical restriction is in the field.

We have noticed this so far with a standard text field that we have been using for years without problems - ie, with the legacy portal, the applicant was alerted to the fixed character restriction for that field, and so entered the correct information, but now there is no alert to the applicant and the application can be submitted. However, it is then blocked when being considered with a red alert icon). This is not a field that we have added min/max character counts in the verification tab, it seems to be an inherent characteristic of the field itself which we cannot change.

Similarly, TaxID has a restriction of 20 characters, regardless of any min/max numbers that we include on the verification tab for that field.

This seems to happen more often than not. For example, grantees can submit a project start date for 2/1/25 and and end date for 1/1/25 and the system does not catch it. Instead, we attempt to pull the report in and are blocked by the system as the end date cannot be before the start date, thus forcing us to send the report back to the grantee for revision when they should not have been allowed to submit in the first place.