FENXT Query Issues

Gideon Buckle

We’re experiencing worsening symptoms of system unreliability across the platform. The situation is dire.

Queries that we have used for YEARS are now providing inaccurate results with increasing frequency. Determining this is easy when a data set is small; it’s impossible to do with larger data sets. Writing a new query provides accurate results in at least one instance I’ve tested, but this an absurd solution. For Blackbaud to expect that we rewrite our entire library of queries to ensure that things are working correctly is incredibly arrogant and reflects a stunning lack of respect for customers’ time.

In addition to the observed and reported problem with queries, we are now also experiencing similar issues with post parameters. Earlier today, I repeatedly tried to post a range of open bank deposits using a filter in the post parameter I've used for this task for many years. Repeatedly, the system popup indicated that there were no transactions to validate - which was incorrect. I wrote a new post parameter and was able to post the transactions, but again - the only way I knew that the “no transactions” popup was inaccurate was because the data set was small.

This presents a huge internal control issue and is profoundly concerning. It’s simply not possible to responsibly manage our finances with a broken financial accounting platform.

Anyone else running into this issue?