Choose the right custom field type

The field type controls what a user can type in and how Service Buddy validates the answer. Choosing the right type up front saves messy data cleanup later.

The six field types

Text

Best for: Short one-line answers like a gate code, lock box number, or referral source.

Keep it for single-line responses. If you expect paragraphs, use Multi-Line Text instead.

Multi-Line Text

Best for: Multi-line notes, descriptions, special instructions.

Renders as a multi-line text box. Users can type as much as they want — no character limit.

Number

Best for: Quantities, weights, readings, sizes.

Service Buddy only accepts numbers in this field. Letters and symbols are rejected automatically, which keeps your data clean for reports and exports.

Dropdown

Best for: A fixed list of options like Priority, Property Type, or Referral Channel.

This is usually the right choice whenever you catch yourself typing the same few values over and over. Dropdowns make filtering reports far easier because everyone picks from the same list.

True/False

Best for: Simple flags like “Has Pets,” “Requires Permit,” “VIP Client.”

Renders as a toggle. Either it’s on or it’s off — no middle ground, no typos.

Address

Best for: A secondary address that isn’t the client’s main billing or service address.

Captures street, city, state, postal code, and country as separate fields so you can print it cleanly on PDFs and filter by region.

A decision shortcut

If the answer is…	Use this type
One of a short list of options	Dropdown
True or false	True/False
A whole number or decimal	Number
A short line of free text	Text
A paragraph	Multi-Line Text
A full postal address	Address
Anything else	Text

Tips for clean data

• Prefer dropdowns over text whenever possible. “Residential,” “Commercial,” and “Industrial” typed freely becomes “Res,” “commercial,” and “industrail” by week three.
• Add a sensible default. If 80% of your jobs are residential, set Residential as the default on the Property Type dropdown. Users can still change it, but most of the time they won’t have to.
• Use Yes/No for flags, not for status. Status fields usually have more than two values (“open, in progress, complete”) so a dropdown fits better.

You can change some types later

Text to Multi-Line Text is safe. Number to Text is safe. Changing a Dropdown to a Number, though, will blank out any values that aren’t valid numbers. When in doubt, create a new field and migrate instead of changing the type in place.

Address fields don’t geocode

An Address custom field stores the text — it doesn’t put a pin on a map or check if the address is valid. For service locations that need routing, use the main location on the client record instead.

FAQ

Should I use Text or Dropdown when in doubt?

Default to Dropdown. Free-text fields drift fast — Residential, residential, Resedential, and RES all end up in your database when three different people type the same answer. A dropdown forces consistency and keeps reports clean.

Can I have a dropdown with hundreds of options?

Technically yes, but UX-wise no. Dropdowns work well up to maybe 20 options. For very long lists (every mill in the industry, every paint color), use a Text field with a clear naming convention instead.

Can I change a field’s type after I’ve created it?

Some changes are safe (Text → Multi-Line Text, Number → Text). Some destroy data (Dropdown → Number blanks out non-numeric values). When in doubt, create a new field with the right type and migrate values manually.

When should I use True/False vs Dropdown?

True/False is right for genuine binary flags — “Has Pets”, “Requires Permit”, “Special Order”. If there’s a third state (“we don’t know yet”), a dropdown with three options (Yes, No, Unknown) is cleaner than a toggle plus a second field.

Should I use a Number field for currency?

Number is fine for amounts, but Service Buddy doesn’t add currency formatting. For prices, the built-in price/cost fields on items and line items are usually a better fit — they’re already currency-aware and feed into reports.

What about dates and times?

There’s no built-in Date custom field type. For dates, most retailers use a Text field with a clear format note (YYYY-MM-DD) or capture the date in the existing job/quote scheduled fields. For one-off date fields, a Text field is the practical workaround.

Can I make a custom field required?

The current field types don’t have a “required” toggle. Required-field enforcement is built into the standard fields (name, email on a client). For custom fields, train staff on what to fill in or build a workflow review.

Related articles

• Create a custom field
• Show custom fields on PDFs and templates