Constituencies vs Attributes

Personally, I would tend to use attribute.  For me, Constituencies are more of a “OMG, we *NEED* to know this info about someone every time we pull them up”. 

Attributes in my case are more like ‘yeah, whatever, good that we know this, but I don’t have to see it every. single. time. I pull up your account’

(that’s a little flippant, but I think is a pretty clear explanation J)

Cheers,

Kathleen

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Grant Offermann
Sent: Wednesday, March 29, 2017 5:05 PM
To: Kathleen Smith
Subject: [Tessitura Development Forum] Constituencies vs Attributes

Hi All,

We are getting ready to do some name captures (with contact information) and are trying to decide if it's better to apply a Constituency to them or an Attribute.  Any advice?  We most likely will be using list manager to pull the info but want to make sure we know all the pros/cons before we decide.  Here is what we have:

Constituencies:

Pros:

• Can have it show up on constituent header
• They have start and end dates
• Can be controlled with different security objects (Add, change, view)
• Just create it in TR_Constituency

Con

• Lack of detail, no dropdown.  Their either have it or they don’t.

Attributes:

Pros:

• Can add a subset to the attribute.  Eg: Dropdown to choose from.
• Can be used with control group

Cons

• A little more work creating them since you have to use multiple tables
• No end date

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!

Personally, I would tend to use attribute.  For me, Constituencies are more of a “OMG, we *NEED* to know this info about someone every time we pull them up”. 

Attributes in my case are more like ‘yeah, whatever, good that we know this, but I don’t have to see it every. single. time. I pull up your account’

(that’s a little flippant, but I think is a pretty clear explanation J)

Cheers,

Kathleen

From: Tessitura Development Forum [mailto:forums-development@tessituranetwork.com] On Behalf Of Grant Offermann
Sent: Wednesday, March 29, 2017 5:05 PM
To: Kathleen Smith
Subject: [Tessitura Development Forum] Constituencies vs Attributes

Hi All,

We are getting ready to do some name captures (with contact information) and are trying to decide if it's better to apply a Constituency to them or an Attribute.  Any advice?  We most likely will be using list manager to pull the info but want to make sure we know all the pros/cons before we decide.  Here is what we have:

Constituencies:

Pros:

• Can have it show up on constituent header
• They have start and end dates
• Can be controlled with different security objects (Add, change, view)
• Just create it in TR_Constituency

Con

• Lack of detail, no dropdown.  Their either have it or they don’t.

Attributes:

Pros:

• Can add a subset to the attribute.  Eg: Dropdown to choose from.
• Can be used with control group

Cons

• A little more work creating them since you have to use multiple tables
• No end date

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!