'Ghost' Associations in Output Sets

We had a similar problem with attributes at the museum, and discovered that it was because the attribute was not added to the TX_CUST_KEYWORD system table, meaning that the values were not visible in the client.

I’d recommend checking to see if this problem is across all constituent types or not, as if it’s only a problem for some constituent types it may be as simple as adding the constituent type to a system table. (Although you’d have to check with your IT department for the system table relating to association types.)

Hope this helps,

Laine

--

Laine Kyllonen

Database Application Specialist

Science Museum of Minnesota

(651) 221-2515

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
Sent: Wednesday, June 12, 2013 10:49 AM
To: lkyllonen@smm.org
Subject: Re: [Tessitura Technical Forum] 'Ghost' Associations in Output Sets

Hi Sam,

We definitely have that here. I don't know the details behind it but I do know that this happened during the conversion of our contribution data from Raiser's Edge to Tessitura.

Luckily for us all of these associations have the same Association Type and it is a type we do not use for any other reason. So we can easily identify them all by creating a list or using SQL.

Our summer project for the development team is to go through these associations. If any are valid and need to be kept they will make sure it is added to the constituent record using an appropriate type. Once that is complete I intend to simply wipe out the bad conversion ones so they no longer exist.

As to why they don't show up in the constituent record - I can't say. The weird thing here is that some of them show up and others don't.

You aren't alone!

Beth

We had a similar problem with attributes at the museum, and discovered that it was because the attribute was not added to the TX_CUST_KEYWORD system table, meaning that the values were not visible in the client.

I’d recommend checking to see if this problem is across all constituent types or not, as if it’s only a problem for some constituent types it may be as simple as adding the constituent type to a system table. (Although you’d have to check with your IT department for the system table relating to association types.)

Hope this helps,

Laine

--

Laine Kyllonen

Database Application Specialist

Science Museum of Minnesota

(651) 221-2515

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Beth Hawryluk
Sent: Wednesday, June 12, 2013 10:49 AM
To: lkyllonen@smm.org
Subject: Re: [Tessitura Technical Forum] 'Ghost' Associations in Output Sets

Hi Sam,

We definitely have that here. I don't know the details behind it but I do know that this happened during the conversion of our contribution data from Raiser's Edge to Tessitura.

Luckily for us all of these associations have the same Association Type and it is a type we do not use for any other reason. So we can easily identify them all by creating a list or using SQL.

Our summer project for the development team is to go through these associations. If any are valid and need to be kept they will make sure it is added to the constituent record using an appropriate type. Once that is complete I intend to simply wipe out the bad conversion ones so they no longer exist.

As to why they don't show up in the constituent record - I can't say. The weird thing here is that some of them show up and others don't.

You aren't alone!

Beth