Custom Fields

How Lead360 helps

Lead360 Custom Fields adds typed business data to supported records when standard fields do not cover the requirement. The field definition, data type, options, visibility, and downstream use provide a stable contract for forms, imports, filters, automations, and reporting.

When to use this area

Use a Custom Field for a reusable value that belongs on a supported record and needs consistent validation or filtering.

Before you begin

• Confirm no standard field or existing custom field already fits.
• Choose the correct object, data type, options, and naming.
• Review forms, imports, automations, templates, and reports that will use the field.

Design the field

1. Choose the record type the value belongs to.
2. Use a clear customer-safe label and stable internal purpose.
3. Select the correct data type: text, number, date, checkbox, or controlled choice.
4. Define options before connecting the field to forms or workflows.

Connect it carefully

1. Add the field only to forms and views that need it.
2. Map CSV imports and integrations explicitly.
3. Update Smart Lists and automations that depend on the value.
4. Test creation, editing, filtering, and merge-field output with one record.

Before changing a field

Renaming a label is usually safer than changing its meaning or type. Review existing data and every dependency before deleting options or the field.

Use Ask360 here

Ask360 can explain the schema, search authorized dependencies, and prepare one reviewed custom-field creation or safe metadata update when supported. It never changes a populated field type, deletes values or a field, remaps imports, or edits contact data from this Help flow.

Confirm the result

A completed Custom Fields workflow should be visible in the product area that owns the final record. Use these checks before relying on the result or moving to the next customer-facing step.

• Enter representative valid and invalid values.
• Test form and import mapping.
• Confirm Smart Lists, templates, automations, and reports interpret the value correctly.

Troubleshooting

A field cannot be changed to a new type

Create and test a replacement field, migrate values with validation, update dependencies, and retain the old field until references are cleared.

Values appear inconsistent

Review option spelling, blank handling, source mapping, and historical imports before normalizing data.