Object Types

Object Type changes how the application treats the data over time and how it expects certain identifiers.

Below is a practical explanation of each type of object.

1. Standard

Use when:

• you want a basic Object with fields

• you do not need external identifiers or history timelines

Best for:

• internal reference data

• simple dimension-like datasets

2. Standard External

Use when:

• the data is coming from an external system

• you need an external identifier to match records

Best for:

• synced entities from external sources (CRM, ERP, etc.)

3. Standard Bitemporal

Use when:

• you need to track changes across time in a more advanced way

• you care about “valid time” and “transaction time” concepts

Best for:

• regulated domains where you must understand “what we knew when” and “when it became true”

4. Transactional

Use when:

• you need transactional behavior (data changes recorded as transactions)

• you need timeline tracking

Best for:

• event-like or transaction-like entities

5. Complete Snapshot

Use when:

• you receive full snapshots periodically (e.g., daily full extract)

• each load represents a complete view at a point in time

Best for:

• daily exports of complete tables

6. Incremental Snapshot

Use when:

• you receive incremental updates (only changes since last time)

• you still want snapshot-like semantics

Best for:

• CDC (change data capture) style ingestion

7. Permissions Object

Use when:

• this Object is specifically meant to represent permissions/security data

• it will be used as part of Row-Level Security rules

Best for:

• user-to-entity access mappings

• entitlement/permission tables