Merge queries

Options
Tess Marino
Tess Marino ✭
Tenth Anniversary Photogenic First Reply
in Blackbaud Raiser's Edge NXT®: General Discussion
 I can't seem to keep all my merge queries straight. What would be a good practice in keeping everything a little more tidy? Any suggestions would be helpful. 

 
Tagged:

Comments

  • JoAnn Strommen
    JoAnn Strommen ✭✭✭✭✭
    Ancient Membership Facilitator 4 Name Dropper Photogenic
    Don't know what you're doing now but suggestions:
    • utilize folders - my 'filing' is based on subject of query
    • Write good query names
    • Write good query descriptions
    With clear names and descriptions it's easier to see what is in the query and/or merge query.
  • Gina Gerhard
    Gina Gerhard ✭
    Ancient Membership Facilitator 3 Photogenic
    You may already do this, but I usually try to use a naming convention that keeps the components together:
    • xxxxxx - Part 1
    • xxxxxx - Part 2
    • xxxxxx - Takeouts
    • xxxxxx - MERGED Part 1+2
    • xxxxxx - MERGED Part 1+2 sub Takeouts (or a rough description of what you're doing in your merge)

    This has helped me keep the components grouped together so you can sort of see what you've done (in addition to good notes!). If someone else has to step in, they can see the pieces grouped together.



    And then I tend to delete the MERGED queries since I have the components (which are dynamic) instead of being left with a MERGED (static) query which can be tricky if you don't refresh correctly.  
  • Tess Marino
    Tess Marino ✭
    Tenth Anniversary Photogenic First Reply

    JoAnn Strommen:

    Don't know what you're doing now but suggestions:

    • utilize folders - my 'filing' is based on subject of query
    • Write good query names
    • Write good query descriptions
    With clear names and descriptions it's easier to see what is in the query and/or merge query.

     

    Thanks for the good tips.
  • Tess Marino
    Tess Marino ✭
    Tenth Anniversary Photogenic First Reply

    Gina Gerhard:

    You may already do this, but I usually try to use a naming convention that keeps the components together:

    • xxxxxx - Part 1
    • xxxxxx - Part 2
    • xxxxxx - Takeouts
    • xxxxxx - MERGED Part 1+2
    • xxxxxx - MERGED Part 1+2 sub Takeouts (or a rough description of what you're doing in your merge)

    This has helped me keep the components grouped together so you can sort of see what you've done (in addition to good notes!). If someone else has to step in, they can see the pieces grouped together.



    And then I tend to delete the MERGED queries since I have the components (which are dynamic) instead of being left with a MERGED (static) query which can be tricky if you don't refresh correctly.  

     

    Thanks for the good tips! 
  • Nicole S
    Nicole S ✭
    Ancient Membership Facilitator 3 Name Dropper Photogenic
    Helpful reminder -- I've seen a lot of people forget to change the descriptions after they change the criteria.  This is primarliy a problem in dynamic rather than static queries like merged queries.  But these organizations tips you've received from JoAnn  are actually good for ALL queries.

Categories