Welcome to Good Training Sign in | Become a member - FREE!
 

Limiting mail merge to primary contact only

Last post 08-29-2008, 9:08 AM by Ben White. 4 replies.
Sort Posts:
  •  08-28-2008, 2:10 PM 1430

    Limiting mail merge to primary contact only

    I have created a group of accounts, primary contact, address, etc......

    When mail merging to a letter, all contacts from the account print as their own letter.

     I only want the primary contact to receive the letter.

    What am I doing wrong?

    Thanks,
    Jerry

  •  08-28-2008, 4:20 PM 1431 in reply to 1430

    Re: Limiting mail merge to primary contact only

    The group you are mailing to, do you have a condition of CONTACT.ISPRIMARY = 'T'?
  •  08-28-2008, 4:53 PM 1432 in reply to 1430

    Re: Limiting mail merge to primary contact only

    Jerry,

    You need to build a group of Contacts.....not accounts.

     

    Dale

  •  08-29-2008, 8:42 AM 1434 in reply to 1432

    Re: Limiting mail merge to primary contact only

    Bingo, that is the right answer.

    With some help I figured that out yesterday. I don't know why I didn't start with contacts to begin with.

    Practice and learn......

     Thanks,
    Jerry

  •  08-29-2008, 9:08 AM 1435 in reply to 1434

    Re: Limiting mail merge to primary contact only

    I always train to "show your working" for those first starting query building or those building complex groups:

    Step 1

    I want to see a list of people who are the primary person for their accounts where they are solicitable, have an email address and are either CEOs or VPs

    Step 2

    People where DNS is not equal to 'Y' and email contains '@' and (title contains 'CEO' or title contains 'VP)

    ---

    You could even take it one step further (and this is how SLX 7.5 web builds groups) by building up the columns you want to use first:

    I want to see the Primary person column with a "Y" in it, the person's firstname, lastname, email, DNS without a "Y" in it...

    --- 

    You can see not only how it helps identify exactly what conditions and operators you are going to use, but also whether you'll be needing brackets or not - Golden rule here is that if there is an AND and an OR then you will have brackets.

    Incidentally, you might notice that I have used the "DNS does not equal Y" rather than "DNS equals N" this is because often, imported data leaves it blank rather than entering an N. I have also seen data imported and the DNS (and other checkbox fields) with other things (e.g. '1' instead of a 'Y').

     

View as RSS news feed in XML