March 2008 Issue
Kheng Chow Consulting LLC
P. 646.522.9346
F. 646.328.3167
info@KhengChowConsulting.com
www.KhengChowConsulting.com
P. 646.522.9346
F. 646.328.3167
info@KhengChowConsulting.com
www.KhengChowConsulting.com
| DataHealth News |
TM
Why are there duplicates in my query results?
Even though you see duplicates in the results, the record is pulled into the Query
only once. The duplicates that you see can be due to fields you selected in the
Output tab of your query. Query is a very literal tool. If you created a constituent
query and then asked the system to show you their phone number in output, you
may see duplicates in the results when the constituent has more then one phone
number. This is called a one-to-many relationship. One constituent can have many
phone numbers. In addition, if you have complex criteria using “OR” operators, you
may find duplicates in the results because the same constituent record will appear as
many times as it meets the criteria set in the Criteria tab. Since Query is not a
reporting tool, use Export, Mail or Reports modules to eliminate duplicates.
Can I remove the appearance of duplicate rows in my query?
If the duplicates are displayed due to complex criteria set in the Criteria tab, you can
minimize the appearance of duplicate rows by going to “Tools” and “Query Options”
from the menu bar then navigate to the “Records Processing” tab and check off
“Suppress Duplicate Rows”.
What is the difference between a dynamic query and a static query?
Dynamic queries will automatically refresh itself by searching for new records in the
database that meet your criteria and adding it to the query results. Static queries
take a snapshot of the database the moment of the query run and results can only
be refreshed manually.
When should I use a static query?
Use static queries if you intend to use it for global changes. For example, event
invitations lists should be created as static queries so that when you are ready to
globally add the appeal to constituent records, the records grouped by the static
query will accurately reflect the constituents that were mailed the invitation. New
constituent records that later meet the invitation list criteria will not be automatically
added to the query.
How can I manually add a constituent that does not meet the query criteria into
my query results?
Use specific record under the constituent information tree in the constituent query.
This can be used to add “seed names” to direct mail lists when they do not meet any
other criteria.
Even though you see duplicates in the results, the record is pulled into the Query
only once. The duplicates that you see can be due to fields you selected in the
Output tab of your query. Query is a very literal tool. If you created a constituent
query and then asked the system to show you their phone number in output, you
may see duplicates in the results when the constituent has more then one phone
number. This is called a one-to-many relationship. One constituent can have many
phone numbers. In addition, if you have complex criteria using “OR” operators, you
may find duplicates in the results because the same constituent record will appear as
many times as it meets the criteria set in the Criteria tab. Since Query is not a
reporting tool, use Export, Mail or Reports modules to eliminate duplicates.
Can I remove the appearance of duplicate rows in my query?
If the duplicates are displayed due to complex criteria set in the Criteria tab, you can
minimize the appearance of duplicate rows by going to “Tools” and “Query Options”
from the menu bar then navigate to the “Records Processing” tab and check off
“Suppress Duplicate Rows”.
What is the difference between a dynamic query and a static query?
Dynamic queries will automatically refresh itself by searching for new records in the
database that meet your criteria and adding it to the query results. Static queries
take a snapshot of the database the moment of the query run and results can only
be refreshed manually.
When should I use a static query?
Use static queries if you intend to use it for global changes. For example, event
invitations lists should be created as static queries so that when you are ready to
globally add the appeal to constituent records, the records grouped by the static
query will accurately reflect the constituents that were mailed the invitation. New
constituent records that later meet the invitation list criteria will not be automatically
added to the query.
How can I manually add a constituent that does not meet the query criteria into
my query results?
Use specific record under the constituent information tree in the constituent query.
This can be used to add “seed names” to direct mail lists when they do not meet any
other criteria.
Query FAQs
