EverTrue allows your institution to implement custom fields at the constituent level to ensure that any additional data points your team needs in the product(s) are available to them.
Creating Custom Fields
To implement custom fields, contact our EverTrue Support (firstname.lastname@example.org) to specify which new custom fields you want added to your account. Please include the following in your email:
- Custom Field Name - the name you want the users to see in the product, not necessarily the name of the field in your file.
- Data Type - what type of data will this field contain? The following options are available: string, date, currency, boolean, or number.
- Custom Field Permissions - what product(s) are these fields intended for? I.e. is this for EverTrue, your Alumni Community, and/or your Volunteers?
Once created and enabled, our Support team will reach out and notify you that you're good to proceed with the new data for import.
Mapping Custom Fields
Once your new custom fields have been created you will be able to map to them in Console during an import. All of your custom fields will be available during mapping of your fields under the "Custom" section. All custom fields have the ability to be list properties, i.e. can be delimited list values using semicolons. Make sure to map those list custom fields appropriately by either multi-selecting your columns or using the delimited checkbox next to the field. For more information on list properties, check out our Data Overview guide here.
In Console, you the ability to customize your previously created custom fields via the "Configure Custom Fields" tab in the left-side menu.
In this tab you will see all custom fields available for your institution, where they have been enabled per product (EverTrue, Community, and/or Volunteer), and their label name. For each platform your institution uses, you'll see a separate tab to toggle between the products and enable or disable the fields at the product level. When editing your custom fields, make sure to toggle over to the platform that you wish to work on. It is important to note that when enabling a custom field, you'll need to contact email@example.com to make sure the backend visibility preferences are also set for the users of that product, i.e. enabling a custom field is a 2-step process, while disabling is only 1-step.
You have the power to change the label for any custom field. Note, the field name is only for back-end use, while the label is the name that will appear in the platform(s). Custom fields will appear in alpha-numeric order according to the labels names. Custom field label names must be consistent across all products, and will be reflected as such.
Don’t forget to save all your changes before checking out the results (if the data has already been imported).
- We recommend labeling the header columns for custom fields as follows: CustomXYZ
- E.g. CustomAthletics, CustomClassAgent, CustomEvents
- Custom fields should retain the same header name for each import.
- Custom fields that have more than one attribute can be implemented in one of two ways:
- Place all attributes in a single custom field column and separate each attribute with a semicolon. E.g. Soccer;Hockey;Baseball
- Map several custom field columns in your file to a single EverTrue custom field. This will eliminate the need to concatenate multiple attributes into a single field. Each column will have a single value, so there is no need to use semicolons to delimit the data.
- You may include as many custom fields as you wish. However, we recommend you start by thinking about what what fields will resonate with your users the most. Try starting with no more than 10, then go from there.
- You can add custom fields at any time, even after you've completed initial implementation. It will simply enhance the platform(s)! Just remember to contact firstname.lastname@example.org about these additions.