nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Excluding "Do Not Solicit" Codes From Query Help

Dylan Medina

Hello

I'm working on preparing a mailing with quite a few criteria. In the past I've always added the excluded solicit codes as “And Not One Of…” as one of the last parts of the query. I'm noticing this isn't always accurate. Is there a better way to exclude these constituents?

Find more posts tagged with

Comments

Laura Neidhold

@Dylan Medina Probably not the exact answer your looking for - but I also use “and not one of” on my query and then in my export I include a solicit code section to catch any that snuck through to manually remove. One in excel I filter on the ones I need to remove and manually delete.

Don Burrhus

@Dylan Medina I find that ‘wrapping’ queries with the overarching criteria helps. Parenthesis are my friends. In other words, like:

Key Indicator is one of Individual
And Deceased equals No
And (
[the 'meat' of the query goes here]
)
And Solicit Code is not one of Yadda, ANC, DNS

Doing this ensures that the solicit codes are applied only at the outermost layer.

Irene Hui

@Dylan Medina I sometimes merge the queries using the SUB operator, where the secondary query has the solicit codes. I can confirm that the excluded solicit code are not included when I use export to produce the output.

Austen Brown

@Irene Hui:
@Dylan Medina I sometimes merge the queries using the SUB operator, where the secondary query has the solicit codes. I can confirm that the excluded solicit code are not included when I use export to produce the output.

Second this! I also go the route of utilizing the merge query options. Here's a KB article that explains merge query operators with diagrams that are super helpful when starting out: