Error in Webview Query

Options
Maya Rosman 3
Maya Rosman 3 ✭
Sixth Anniversary Facilitator 1 Name Dropper Photogenic
in EAP for Query in Blackbaud Raiser's Edge NXT®

Hi David and team. I just went to run a query I only run this time of year in webview and it will not run there. When I try, it gives me this error message with a little red triangle w/ an exclaimation point in it near the bottom of the screen:

“The compare_type must be None for the first filter field, and And or Or for all others.”

I'm not sure what that means. This query does have a summary field in the criteria (amount of gifts). The query is titled “Holiday Mailing - Gifts Since Last Run”.

This query runs without any issues in database view, so I'm guessing this is just an new bug having to do with summary fields working in webview now. Please let mek now if you need any additional information from me!

Comments

  • David Springer
    David Springer Blackbaud Employee
    Tenth Anniversary Facilitator 2 Name Dropper Photogenic

    @Maya Rosman, thanks for letting me know! I filed a bug for it and we'll look into it.

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer Thank you so much!

  • David Springer
    David Springer Blackbaud Employee
    Tenth Anniversary Facilitator 2 Name Dropper Photogenic

    @Maya Rosman, - is the query named "Holiday Mailing - Gifts Since List Run" rather than "Holiday Mailing - Gifts Since Last Run"?

    Just confirming since we don't see the latter in your environment.

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer Huh. That is a typo I never noticed before. You are correct. I apparently titled it “Gifts since List Run” when I meant to title it Last Run. I've been using this query for 4 years without noticing that! I'll fix the name when you're done testing it!

  • David Springer
    David Springer Blackbaud Employee
    Tenth Anniversary Facilitator 2 Name Dropper Photogenic

    @Maya Rosman, looks like this query is corrupt in both web view and DBV. For some reason one of the criteria is missing the AND/OR:

    632d36592ff55e5ceb0dbb8d5b58ce52-huge-im

    This still completes in DBV, which seems to be because DBV defaults to AND.

    If you go into the query and toggle AND/OR to select the correct value, it should complete.

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer
    Hi David, I'm not sure that this is corruption. When you add filters within a summary field, the primary summary criteria (AND total amount of gifts greater than or equal to $500) gets the AND, and then the first summary field filter never does in database view. I toggled the top level “AND Total Amount of gifts” and from Or and then back to And and ran the query. This time it appeared to run (instead of erroring out immediately), but now I get that same error message in the Results tab. "The compare_type must be None for the first filter field, and And or Or for all the others.

    I went into the Summary field filter area to try to add an AND to the Gift Date between node, but it is greyed out and I am not able to select it at all.

    ee1f8161f2cf746d468def0c3a825696-huge-im

    So, if that was where I supposed to toggle And/Or, then it is not possible for me to do so in webview.

    Again, the first filter field selected in a summary criteria in webview never includes operators, so I don't think this is corruption. I think it's webview making different assumptions than database view.

    Let me know if there's something else I can try to resolve this.

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer

    I just tested this out and a different query with summary criteria does appear to run: “Holiday Mailing Initial List (2024)”. However, the summary criteria does look the same with the first filter NOT having an operator before it and it runs without error:

    754e25dd469b0d9639531b9c5566fddf-huge-im

    When I go into this summary field, it also has the And/Or greyed out for the first criteria.

    So I think something else must be going on that is causing the other query to fail.

  • David Springer
    David Springer Blackbaud Employee
    Tenth Anniversary Facilitator 2 Name Dropper Photogenic

    @Maya Rosman, the first field in a query (or a summary field) will always be missing the AND/OR. It's the one I pointed out in my screen shot that's the problem - the 4th row - that should have an AND/OR.

    Are you able to add it to that one? If you do, does it run?

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer when I look at it, it is not missing. Yesterday the first thing I did was go to that node and toggle the AND/OR and run it. That was when the behavior changed from showing an error on the criteria tab after I hit run, to going to the results tab and then instead of loading the results, showing the same error. I did not save anything in the query yesterday after I hit the error again and this is what I see when I look at it:

    a7977eb48d6058010ddc402780a12dc1-huge-im

    As you can see, the AND is there for me. I just tested it again by toggling the operator from And to Or and back to And and I'm seeing the same thing as yesterday. It lets me run the query, but instead of loading results in criteria, it just throws the same error there instead.

    f560fbf502040419e5b2c795c7de79c9-huge-im



    Would you like me to try something else?

  • Maya Rosman 3
    Maya Rosman 3 ✭
    Sixth Anniversary Facilitator 1 Name Dropper Photogenic

    @David Springer, I'm just checking in again on this. It's still hitting that error when I try to run it. Is there anything else I can be trying here?

  • David Springer
    David Springer Blackbaud Employee
    Tenth Anniversary Facilitator 2 Name Dropper Photogenic

    @Maya Rosman, Apologies for forgetting to follow up… I've refiled the defect with my team and I'll let you know what I hear back. I suspect a data specific issue, just not resolved quite the same way we expected.

Categories