Entity link origin

Where a record's link to an opportunity or customer came from in your CRM or ERP.

Part of Counterparties in the register catalog.

Register ID

entity_link_originUse this name to ask for the register. The API calls it a shelf ID.

Each record is

A stateThe current value of something, replaced when it changes.

Status

AvailableFilled today from connected systems, uploads or public data.

Data

OrganisationPrivate to each organisation's own workspace.

Version

v1Current version.

Download JSON SchemaSee an example record

Connectors

Connected today

Demiton keeps this register current from these systems now.

• Business Central
• HubSpot

On the roadmap

Systems in the planned connector rollout that can fill this register. Partial means the system holds only some of its fields.

• MYOB Acumatica

Fields

13 fields: 8 required, 5 optional.

Required

Every record carries these fields.

relationText

The link direction/type, as declared by the org's EntityLinkSpec.relation (observed value originated_from_opportunity).

Example: originated_from_opportunity

subject_entity_idNumber

The subject entity the fact is anchored to (observed: a project).

Example: 8101

subject_entity_typeText

The subject's spine entity type.

Example: project

object_entity_idNumber

The linked object's canonical spine entity id (observed: an opportunity).

Example: 7001

object_entity_typeText

The linked object's spine entity type (observed: opportunity).

Example: opportunity

object_external_idText

The source system's natural key the two entities share — the join key the link is derived on.

Example: OPP-2025-0141

link_source_systemText

The system whose shared alias key joins the pair (observed value D365_BUSINESS_CENTRAL).

Example: D365_BUSINESS_CENTRAL

computed_atDate and timeISO 8601, with time zoneUnit: UTC

When the origin fact was (re)materialised.

Example: 2026-03-12T05:00:00Z

Optional

Present when the source system records them.

outcomeText

The linked object's outcome at materialisation time (won/lost/open).

Example: won

valueTextUnit: currency of value

The linked opportunity's estimated value (BC Estimated_Value_LCY, AUD by default).

Example: 2850000

value_currencyTextUnit: ISO 4217

Currency of value.

Example: AUD

closed_dateDateYYYY-MM-DD

The linked opportunity's close date.

Example: 2026-03-12

summaryText

The composed human-readable sentence about the link.

Example: Project originated from Opportunity OPP-2025-0141, won 20…

Example record

A sample from Bridgeworks Group, Demiton's demonstration company. The values are illustrative; the shape is exactly what the contract describes.

entity_link_origin.example.json

{
  "closed_date": "2026-03-12",
  "computed_at": "2026-03-12T05:00:00Z",
  "link_source_system": "D365_BUSINESS_CENTRAL",
  "object_entity_id": 7001,
  "object_entity_type": "opportunity",
  "object_external_id": "OPP-2025-0141",
  "outcome": "won",
  "relation": "originated_from_opportunity",
  "subject_entity_id": 8101,
  "subject_entity_type": "project",
  "summary": "Project originated from Opportunity OPP-2025-0141, won 2026-03-12.",
  "value": "2850000",
  "value_currency": "AUD"
}

Use this contract

The contract is a standard JSON Schema (draft 2020-12) document, so any JSON Schema validator can check a record against it. Keywords starting with x-demiton- add Demiton's own meaning, such as units and requiredness, and validators ignore them.

Schema URL

https://docs.demiton.io/registers/entity_link_origin/v1.json

Show the full JSON Schema

Loading the schema…