nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Field Errors with new application?

Sally Kalra

We successfully considered a handful of test applications in the new portal before we started getting a “Field Error” message. We are now unable to consider any new applications! The field named in the error is NOT even on the application! It is a custom field that the applicants do not see, and do not fill out. Anyone else experiencing this? We created a couple of versions of the application and all have the same problem. Any suggestions?

Find more posts tagged with

Comments

Monica Jordan

Hi @Sally Kalra! What field is the error on? If you click the triangle you will see where the issue is.

I also had several issues with field errors. In my experience, one issue stemmed from restrictions on the field from Blueprint that didn't transfer to the new portal. For example, a text field that when viewed in the new portal, I could change the max number of characters, but when I went back to the source → the actual field in Blueprint, the max # was unchanged. Compounding the issue is the fact that this limitation wasn't visible and didn't create an error for the applicant, so they could submit the application, but the grant request was left in limbo since I couldn't consider it. Once you know where the issue is, you can send the request back to the applicant for resubmission (tell them what to change).

You mention the field isn't visible to the applicant, if you imported forms, the hidden field may be on the form. I have hidden fields that help sort the requests for me.

Good luck and please let us know what you find

Sally Kalra

@Monica Jordan
Thank you for your response. I feel like the issues must be related, although in our case, the Field Error is related to a custom field within the organization record, that is not even on the application form. Where did you find the hidden fields? I do not believe we have any.

Monica Jordan

@Sally Kalra when you click on the triangle, you should see the field containing the error. Once you know the field name, go to your form and type the field in the Form Builder, and click “Currently on Form” and the system will take you to the field

Sally Kalra

@Monica Jordan
Thanks! I searched the Form Builder for what's "Currently on Form" and the field does not come up as being on the form. It does come up under Capture “Applicant Responses.” I think that just means it's an available field?

Monica Jordan

@Sally Kalra Unfortunately, that's beyond my level You'll have to engage the experts by submitting a ticket! Sorry I couldn't help!

Sally Kalra

@Monica Jordan
Thank you, Monica. I truly appreciate your input and suggestions. I have opened a case and am just waiting for answers.

Maryann Jusino

@Sally Kalra I am getting an error on my tests as well my error is 1712909 Indvidual Req Org ID is missing. This is a field we are not using and is not on our application. I am not sure if it is the same field you are referring to but I am clueless how to get around it.

Sally Kalra

@Maryann Jusino Our field error was caused by a different field, but we did get the issue resolved by the Blackbaud experts. If you are familiar with Blueprint, go into the Fields Library and make sure the field is not marked as ‘required.’ If you are unsure, it may be best to open a case with Blackbaud. Good luck!