Blank line in query list that can not be deleted

Options
JoAnn Strommen
JoAnn Strommen ✭✭✭✭✭
Ancient Membership Facilitator 4 Name Dropper Photogenic
in Blackbaud Raiser's Edge NXT®: General Discussion
Has any one encountered and figured out a solution? I took a query of prospects for one of our branch Y's and pulled it in to make a query list so that I could edit it. When I pulled it in I had a totally blank record line. I tried to delete it but it would not delete. No error message just stayed in the query list. I went back to the original query to see if I could tell what record was causing it. Seems to be the record immediately preceding it in the QL. I tried deleting that record. Doesn't delete. 


Wouldn't have been a big deal as I could edit the record out after I did the Export but it would not let me save the QL. I tried multiple times and just kept getting an error message. Searched the error message in KB and solution was for this problem happing when using Export. Not where I was at.


Finally had to give up and go back and just do more editing than I wanted to in original query. QL shows on my list of queries now but says it contains 0 records. And zero is what is there when I open it.


Anyone else run into this? Solution?
Tagged:

Comments

  • Steven Cinquegrana 2
    Steven Cinquegrana 2 ✭
    Ninth Anniversary Facilitator 3 Name Dropper Photogenic
    Hi JoAnn,


    This sounds similar to an issue we've experienced when pulling Query results using the RE API. Occasionally, there is a single blank row - as in, completely blank, as you describe - and it's usually the last row. Very occasionally, the blank row will appear further up in the recordset and very, very occasionally, there will be more than one.


    But when the Query is run and results displayed, no blank rows are shown. (We haven't investigated using Query Lists.)


    We've never been able to determine the cause of this, nor to replicate it intentionally, even by recreating the errant Query. So in our integrations, we simply detect and forget these rows if they occur as they don't seem to actually be part of the intended recordset.


    If you can consistently recreate the cause, please do advise as I'd love to find out what's going on here.


    Cheers,

    Steve Cinquegrana | CEO and Principal Developer | Protégé Solutions

     

Categories