FieldCampCustom Objects, Fields, and Pipelines | FieldCamp
Design custom objects, fields, and pipelines in FieldCamp with validation rules, stage transitions, and saved custom views across every record type.
Under the hood — see how Custom Objects & Fields work in the FieldCamp data model: the fields they hold, how they connect to your other records, and how to customize them.
FieldCamp ships a Salesforce-style platform for modeling your business: define custom objects, add typed fields with validation, and configure pipelines with stages, transitions, and rules. This guide walks through how custom objects, fields, and pipelines fit together so you can tailor FieldCamp to the way your team actually works.
This is the in-depth platform guide. If you just want the basics of creating an object, start with Create Custom Objects, then come back here for field definitions, validation rules, pipeline transitions, and saved custom views.
How the Platform Fits Together
FieldCamp's data model is built from four building blocks that you can configure in Settings:
| Building Block | What It Does |
|---|---|
| Object Definitions | Define a record type — for example, "Asset", "Property", or "Contract". Includes singular/plural labels, icon, color, sidebar visibility, and parent object. |
| Field Definitions | Add typed fields to an object with labels, validation rules, default values, and visibility settings. Labels support i18n so they translate cleanly in multi-language workspaces. |
| Pipeline Configurations | Attach a pipeline to any object with named stages, allowed transitions between stages, and entry/exit rules. |
| Custom Object Records | The actual rows your team creates and edits — filtered, sorted, and grouped through Custom Views. |
System objects (Clients, Jobs, Visits, Invoices, Quotes, Team Members) use the same plumbing, which is why custom and built-in objects feel consistent. For background on how this connects to your CRM, see the CRM overview and key concepts.
Defining a Custom Object
Open Settings > Custom Objects and click New Object. Object definitions control the shell of your record type before you add any fields.
Name the object
Enter both the singular and plural labels (for example, "Asset" / "Assets"). These show up in the sidebar, on detail pages, and inside relation dropdowns.
Pick an icon and color
Choose from icons like box, building, briefcase, wrench, truck, home, map-pin, tag, layers, and shield. Pair it with one of ten colors so the object is easy to spot in the sidebar.
Set the parent (optional)
If this object should nest inside another — for example, a "Pool" under a "Property" — pick the parent here. Records will be filtered automatically on the parent's detail page.
Toggle sidebar and pipeline
Turn on Show in Sidebar to put it in the left navigation. Turn on Enable Pipeline if records should move through stages.
Add relationships
Link the object to system objects (Clients, Jobs, Visits, Invoices, Quotes, Team Members) or other custom objects. FieldCamp creates the relation fields on both sides automatically.
Singular and plural names cannot be changed after the object is created. Pick names you can live with — or duplicate the object and migrate records if you really need to rename it.
Field Definitions and Validation
Field definitions describe each column on your object. Click Add Field on an object to open the field configuration modal.
Available Field Types
| Field Type | Use For |
|---|---|
| Text | Names, codes, short titles |
| Textarea | Notes, descriptions, multi-line content |
| Number | Quantities, counts, sizes |
| Currency | Prices, budgets, deposits |
| Date | Calendar dates (install date, warranty expiry) |
| Boolean | Yes/No toggles (Active, Under Warranty) |
| Select | Single choice from a dropdown list |
| Email addresses with format validation | |
| Phone | Phone numbers |
| URL | Web addresses |
Validation Rules
For each field you can set:
- Required — record cannot be saved without a value
- Visible — show or hide on create and edit forms
- Read-only — visible but not editable in forms (useful for system-managed values)
- Default value — pre-fill the field when a new record is created
- Format validation — automatic for Email, Phone, URL, Number, and Currency types
For Select fields, take time on the option list up front. Kanban groupings and saved custom views lean heavily on Select values, and changing options later can leave older records on stale values.
i18n Labels
Field labels support internationalization, so a single field definition can render in different languages depending on the user's workspace locale. If you operate across regions, set the localized label for each language you support at field creation time.
Field Order and Visibility
Drag the handle on each field to reorder it. The position you set determines the order on create/edit forms and the default column order in the records table. For client-level custom fields specifically, see Managing Custom Client Fields.
Pipeline Configuration
Pipelines turn a flat list of records into a flow. Each pipeline has stages and a transition matrix that controls which stages a record can move between.
Configure Stages
Go to Settings > Pipeline Configuration, pick the object, and open the pipeline editor.
- Add Stage — create a new stage with a name, color, and order position
- Reorder — drag stages to set the default order on the Kanban board
- Rename — update the stage label without breaking existing records
- Archive — hide a stage from new records while keeping it on history
For each stage you can mark it as an entry stage (where records start), an active stage, or a closed stage (won, lost, completed, archived).
Transitions Between Stages
The transition matrix defines which moves are allowed. For each stage, choose which other stages a record can advance or revert to. This is how you enforce process — for example, a "Quoted" record can only move forward to "Won" or "Lost", not back to "New".
The request and lead pipeline uses the same transition engine. See Pipeline Stages & Configuration for the request-specific walkthrough, and Categories & Stages for how it applies to clients.
Transition Rules
You can attach rules to a transition so the move only succeeds when conditions are met. Common patterns:
- Required field check — a field must have a value before a record can leave a stage
- Role gate — only certain roles can perform the transition
- Approval — admin sign-off is required before the move commits
If a rule fails, FieldCamp blocks the transition and surfaces the reason inline. For deeper automation off these transitions, pair pipeline rules with a workflow automation so an email, task, or invoice fires when a record moves stages.
Custom Object Records
Once an object is defined, records live in their own browser at the URL slot for the object in the sidebar.
Paginated record table with search, filter, sort, and inline add/edit/delete.
Save filters, sorts, columns, and Kanban groupings as named views that work across object types.
Use the same filter, sort, and group controls on any custom object table.
Drag records between pipeline stages, respecting the transition matrix you configured.
Creating and Editing Records
Click Add [Object Name], fill in the required fields, and save. Relation fields appear as searchable dropdowns capped at 100 results — type to narrow the list. Edit and delete using the icons on each row; deletes are soft, so records are recoverable for audit.
Sub-Records on Parent Pages
When a custom object has a child relationship to a parent, a sub-records tab appears on the parent record's detail page (including the client detail page). Use the inline Add button there to create child records pre-linked to the parent.
Saved Custom Views
Custom Views work across every object type — clients, jobs, requests, and any custom object. Build a view once, save it, and pull it up with one click.
A saved view captures:
- The active filters on the record list
- The sort order of columns
- The column set (which fields are visible, in what order)
- The layout (Table or Kanban)
- For Kanban, the grouping field (a Select field or the pipeline Stage)
Saved views show up in the toolbar above the records list. See Save Custom Client Views for the full walkthrough — the same pattern applies to every custom object. For module-wide pinning and workspace personalization, also see Workspace Views and the broader custom data views reference.
Permissions
| Action | Who Can Do It |
|---|---|
| Create or edit object definitions | Admin, SuperAdmin, Account Owner |
| Add or edit field definitions | Admin, SuperAdmin, Account Owner |
| Edit pipeline stages and transitions | Admin, SuperAdmin, Account Owner |
| Create, view, and edit records | All authenticated team members |
| Delete records | Admin or higher |
| Save and share custom views | All authenticated team members |
Granular per-object permissions follow your workspace's role configuration.
Troubleshooting
A record will not move to the next stage
Open the record and try the transition again — FieldCamp shows the blocking rule inline. The usual culprits are a required field with no value, a role gate that excludes the current user, or a transition that simply is not allowed in the matrix. Edit the pipeline configuration or update the record and try again.
A field is missing from the create form
Check the field definition's Visible toggle. If it is off, the field is hidden on create/edit forms but still stored on the record. Read-only fields show up but cannot be edited.
A relation dropdown is missing records
Relation dropdowns return the first 100 matching records. Start typing to narrow the search until your target record appears. If you have thousands of related records, consider tightening the relation with a more specific field.
My saved view does not show new records
Saved views apply their filters every time they load. If a new record does not match the filter conditions, it will not appear. Clear the filter or adjust the criteria to include the new record.
I cannot rename an object
Object singular and plural names are permanent. Duplicate the object with the new name, migrate records, and archive the old one.
FAQs
Can I import or export custom object records in bulk?
Not yet. Custom object records are created and edited individually through the UI. System objects like clients support bulk operations — see Import Clients for that workflow, and Export Clients to Excel or CSV for the reverse.
Can a custom object have more than one pipeline?
Each custom object has one pipeline configuration at a time. If you need parallel pipelines for the same record type, create separate custom objects or use a Select field to slot records into a category and filter Kanban groupings off that field.
Do field validation rules run on the mobile app?
Yes. Field validation and pipeline transition rules run on every client — web, mobile, and the API. The same rules apply when records are created or updated through the API.
Can I localize field labels for different languages?
Yes. Field definitions support i18n labels, so the same field renders in the user's workspace language. Set the localized label when you create or edit the field.
How do custom objects work with the Command Centre?
The Command Centre can query custom objects by name. For example, "Show me all properties in downtown" or "List equipment due for service this month" will pull from your custom object records, including filters on your custom fields.
Related Articles
- Create Custom Objects — Step-by-step on creating a custom object from scratch
- Save Custom Client Views — Build named views with filters and Kanban groupings
- Pipeline Stages & Configuration — Stages, transitions, and rules for the request pipeline
- Categories & Stages — How pipeline stages apply to the client object
- Managing Custom Client Fields — Add custom fields to client records
- Filter, Sort, and Group — Use the same controls across every object type
- CRM Overview — How custom objects fit into the FieldCamp CRM
- Roles and Permissions — Who can configure and edit custom objects
- Key Concepts — The core building blocks behind FieldCamp's data model
- Client Detail Page — Sub-records tabs appear on client detail pages
- Workflow Automation Overview — Fire emails, tasks, and invoices when records change stage
- Sales Pipeline Kanban — Drag records between stages on the Kanban board
Create Custom Objects | FieldCamp
Create your own data types in FieldCamp to track equipment, properties, vehicles, or anything unique to your business with custom fields and pipelines.
Manage Client Calls, Emails & SMS | FieldCamp
Manage all client communication from one place. Send emails, review call history, and exchange SMS messages directly from the client detail page in FieldCamp.