Custom Fields

Custom fields are used to extend the base DonorPoint object models:

  • adding fields to the objects created on forms or back-end transactions, for example fields you want on every contact in your database, or employee fields for a specific account
  • adding fields to specific forms or items that wil be part of the resulting transaction record
  • adding Integration Codes to specific forms or items that can be used in scripting and reporting

Custom fields can be located in a number of places in the system, on the Customization tab for each:

  • On your Catalog checkout page under Advanced Options
  • On an item
  • On an attendee definition for an Event
  • On an employee relationship for an organization
  • On a Contact, Organization or Fund across your database on the Customization tab on you Account

Custom fields added to pages and items appear on the forms when they are rendered. The data for all custom fields and integtation codes will also appear automatically in reports. Custom field will be available in imports.

Available custom fields include:

  • Checkbox
  • Text Area (i.e., a comment box)
  • Text Field
  • Color (color picker)
  • Date (calendar for date selection)
  • Dropdown
  • File Upload (for uploading a document)
  • Image Upload (i.e. for uploading a logo)

Custom Properties have a number of parameters in common:

  • Name - as you will see it in your database and on records and reports
  • Prompt Text - text used as the label for the field input on forms
  • Confirmation Text - text used as the label when the field is displayed on confirmation pages and emails
  • Hidden - whether the field is hidden on a form - this can be overridden dynamically in response to other fields being changed
  • Required - whether a value is required to complete a transaction
  • Default value - initial value for the property
  • Show On Receipt - whether the field shows up on confirmation pages and emails

The Prompt Text and Confirmation Text can include context variables and messages. Advanced parameters define how the field acts on the form

  • Rendered Rule - script that defines whether the field is rendered on the form or not
  • ReRender Panel - defines whether changing the field causes the entire form to be re-rendered, triggering the Rendered Rules of other custom fields
  • Action - script to be executed when the value of the custom proeprty is changed
  • OnComplete - javascript to run on the form after the custom field value is sent to the server Custom Fields are also the basis for Integration Codes on pages and other objects.
    See Advanced Customization using Scripting for more information.

Once a custom field has been created, it can be re-used again and again. It is important to name your custom fields so it is clear what they do and you can find and use them in the future.

** If a custom field is in use in more than once place, you will see a warning at the top of the page when you open it. Be sure to heed this warning. Any changes you make will affect every all places in which that field is in use.**