Novi has a standard set of fields that are used to collect various types of data throughout the software, such as member or events data. Most likely, you have additional data that doesn't fit our standard set, thus the need for custom fields specific to your organization.  

Novi AMS can be personalized to an association's business practice using custom fields. These fields can be attached to member records or added to event registration forms.

NOTE: Limited admins cannot update custom fields.


Where Custom Fields Are Used & Common Examples

As noted above, custom fields are used to collect data outside the standard set of fields Novi provides. Custom fields will typically fall into two categories for use in multiple scenarios:

  1. Member Data Fields
  2. Event Attendee Data Fields

Custom Member Data

Used to:

  • Set-up dues rules
  • Set-up groups
  • Take internal admin notes
  • Create custom reports
  • Create filters on your member directory or member detail pages

Examples include:

  • Data to calculate dues such as # of employees, unit counts, # of locations, etc.
  • Internal Member Notes
  • Filter by County, Committee, or other segments of your data your members may search for in the member directory

Event Attendee Data

Used to:

  • Collect specific attendee information 
  • Run event specific reports

Examples include:

  • Dietary Restrictions
  • Session Choice
  • Team Name

Ecommerce Purchase Data

Used to:

  • Collect and view information about selections of products being purchased and/or the purchaser

Examples include:

  • T-Shirt Size
  • Nominee Information
  • Dates of Room Rental Requests


How To Set Up Custom Fields

Under the Fields section in the left navigation on the backend:

  1. Select Custom Fields
  2. Click the Add Custom Field button

This will bring up a modal with fields to fill out. From there, select the settings needed for your field. Keep reading below for more information!


The Basic Settings

Below, you'll find information about settings that should be considered for all custom fields.

1 and 2 - Field and Display Name

The field name and display name are often the same. But sometimes you may need to distinguish a field name with an additional note that you don't want shown to your members on the front-end. Alternately, you may need to add clarification in the Display Name (so users understand what you're asking for), but the Field Name can be abbreviated.

3 - Field Type

You have multiple options here to fit your needs.

  • Plain Text: This creates an open text box to fill out. Can be single line or multi-line. Can also have a character limit.
  • Date/Time: Allows you to collect date only, time only, or both. Field can also have a min or max.
  • Number: Choose this if you only want to collect numerical values. There is an option to select whole numbers only. Field can also have a min or max. Member records can also be enabled to "show summation checkbox." This allows a parent record to inherit the sum of its children's values for that field. Example: Acme East Coast Division has a value of 5 for their 'employe count' custom field and Acme West Coast Division shows 9. Using this summation functionality, Acme US can automatically show 14 employees for their 'employee count' custom field.
  • Checkbox: Displays a box to select Yes or No.
  • Related Member Record: This allows one member record to be attached to another. Allowing "non-members" makes the field an open company or person with no link to another record in the database. Once the user starts typing a name, this type of custom field will display a list of records from your database. By default, selecting this option will also collect phone number, email and company name. Some examples include Emergency Contact or Team Captain.

4 - Sections

Next, tell the custom field where you want it to appear. 

  • Members: Check this option if this field will need to be filled out on a member's record. This could be during signup, in their profile, done by an admin, etc. Fields can be limited to just individuals or companies. They can also be limited to specific member types.
  • Events: Check this option if this field will need to be filled out during the registration of any events. Remember that if a custom field is filled out within a member record, and the member registers for an event, the custom field will auto-fill.
  • Ecommerce: Check this option if this field will need to be filled out during the purchase of any products.  

5 - Frontend/Backend

  • Internal Use Only: Check this option if this field should only show and be available to admins.
  • Require on Frontend: Check this option if this field needs to be required on the frontend when users are prompted to fill it out.
  • Require on Backend: Check this option if this field needs to be required on the backend/admin side when prompted to fill it out.


Additional Custom Field Settings: Member Section

Below, you'll find information about settings that should be considered specifically for custom fields with visibility exclusively within OR including the members section. This could be a combination of members + events sections, members + ecommerce, or all three.

6 - Frontend/Backend

  • Internal Use Only: See item #5 above
  • Users Cannot Change on Frontend After Initial Value: This setting is a hybrid between internal-use only and visible on the frontend. This type of field is great for information that is required up front, but you may not want the member to have the ability to edit the value without contacting you first. Examples include Unit Count & Employee Count, because oftentimes dues rules are based on the value of this custom field.
  • Require on Frontend: See item #5 above
  • Require on Backend: See item #5 above
  • Key Information: If a field is required then it is also considered to be Key Information. This option is only available if "Member Record" or "Event Registration" is checked in the Visibility section (#4 above). Learn more about Key Information here.

7 - Details

Basically, in which sections pertaining to members do you want to be able to see this field?

  • Member List View (Admin): Makes the custom field values viewable on the member list page.
  • Dues Rules: Enabling Dues Rules allows the field's value to be used when calculating or applying dues rules. 
  • Directory Profile Page: This allows the custom field values to display on member profiles in the frontend directory.
  • Attendee List: In the context of member records, checking this will allow you to view data for the custom field that has been filled out on a member's record within a column on an event attendee list. Please note that this option also appears when ONLY the events section is checked. It will show the custom field filled out during an event registration in the attendee list. If it was not manually filled out, it will populate what the member has on their record. If there was no value, it will show blank.

NOTE: Set of Options & Checkbox custom fields will also have a Member Directory Filter option that will allow users to use the options as filters to select from in the directory.

8 - Individuals/Companies

  • Determine whether this field needs to be displayed for people records, company records, or both types of records. For example, you probably wouldn't want to ask a company for its dietary restrictions.

9 - Restrict to Member Type

If a custom field is only applicable to certain member types, toggle this setting to ON. This will display a list of your member types and all types will be checked by default - update as needed.

Once you've completed all the settings, click the Save & Close button.


Related Articles

Did this answer your question?