Custom construction fields, tables and imports

Extend standard records without code, create typed company tables and import CSV or XLSX contacts with preview and field mapping.

Custom construction fields, tables and imports: how it works in Home Builder Software

Every builder tracks something the standard record does not hold, and that detail usually ends up in a spreadsheet nobody else can find. Under Settings and Custom data, administrators and managers extend the standard models without writing code: an extra field on the project file, a small table for a list the software does not carry, or an import that brings the existing contact list in. The side file becomes unnecessary.

A custom field is typed from the start: single or multi-line text, number, currency, percent, date, date and time, email, phone, URL, yes or no, single choice and multiple choice. Data type, required status, active status and the option values stay editable afterwards, and the field shows up in the detail files of projects, leads, customers, subcontractors, service requests and equipment. A custom table adds a name, a description and typed columns that server-side validation enforces on every entry.

Imports feed the same structures. The reader takes CSV, TXT or XLSX, shows a preview and lets you map columns onto name, email, phone and address; contacts already known by email are updated instead of duplicated, and new rows receive their own customer number. Customer, project, employee and subcontractor stay fixed relations rather than configurable fields, so the links between records survive every change to the model. Only administrators and managers may change it.

Real Home Builder Software interface for Custom construction fields, tables and imports
The settings area of Home Builder Software with the tab row Company, People & permissions, Master data & lists, System and My account, opened on Jordan Miller's account with the Raleigh main office; custom fields, custom tables and the contact import belong to this same area.

Custom construction fields, tables and imports in the daily routine

The need usually surfaces in the office: a value keeps being written into a comment because no field exists for it. A manager opens Custom data, adds the field with its type, marks it required where a record should not be saved without it, and sees it appear in the relevant detail files. Site and sales staff fill it as they work. A whole list gets its own table the same way, and an inherited contact file is mapped once and imported.

Read the documentation

Custom construction fields, tables and imports: what it covers

  • Add typed fields to projects, leads, customers, subcontractors, requests and equipment

  • Define custom tables with validated column schemas

  • Map contact columns and update existing records by email during import

Custom construction fields, tables and imports: questions and answers

Can a customer or project relationship be replaced by a custom field?

No. Core relationships remain fixed tenant-filtered records rather than configurable fields.

Which contact import formats are supported?

The import reads CSV, TXT and XLSX and provides a preview before mapping.

Use Custom construction fields, tables and imports on your own projects

A demo runs on a project that resembles yours, with the roles and permissions your team actually uses.