Contribution frequency

Can you share the setup for these elements?

--Tom


On Wed, Feb 24, 2016 at 12:02 AM, Phil Petch wrote:

Thanks for your reply Matthew, and you've suggested what I thought would be the most likely solution to this problem. Just to clarify, your custom criteria "lifetime number of gifts" and "number of gifts to an individual campaign" function as a measure against constituents? So you can pull a list utilising your custom output which details constituents and their lifetime # of gifts and/or # of gifts to a campaign? That's cool.
From: Matthew Echert
Sent: 2/23/2016 1:18:06 PM

I don't know of reports, but a custom output set element might do the trick for you. We have lifetime number of gifts and number of gifts to an individual campaign.



This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Development Forum. You may reply to this message to post to the Development forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Of course, always happy to share. On our system these run on a custom local view that takes soft credits into account, but configured as below they should run fine on the default contribution table, (which does not reflect soft credits!)

Lifetime Number of Gifts

In T_QUERY_ELEMENT:

 

• Description: Contribution Lifetime # of Gifts (or named however you please)
• Category: Contribution
• Data Select: count(ref_no)
• Data From: vs_contribution
• Data Where: cont_amt > 0
• Single Row: (checked) 

 

Number of Gifts by Campaign

In T_QUERY_ELEMENT_PARAMETER:

 

• Description: Campaign
• Data Type: String
• Multi Select: (checked)
• Ref Tbl: vs_campaign
• Ref Id: campaign_no
• Ref Desc: description
• Ref Sort: description

 

In T_QUERY_ELEMENT:

• Description: Contribution # of Gifts by Cpg (or named however you please)
• Category: Contribution
• Data Select: count(ref_no)
• Data From: vs_contribution
• Data Where: campaign_no in (<<p7>>) AND cont_amt > 0
• ....except replace the 7 in <<p7>> above with the id # of the "Campaign" parameter you created in t_query_element_parameter
• Single Row: (checked)

 

You could use the same setup to capture number of gifts over a given date range if you made "Start Date" and "End Date" parameters in t_query_element_parameter. (Or maybe you already have those parameters set up for other output set elements.) Then in the "data where" you would put something like: cont_amt > 0 AND cont_dt between (<<p1>>) and (<<p2>>) where p1 and p2 are your start and end date parameters.

Of course, always happy to share. On our system these run on a custom local view that takes soft credits into account, but configured as below they should run fine on the default contribution table, (which does not reflect soft credits!)

Lifetime Number of Gifts

In T_QUERY_ELEMENT:

 

• Description: Contribution Lifetime # of Gifts (or named however you please)
• Category: Contribution
• Data Select: count(ref_no)
• Data From: vs_contribution
• Data Where: cont_amt > 0
• Single Row: (checked) 

 

Number of Gifts by Campaign

In T_QUERY_ELEMENT_PARAMETER:

 

• Description: Campaign
• Data Type: String
• Multi Select: (checked)
• Ref Tbl: vs_campaign
• Ref Id: campaign_no
• Ref Desc: description
• Ref Sort: description

 

In T_QUERY_ELEMENT:

• Description: Contribution # of Gifts by Cpg (or named however you please)
• Category: Contribution
• Data Select: count(ref_no)
• Data From: vs_contribution
• Data Where: campaign_no in (<<p7>>) AND cont_amt > 0
• ....except replace the 7 in <<p7>> above with the id # of the "Campaign" parameter you created in t_query_element_parameter
• Single Row: (checked)

 

You could use the same setup to capture number of gifts over a given date range if you made "Start Date" and "End Date" parameters in t_query_element_parameter. (Or maybe you already have those parameters set up for other output set elements.) Then in the "data where" you would put something like: cont_amt > 0 AND cont_dt between (<<p1>>) and (<<p2>>) where p1 and p2 are your start and end date parameters.