• Replies 10 replies
  • Subscribers 413 subscribers
  • Views 299 views
  • Users 0 members are here
Related

Constituencies vs Attributes

Grant Offermann
$organization

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
Parents
  • $organization

     

    Constituences are built to have start/end dates while attributes are fixed, so that always guides my thinking towards which one to use. Capturing relational data makes sense within constituencies, such as being a board member or subscriber, since those have a natural timeframe attached to them...whereas a fixed or perpetual piece of info (such as a birthdate) is better suited to attributes. Hope that helps guide your thinking!

    It's also certainly possible to display an attribute value in the constituent header - the Flex Header topics in the documentation go into detail. It takes a bit of time but isn't too arduous to set up though.

Reply
  • $organization

     

    Constituences are built to have start/end dates while attributes are fixed, so that always guides my thinking towards which one to use. Capturing relational data makes sense within constituencies, such as being a board member or subscriber, since those have a natural timeframe attached to them...whereas a fixed or perpetual piece of info (such as a birthdate) is better suited to attributes. Hope that helps guide your thinking!

    It's also certainly possible to display an attribute value in the constituent header - the Flex Header topics in the documentation go into detail. It takes a bit of time but isn't too arduous to set up though.

Children
No Data