We're on Tess 15.2.27. We've just recently noticed that contributions (of any kind) are not being reported for some seemingly random constituents by Analytics.
We can create a new widget with x-Axis being the Constituent ID and no other values. Add a filter for the specific Const ID and we see the individual just fine. When we add any gift values to the widget, we see nothing, despite the constituent sometimes being a regular donor. It is as if all gifts of a few specific and highly random individuals are being filtered out completely.
I can find no unique characteristics for the impacted individuals. Neither can I find any unique characteristics in their gifts. The donors and their gifts appear to be virtually identical to others that appear normally.
The suppressed accounts are seemingly very few in number, but the problem has become noticeable over the past few days. As an example, I looked for all gifts on 2023.06.05 and found 1 gift/donor lacking. I then created a new widget to view all gifts from that specific generous donor and Analytics reports "No Results" even with an open-ended date.
I've rebuilt ALL of our cubes. The mysterious issue remains. What might we be doing wrong?
THANK YOU IN ADVANCE!
Hello, Ty. Did you ever get a response from Tessitura Support on what might be taking place?
Hi Nathaniel! I'm happy to report that we did get this resolved. I'd already forgotten about this one, but I went back to the ticket and here's how I closed it. We concluded that it was a Windows update to SQL on the Analytics server that somehow caused the issue for us.
I think we've got this solved! Your questions inspired me to go to the SiSense ElastiCube Manager to try rebuilding using "diagnostic" logging (rather than using the Web interface). There, I got an error that I didn't get on the web version. Went Googling and found a perfect match for the error and the behavior: https://community-old.sisense.com/hc/en-us/community/posts/360021537173-ExecuteReader-CommandText-Property-Has-Not-Been-Initialized
The entry in the above page suggests that rebuilding the connection without encryption was the likely solution. My guess is that this has nothing to do with encryption, but rather the act of rebuilding the connection is what did the trick. I rebuilt the connection to the existing Analytics MS Sql DB and ran the rebuild again. This time it was successful and the data is up-to-date!
Looking at Windows updates, I see installation of KB4019088 ("Critical Update for SQL Server 2016 MSVCRT Prerequisites") coincides precisely with the start of the issue. I think its a safe bet that this is the culprit! Many thanks for your help. Closing this ticket.