Merge Query in web view suppresses inactive automatically
I am doing merge query of two constituent queries for the first time using "OR" operator. Then from database view used export to build a list. I found that some records were not in the export of data - at first thought it would be head of house situations - but after review of some records which did not have spouses realized that inactives were being suppressed in the merge query despite being included in both of the individual original queries.
My merge query from NXT record count was 445 records (static of course).
I re-ran the same merge query in database view and saved it and the count increased to 469.
Please get this resolved so that inactives are not automatically being suppressed from merge queries.
-
Matt Haynes
- May 21 2025
- Reviewed: Voting Open
Related ideas
Suppressing inactives is not all it does. Query merges in NXT web view also exclude anyone marked as No Valid Address, which is absurd. Query merges are used for so much more than generating mailing lists. This is what the knowledgebase AI told me today:
"In NXT, when performing a query merge, records that are marked as No Valid Address will be excluded from the merge process. This is because the system is designed to filter out constituents without valid addresses to ensure that communications are sent only to those with valid contact information.
If a constituent's record has all addresses marked as not valid for mailing, the No Valid Address checkbox will be checked, leading to their exclusion from any query merges.
Yes, when performing a query merge in NXT, records that have no valid address marked will be excluded from the merge process. This is because a valid preferred address is necessary for a constituent to be included in the query results. If a record is marked as having no valid address, it will not be processed in the query merge."
Inactive records should not automatically be suppressed!