Custom fields in ProjectMark allow you to structure and standardize information across opportunities, contacts, and companies. By choosing the right field types and placing them correctly, you ensure data remains consistent, searchable, and useful across the platform.
This article explains where custom fields can be created, how field visibility works, and how to choose the right field type for your data.
Where Custom Fields Can Be Created
Custom fields in ProjectMark are configured from Settings, and the location determines where those fields appear.
Opportunity Fields
To create or manage opportunity fields:
- Go to Settings → Opportunity Fields Templates
Fields created here:
- Are available on all opportunities
- Support consistent data capture across your pipeline
- Can be used with workflows and conditional logic
You can also add a field directly from an Opportunity card. Fields created this way:
- Apply only to that specific opportunity
- Are useful for one-off or unique information
- Do not affect other opportunities
Contact and Company Fields
Custom fields are also available for contacts and companies.
- Contacts:
- Go to Settings → Contact Data Fields
- Companies:
- Go to Settings → Company Data Fields
Fields created in these areas:
- Appear on all contact or company records
- Are ideal for storing standardized profile information
- Help maintain consistency across your CRM
Conditional Visibility with Automated Workflows
ProjectMark supports automated workflows that control when fields appear based on defined conditions.
For example:
- A field can appear only when an opportunity sector is Commercial
- Certain fields can be shown or hidden based on type, stage, or classification
This approach keeps records clean while still capturing detailed information when it’s relevant.
Creating a Field: Core Configuration
When creating a custom field, you’ll define:
- An icon to visually identify the field
- A field name that clearly describes the data
- A field type, which determines how data is entered and used
Choosing the correct field type is critical for reporting, filtering, and long-term data quality.
Text-Based Fields
Single-Line Text
Use single-line text fields for:
- Short labels
- Codes or identifiers
- Brief notes
These fields are best when formatting is not required.
Paragraph Text
Paragraph fields support longer inputs and formatting.
Use paragraph fields for:
- Descriptions
- Scope details
- Background information
- Notes that require readability
Paragraph text is especially useful when content may later be reused in proposals or reports.
Selection Fields: Dropdowns and Tags
Selection fields help standardize information that appears frequently.
Dropdown Fields (Single Selection)
Dropdowns allow users to select one predefined option.
Best used for:
- Categories
- Sectors
- Delivery methods
- Status classifications
Dropdowns are ideal when only one value should apply and when consistency is critical for filtering and reporting.
Tag Fields (Multiple Selection)
Tag fields allow multiple values to be selected.
Best used for:
- Attributes that can overlap
- Flexible classifications
- Labels that may change over time
Choose tags when a record may logically belong to more than one category.
Numeric and Date Fields
Number Fields
Number fields store measurable values and can include units, such as:
- Meters
- Centimeters
- Inches
- Liters
Use number fields when values represent quantities but are not financial.
Date Fields
Date fields support two formats:
- Single date
- For deadlines, birthdays, milestones, or fixed dates.
- Date interval
- For ranges such as construction periods, contract durations, or phased work.
Intervals are especially useful when start and end dates matter equally.
Money Fields
Money fields are designed specifically for financial values.
Key characteristics:
- A currency is selected per field
- Values are stored exactly as entered
- No automatic currency conversion is applied
Use money fields for budgets, costs, estimates, and financial tracking where currency matters.
Formula Fields
Formula fields calculate values based on other existing fields.
They can:
- Reference number, money, or date fields
- Perform operations such as addition, subtraction, multiplication, and division
- Combine multiple fields into a calculated result
Formula fields are ideal for:
- Totals
- Comparisons
- Derived metrics
Important:
All fields used in a formula must already exist before the formula field can be created.
Best Practices for Custom Fields
- Create global fields only when reuse is expected
- Use opportunity-level fields for unique cases
- Group selection fields thoughtfully (dropdown vs tags)
- Design formulas after base fields are defined
- Use workflows to control visibility and reduce clutter
