Dashboard Panel does not honor query's 'Suppress Duplicate Rows'

Options
Karl Craven 2
Karl Craven 2 ✭
Ninth Anniversary Facilitator 1 Photogenic
in Blackbaud Raiser's Edge NXT®: General Discussion
I'm trying to help our Alumni Relations team build a dashboard to help them more easily report on Alumni demographic and activity data. We're setting it up as a series of dashboard panels, each of which is linked to a 'Solicitor' query that's basically just a Constituent query with criteria but no output. The query then just returns the total number of rows, which is what is reflected on the dashboard.



However, we've realized that the number shown on the dashboard panel is not always the same as that reported by the query itself, and we figured out that this is because the dashboard does not honor the 'Suppress duplicate rows' checkbox like the query does. So, for example, our query of Alumni who have attended an Alumni event this year reports 702 unique constituents, but the dashboard shows 874, because it's counting the multiple event attendances for each Alumni who attended more than one event.



Is this something anyone else has run into? And is there a way to fix it?
Tagged:

Comments

  • Ryan Hyde
    Ryan Hyde ✭
    Tenth Anniversary Facilitator 3 Name Dropper Photogenic
    This is weird. I have never had a dashboard query module ever output anything the query itself didn't output.



    I would suggest jumping on chat support. https://www.blackbaud.com/support/needhelp.aspx
  • Emmet O'Conlon 2
    Emmet O'Conlon 2 ✭
    Ninth Anniversary Facilitator 1 Photogenic
    Very odd. I was able to replicate your error, though I don't know why it happened.



    There is a work-around, but it's inelegant. If you create a second query, and use the first one as the basis under the Query Options > Record Processing, it should report the correct, true number--or at least, it did for me when I tried it. Good luck!
  • Karl Craven 2
    Karl Craven 2 ✭
    Ninth Anniversary Facilitator 1 Photogenic
    ...
  • Karl Craven 2
    Karl Craven 2 ✭
    Ninth Anniversary Facilitator 1 Photogenic

    Emmet O'Conlon:

    Very odd. I was able to replicate your error, though I don't know why it happened.



    There is a work-around, but it's inelegant. If you create a second query, and use the first one as the basis under the Query Options > Record Processing, it should report the correct, true number--or at least, it did for me when I tried it. Good luck!

    I'll check that out, thanks!



    Edit: Yup, that worked a treat!smiley

  • Karl Craven 2
    Karl Craven 2 ✭
    Ninth Anniversary Facilitator 1 Photogenic

    Ryan Hyde:

    This is weird. I have never had a dashboard query module ever output anything the query itself didn't output.



    I would suggest jumping on chat support. https://www.blackbaud.com/support/needhelp.aspx

    Thanks. I spoke to a support rep and they were unable to find a solution that worked for me in this case. It may be an issue that I can work around whenever we upgrade to the latest version of RE, though, since an additional summary field has been added for Events.

Categories