Column profiles

When you need a profile

Use a profile when a Name or String column stores another table’s row key, or when an empty row handle is valid in your data. Without a mapping, ordinary Name and String columns are not treated as foreign keys.

Write and load a profile

A Name or String property becomes a relationship only when you map it. Use authored top-level property names. A nullable handle rule changes empty-value semantics; the handle’s actual destination remains authoritative. For a row-handle rule, leave targetTablePath empty because the handle stores its own destination. The example below maps a Name or String property called TargetKey.

{
  "schemaVersion": 1,
  "maxRecords": 10000,
  "rules": [{
    "tablePath": "/Game/Data/Consumers.Consumers",
    "propertyPath": "TargetKey",
    "targetTablePath": "/Game/RowTetherExample/Targets.Targets",
    "nullable": true
  }]
}

All rule fields are required, source tables must be selected, and mappings must be unique. Store shared JSON in Config/RowTether. Save profile as writes only on request and preserves existing files. Future schema versions are rejected.

Top-level arrays and sets of DataTableRowHandle values are inspected. Nested references, maps, static arrays and unsupported containers are reported as omissions and may produce Partial coverage. Arbitrary Name properties are never inferred as foreign keys.

About schemaVersion

schemaVersion: 1 identifies the JSON profile format RowTether can read. It is not your Unreal version or a setting that improves the review. Keep this value at 1 when authoring a profile for this build. Unknown versions are rejected so the tool does not silently misread the rules.