Skip to main content

Mapping fields without code

When several tools describe the same thing, SixDegree merges them into one record: one Account, one Contact, one Deal. This page covers how to control what feeds each field, entirely with pickers. No expressions required.

The Map fields dialog​

Open Build → Your model, expand a type (say, Contact), and click Map fields. You'll see every field, its value on a real sample record, and where it comes from.

Each dropdown shows the source's actual fields with real values from the record you're looking at, plus how often each field is filled, so you can pick the right source field without opening the source system:

account_id · "001QR7ax" 
phone      · "+1-510-555-0190" · 87%

Change a mapping and the preview below updates against your real records before you save. Your choices survive re-syncs and pack updates.

Some values live on a different record. A contact's account_name is not on the contact. It's on the account the contact points to.

Pick ↗ From a related record… in any field's dropdown:

  1. Related record type: the record to pull from (e.g. Account)
  2. Field on this record that points to it: the connecting field (e.g. account_id)
  3. Field it matches on the related record: usually Id, preselected
  4. Field to bring in: what you want (e.g. Name)

The preview shows the looked-up values immediately: record IDs become company names before your eyes, and you save when it looks right. Looked-up values carry full provenance. Verifying one shows it came from the related record, and access to it follows your permissions for that record's system.

Combining fields and set values​

Pick ƒ Combine fields or set a value… for the other common shapes:

  • Combine two fields: first_name + last_name into a full name, with any separator
  • First field that has a value: use work_email, fall back to personal_email
  • A fixed value: stamp a constant

These read back as what they are. A saved combination shows as ƒ first_name + last_name with an edit button, not as a formula you have to decode.

When sources disagree​

If a field is available from more than one source, the row shows a +1 marker. Hover it to see which sources compete and which one wins. The winning source's value is used; the losing values are kept and visible when you verify the field.

Advanced: expressions​

Everything above compiles to the same expression language available in Build → Canonical Types for technical users. Hand-written expressions are shown read-only in the Map fields dialog and are never overwritten by picker edits.