Custom fields let you extend Vertiqa's data model with the columns your business actually needs. Each field belongs to one entity type (accounts, contacts, opportunities, jobs, etc.) and is available on that entity's detail and list views.
Layout
- Entity tabs — pick which entity you're editing fields for.
- Field cards — one per custom field, each showing its name, type, and required status. Edit or delete via the card menu.
- Editor — a sheet that opens when you create or edit a field.
Field types
Common types include text, number, date, dropdown (single / multi), checkbox, and entity reference. Pick the type carefully — switching type later usually means losing data.
Tips
- Don't add a field "just in case." Empty custom fields clutter the UI and slow team adoption.
- Use dropdown rather than free text for anything that should be reportable. Free text fragments into "northeast", "NE", "North East" — dropdowns don't.
- Mark a field required only when the entity genuinely shouldn't exist without it. Required fields block save.