Batch Consider not functioning properly

Kayte Wisor

We had an unfortunate experience during our current grant cycle, which we haven't experienced before, but I believe is due to a change that Blackbaud made since our last grant cycle (in early February).

When we batch considered applications from Pending (we have 85 applications this quarter, so it's helpful to batch them), the organization fields did not properly update in our Blueprint fields, and in fact populated with old data from previous application responses over the past 5-10 years in some cases. Very strange!

We are working with support, and ended up having to delete all of the requests and reconsider one by one, as well as -re-upload the documents again. Not a good use of our time at all, so I just wanted to warn others about this experience. I'll update if I hear anything else from support. (Current response from BB is: There is some issue with batch consideration where the org record fields are not updated consistently when you select "Update the existing record with selected fields from the application.)

Crystal Bruce

Hi @Kayte Wisor - I'm sorry to hear about your experience with the batch updates. I'm glad to see you are working with support and I appreciate you coming into the community to let others know. If you want to PM your support case, I can keep an eye on it. Thanks!

Audrey Kidwell

@Kayte Wisor We have had this issue too! It seems to only effect certain applications which is making more work for me to double check them all!

Jen Hammerstrom

@Kayte Wisor @Audrey Kidwell

We have been experiencing this issue since early March.

At this point I do not use the option to update fields during the "consider" process, I am now checking each application and manually updating as needed. When support asked me the other day if I was still experiencing issues, I replied with, "Until I know this is fixed, I am doing everything manually." Far from ideal, but, for me, it is faster to check each manually as I go.