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.
Replying mainly to say this would be a spectacular conference session title!
'Divorced, married or killed 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 or use relationships in a different manner?
Victoria
It will depend where you store these in the database. Many sites have an Attribute of DOD (Date of Death) but Marriages/Divorces tend to just be in Development Bio notes – though the Marital Status is often an Attribute.
I suppose manner of death could be an Attribute too
Check where this info is captured and there may be a way to pull the data
From: Donna Searles-Brown [mailto:bounce-donnasearlesbrown1984@tessituranetwork.com] Sent: Wednesday, March 02, 2016 6:06 PM To: McKinley, Leslie <LMcKinley@nycitycenter.org> Subject: [Tessitura Shared Reports Forum] Track Divorce, Marriage, and Deaths
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!
Donna
You might want to look at the audit table in Tessitura – you can see it under the Transactions Tab and the Audit radio button in a constituent’s account
Your System Admin could make a custom list criteria based upon the audit date and the column being inactive and the new_value = 2 (meaning it has been inactivated) and then you can include your other criteria of the inactive reasons you are interested in.
Of course you could make a report based upon the Audit table and combine the inactive reasons too.
Just a thought that might help if nothing else pops up.
Cheers
Sandra
From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Donna Searles-Brown Sent: Thursday, March 3, 2016 10:07 AM To: Sandra Ashby <sashby@tessituranetwork.com> Subject: [Tessitura Shared Reports Forum] Track Divorce, Marriage, and Deaths
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'
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?