Skip to main content
Once you have created custom fields, you can populate them with data and use them across Slant. This guide covers entering data, displaying fields in views, filtering, and importing values.

​
Enter custom field values

​
On a single record

  • Open a client, prospect, business, or opportunity
  • Scroll to the Custom fields section
  • Click on the field to edit it inline
  • Enter the value and save

​
Input by field type

Field typeHow to enter
TextType in the text box
Rich textUse the rich text editor
NumberType a numeric value
DateClick to open the date picker
Yes/NoClick to toggle
Single selectClick and choose an option from the dropdown
RelationshipsSearch for and select a record
User referenceSelect a team member from the dropdown

​
Display custom fields in table views

Add custom fields as columns in your list views:
  • Open Clients, Prospects, or the relevant list view
  • Click the column manager (the + button or column settings)
  • Select the custom fields you want to display
  • Custom field columns appear alongside standard columns
Custom field columns support sorting and filtering, just like standard columns.

​
Filter by custom fields

Use custom field values to filter your list views:
  • Open a list view (Clients, Prospects, etc.)
  • Open the filter panel
  • Find your custom field in the filter options
  • Set the filter condition and value
  • Apply to see matching records

​
Available filter operators

Field typeOperators
TextEquals, contains, starts with, ends with, blank, present
NumberEquals, not equal, greater than, greater than or equal, less than, less than or equal, blank, present
DateEquals, not equal, greater than, less than, blank, present
Yes/NoEquals (true/false), blank, present
Single selectEquals, not equal, blank, present, in
RelationshipsBlank, present
User referenceEquals, blank, present, in

​
Import custom field data

​
Include in a CSV import

When importing records via CSV, custom fields appear as additional mapping targets in the importer:
  • Add a column for the custom field in your CSV
  • During the mapping step, map the column to the custom field
  • Values populate automatically on each imported record

​
Value formats for CSV import

Field typeCSV format
TextPlain text
NumberNumeric value (no commas)
DateYYYY-MM-DD or MM/DD/YYYY
Yes/NoTRUE, FALSE, Yes, No, 1, 0
Single selectExact option text
Example CSV: 
name,risk_tolerance,accredited_investor,target_return
Smith Family,Aggressive,TRUE,8.5
Johnson Household,Moderate,FALSE,6.0

​
Export custom field data

Custom fields are included in CSV exports from list views. The column header uses the field’s display name.

​
Use in workflows

Custom fields can be referenced in workflow triggers, conditions, and actions:
  • As trigger conditions — Start a workflow when a custom field value matches a condition
  • In branch conditions — Route workflow logic based on custom field values
  • As action targets — Set custom field values as part of a workflow action

​
Field keys in automations

Each custom field has a field key (e.g., risk_tolerance) that is used internally for automations and reporting. You can view the field key by editing the custom field in Settings > Data customizations > Custom fields. Field keys are auto-generated from the display name and cannot be changed after creation.

​
Best practices

​
Keep data current

  • Update custom fields when information changes
  • Include custom field reviews as part of regular client reviews

​
Use single select for consistency

For data you plan to filter or report on, use single select fields instead of free text. This ensures consistent values across records.

​
Define clear options

For single select fields:
  • Use clear, descriptive option names
  • Document what each option means for your team
  • Keep the list focused — too many options reduce usability

​
Review unused fields

Periodically check:
  • Which fields have low fill rates
  • Whether all fields are still relevant
  • If any fields should be deleted to reduce clutter

​
Troubleshooting

​
Field not appearing on a record

  • Verify the field was created for the correct record type (Household, Business, or Opportunity)
  • Household custom fields appear on both clients and prospects

​
Cannot enter a value

  • For single select fields, the value must match one of the defined options
  • For number fields, the value must be numeric

​
Filter returns unexpected results

  • Verify you are using the correct operator
  • For single select fields, the filter value must match the option exactly
  • Check that data was entered consistently across records

​
Custom field not appearing in CSV import

  • The custom field must exist before you start the import
  • The field must be created for the same record type you are importing

​
Next steps

Custom fields overview

Create and manage fields

Field types

Choose the right field type