Field types

Custom fields come in different types, each suited to specific kinds of data. Choose the right type when creating a field — the field type cannot be changed after creation.

​

Text

Short text values without predefined options. Examples:

• Preferred name
• Employer name
• Hobbies

Behavior:

• Accepts any text input
• Single-line text field

​

Rich text

Longer formatted content with rich text editing. Examples:

• Investment philosophy
• Special instructions
• Background notes

Behavior:

• Supports formatting (bold, italic, lists, etc.)
• Multi-line content
• Rendered with rich text styling on the record

​

Number

Numeric values with optional formatting. When creating a number field, choose one of three formats:

​

Plain number

Standard numeric values without special formatting. Examples:

• Years as client
• Number of accounts
• Age at retirement

​

Currency

Money amounts displayed with currency formatting. Examples:

• Target AUM
• Annual fee
• Insurance coverage amount

Behavior:

• Displays with currency symbol
• Formatted with thousands separators

​

Percentage

Percentage values displayed with a % symbol. Examples:

• Equity allocation target
• Annual return goal
• Fee rate

Behavior:

• Displays with % symbol

​

Date

Calendar date values. Examples:

• Policy renewal date
• Anniversary
• Last review date

Behavior:

• Date picker interface for input
• Stored as a date (no time component)

​

Yes/No (boolean)

True or false values. Examples:

• Accredited investor
• Receives newsletter
• Has estate plan

Behavior:

• Toggle or checkbox interface
• Stores as true/false

​

Single select

One choice from a predefined list of options. You define the options when creating the field. Examples:

• Risk tolerance (Conservative, Moderate, Aggressive)
• Lead source (Referral, Seminar, Web, Other)
• Billing type (AUM, Flat fee, Hourly)

Configuration:

• Add at least one option when creating the field
• Options can be added or removed later by editing the field
• Each option is a text value

Behavior:

• Dropdown interface for selection
• Users can pick exactly one option
• Consistent data for filtering and reporting

​

Relationships (cross reference)

Link a record to another record in Slant. When creating a relationship field, you choose which record types can be linked. Allowed target types:

• Household (client or prospect)
• Business
• User

Examples:

• Referred by (links to a household)
• Related business (links to a business)
• Primary advisor (links to a user)

Configuration:

• Select at least one allowed target type
• You can allow multiple target types on the same field

Behavior:

• Search and select interface for choosing a record
• Creates a bidirectional relationship between records
• Shows the linked record name with a clickable link

​

User reference

Link a record to a team member in your workspace. Examples:

• Assigned planner
• Onboarding coordinator
• Secondary advisor

Behavior:

• Dropdown of team members
• Shows the user’s name on the record

​

Choosing the right type

​

When to use single select vs text

Use single select when:

• The possible values are known and limited
• Consistency matters for filtering and reporting
• You want to enforce specific choices

Use text when:

• Values are unpredictable or highly varied
• Users need complete flexibility
• The list of possible values would be too long

​

When to use single select vs tags

Use a single select custom field when:

• The options are specific to one data point
• You need exactly one value per record
• Values should not change often

Use tags when:

• The same labels apply broadly across records
• You need multiple labels per record
• You want flexibility to add new labels on the fly

​

Field keys

Each custom field gets an automatically generated field key based on its display name. Field keys:

• Are lowercase with underscores (e.g., risk_tolerance)
• Cannot be changed after creation
• Are used in automations and reports

You can see the field key when editing a custom field.

​

Next steps