I am trying to find a way to track the changes we make for divorce, marriage and deaths in Tessitura.
Is there a way to pull a report that would indicate who has been divorced, married or killed within Tessitura?
We specifically are looking to be able to pick a date range and pull a report based on that date range with any constituents who have been made inactive within that date range.
Victoria, I love it!
When we know of a marriage/divorce, we will household or de-household as needed, but we don’t have an attribute or association/affiliation type to mark them as such. I guess that part isn’t as important to us! As long as we know we have the correct people in the correct relationship pairings, we’re all good.
For pulling a record of deceased, I would use a basic sql query as suggested. This we actually do care about, because we have a more elderly population, and it’s theoretically possible to have a decrease in sales or donations if our population shrinks more than it grows in a given year!
Cheers, Kathleen
From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Victoria Carlin Sent: Thursday, March 03, 2016 5:29 AM To: Kathleen Smith Subject: Re: [Tessitura Shared Reports Forum] Track Divorce, Marriage, and Deaths
Replying mainly to say this would be a spectacular conference session
'Divorced, married or killed within Tessitura? - auditing within Tessitura'
In addition, I'd be really interested in this too, would a basic query on t_customer where inactive_reason is not null or the corresponding number code for your org as deceased suffice for deaths?
How do you register your marriages and divorces? Do you household and de-household?
Could you do an amalgam of Sandra's idea and report on the relationship table too? This could give you a better idea of when a record is de-householded?
I also had an idea about using CSIs for this too? I'd imagine you get notification that the divorce/marriage has happened and it might be a quick way to implement?
If a CSI with a better name than 'relationship status' type is added (we run our dietary requirements as CSIs too) then you could have a regular report run using CSI Tracking which would give you a basic idea of these changes?