Last deployment: —
Sign InJoin
TURFI

Turfi Platform Documentation

Official Turfi documentation portal for users, admins, and developers.

Back to support

Documentation Search

Search only within Turfi documentation pages.

C

Relationship Resolution

Foreign-key and lookup resolution behavior.

Foreign Key Resolution

  • Entity foreign keys are resolved before write payload construction.
  • *_key input is the primary normalized form for portable CSV contracts.
  • Non-suffixed relationship fields exist to support human-readable source files and are resolved in the order key -> slug -> name.
  • Resolved matches are stored as canonical ids in the final write payload.

Lookup Priority

  • Lookup-backed fields prefer canonical key values.
  • If a UI/operator-facing label is supplied instead of a key, mismatch handling should resolve or remap it before the base write occurs.

Failure Behavior

  • Critical structural relationships must fail hard when unresolved. This includes competition organization/league/season and join-table sides such as competition/team.
  • Non-critical or ambiguous relationships can enter paused review/mismatch handling where the import workflow supports it.
  • Silent null persistence for unresolved documented relationships is not allowed in this contract.