Query Export Failing with Date Fields Included

Amelia Ketzle

Multiple query exports of different types have been consistently getting errors over the past week. When Date To and Date From fields are removed, they start working again. All of the queries we had issues with were resolved when the Date To and Date From fields were removed. Does anyone know why these critical fields are not supported? Has anyone had similar experiences? Failed query exports include Address, Assigned Solicitor, Constituent Code, Fund Relationship, Individual Relationship, Non-Constituent Individual Address, Organization Relationship.

Alex Wong

@Amelia Ketzle
are you talking about using database view Query to export, or Export to export?

Alex Wong

@Amelia Ketzle
I just tried Query to export

constituent query, constituent code from date not blank and output the code, from and to date, no problem.

maybe a few screenshot will help and the error message

Christine Robertson

@Amelia Ketzle Do you have any of the wordings from the error messages that you're seeing? That might help.

Lee Grisham

@Amelia Ketzle have you checked if those Date fields have to do with Birthdates? I think I remember when they encrypted those fields that they would fail depending on what information was used in those filters.

Amelia Ketzle

@Lee Grisham - No, they were start and stop dates, I believe. Date To and Date From in Addresses, for example.

Amelia Ketzle

@Alex Wong - I'm talking about running existing queries (from db view) in web view query. They've been working fine and all of a sudden they went kaput. But, then all of a sudden, they started working again yesterday.

Amelia Ketzle

@Alex Wong - And sorry, exporting directly from the query, not using Export.

Amelia Ketzle

@Amelia Ketzle - This issue self-resolved yesterday. We don't know what changed, but it's working now, so I can't replicate the error message. I'll revisit this post if it happens again. THanks to everyone for your efforts to help!