Query Output of Consecutive Years Giving field

Is there still the bug preventing the Consecutive Years Giving summary field from being output in a query? Or has this been resolved?

Answers

  • Alex Wong
    Alex Wong Community All-Star
    Tenth Anniversary Facilitator 5 Kudos 5 bbcon 2025 Attendee Badge

    what was the bug?

    I am able to create a constituent query > criteria on summary of gift - Consecutive years of giving, output constituent id and the consecutive year giving field with no problem

  • The issue appears to be with database view, since I was able to get it to work with web view.

    I'm not sure if this will work if I try to using Queue to get the query output file.

    Thanks Alex.

  • Alex Wong
    Alex Wong Community All-Star
    Tenth Anniversary Facilitator 5 Kudos 5 bbcon 2025 Attendee Badge

    Since you are already doing Power Automate, no reason to use Queue, just use PA to run the query get the export to save to a cloud storage

  • Just to clarify, if other people are reading this, the results are produced much quicker in web view than DBV. In fact, having CYG in the query output in database view is so slow that it seems to hang up.

  • I had the opposite problem - a query with only CYG parameters and only one or two output fields (Con ID, name) would never complete in web view, but in DBV it would complete and show that there were about 300 records. I submitted a ticket and was given a 'some queries are not suitable for web view' response and no other support.

    I'm curious if your queries were for more specific or smaller subsets of data, or with fewer results?

  • I tested this with criteria to have results for 1 record, which had DBV "thinking" while calculating the consecutive years, whereas WV gave an answer right away.

    I thought there was an issue at one point with the CYG field.

    So, I haven't tested the results with a large number of records.

  • Alex Wong
    Alex Wong Community All-Star
    Tenth Anniversary Facilitator 5 Kudos 5 bbcon 2025 Attendee Badge

    i did the test with consecutive year of giving >= 5 with subcriteria of one-time gift only, output is Constituent ID and the consecurive year of giving field, we have 15K+ results and took less than 10s

    image.png image.png image.png

    @Robin Kuehn please provide the support ticket #, I think your support rep answer is not proper, @Crystal Bruce if the support from BB is indeed saying "some queries are not suitable for web view", then we will need to know what BB defines as what is not suitable for web view and this answer does not align with BB vision of Total Web Solution.

  • @Alex Wong My query did not exclude recurring gifts, so that may have been part of why it got bogged down.
    This conversation was in the first half of the discussion under support ticket #020740083 back in February. I received the following:

    "You can generally use queries in both the Raiser’s Edge database view and the web view, as the system keeps them synchronized between the two interfaces. However, there may be times when a specific query or functionality works in one view but not the other. This is due to differences in design, supported features, and the intended purpose of each view."

    And later:

    "I totally get that may be inconvenience not being able to create that query in WebView, sometimes the system in WebView fails when the query is too complex or large, however, I can assure our team is working on that to resolve this issue in future updates. "

    Perhaps the future updates have happened, but I haven't wanted to put time into this since.

  • Similar Post:

    Support had no knowledge of what the "Job ID" meant or how to help with that. Doesn't always happen to me, but I haven't been able to test it with the API like @Alex Wong mentioned in that post. I can get it to work in database. It was a list from a Retention dashboard, which is hard to replicate…

Categories