How do I add a custom field to a Constituent record?

Matt Burghdoff:

You'll need to change your database configuration settings, but this was a special permission that we had to request from our account rep.  To see if you have access to this, login and check to see if you have "Database Configuration" as a drop down selection in "Setup" along your top nav bar.  If you do, select it and go to "Additional Information."  Expand that, and there are your custom strings available for use.

If you DON'T have Setup-->Database Configuration as an option, then you'll need to contact your convio rep.  If you do, you should also check to see what your limit is on custom strings that can be used (can't remember if this is a contractual limit or hard limit of the database software).

Be careful about using up all of your custom strings, though, as you might in the future have another use for them but run into huge problems if you've already filled them with info.  So far, of the dozen or more requests to use a custom string I've been able to find other ways to record that info for all but one, and most of the info never ended up being used anyway.

Note that generally these database configuration settings are not available to clients directly.  The best way to add new custom constituent fields to your Convio instance is to open up a case with Convio Support.  The Support Analyst will be able to help you determine the best field type for the data you would like to store.  They will also be able to help you consider other implications of activating new fields (reporting, data syncs, and API integration).  It's much more difficult to undo changes to the database configuration than it is to make them in the first place so we prefer to be involved in the process.

In the future we are considering additional ways that clients will be able to self-manage custom constituent attributes in the system without the risks that are currently involved.