Skip to main content
Lesson 3 of 10 · ~5 minutes · Prerequisite: Lesson 2 — Objects and records

What you’ll learn

  • What attribute types exist
  • How to add a custom field
  • When to use a formula instead of a manual field

Standard and custom attributes

Each object has standard attributes (name, owner, creation date, status) and you can add custom attributes to fit your business model. Useful examples:
  • On Deal: Lead source (select), Probability (number), Acquisition cost (currency)
  • On Company: NACE sector (select), Annual revenue (currency)
  • On Invoice: Related project (reference)

Attribute types

Free-form string, single or multi-line. For names, descriptions, notes.
Integer or decimal. You can set a unit (€, %, pcs, hours).
Number with currency symbol. Multi-currency with automatic conversion.
Day or precise timestamp. Timezone-aware.
Pick from predefined options. Single or multi-select.
True/false. For flags like VIP, Paid, Archived.
Link to another record. E.g. Owner (reference to Employee), Parent company (reference to Company).
Auto-computed from other attributes. E.g. weighted_value = deal_value × probability / 100.
Special select with a workflow. Statuses can be grouped (e.g. Open → Qualified → Won / Lost).

Add a custom field

1

Open the object configuration

Go to Settings → Objects and select the object (e.g. Deal).
Deal object configuration with attribute list
2

Add attribute

Click + New attribute. Name, type, required flag.
3

Define options (select)

For select attributes, enter options with a colour (useful in Kanban pipelines and filters).
4

Control visibility

Decide who can view and edit the field: everyone, specific roles, or only the record owner.
5

Save

The field is immediately available on every record of that object, in views, filters and automations.

Using a formula

Formulas enable automatic calculations. Practical example on Deal:
weighted_value = value * (probability / 100)
Formula editor with expression and result preview
Supported operators: arithmetic (+ - * /), comparison (> < == !=), logical (AND OR NOT), text (CONCAT LOWER UPPER), date (DAYS_BETWEEN TODAY).
If a referenced field is deleted, the formula errors until you fix it. Arya warns you.

Best practices

  • Don’t create a thousand fields: add them only when truly needed. Too many fields slow the team down.
  • Use sections: group related fields (Commercial data, Legal data, Internal notes).
  • Standardise values: prefer Select over free text when possible (avoid Rome, ROME, rome).

Verify

You know the main attribute types
You added at least one custom field to an object
You can write a simple formula

Next lesson

Lesson 4 — Lists, views and filters

Create your first dynamic list and share it with the team.