1. Run and read your first review

Goal: Locate two broken references and explain each one.

Before you start: The original tables and nullable-handles profile.

The idea you will use

Status, coverage and findings answer: did it finish, what was inspected, and what issues were found?

Predict before running

Does Completed mean C4 and C5 must have disappeared?

Build and check

Select the practice tables and learn to distinguish the review status from the data findings.

1. Open Tools → RowTether. If the editor groups studio tools, open Tools → Tether → RowTether.
2. In the Content Browser, select Targets and Consumers, then click Use selected DataTables.
3. Expand Rules → References and game rules and load Fixtures/nullable-handles.json. This profile marks Link as nullable; the empty handles in the CSV are intentional.
4. Wait for the review started by the profile to finish. Check its status and coverage before interpreting the results table.
5. The expected result is two current errors: C4 points to a Missing row that does not exist, and C5 has no destination table. Optional empty handles do not create errors.
6. Open both findings to locate the row and Link property in the source DataTable.

A Completed review can still contain errors: status describes the run; findings describe the relationships it found. If coverage is Partial, inspect the reasons before deciding a table is clean.

If the result differs, confirm the panel uses these tables’ object paths and that nullable-handles.json is loaded. This profile allows empty handles; it does not make missing rows or destination tables valid.

Check your reasoning

See the explanation

No. Completed describes execution. C4 points to Missing; C5 names a row without a destination table.

Your turn: Compare C5 with C6. Explain why nullable allows the empty second handle but does not validate the first.

Ready to continue when: you can locate source, property and destination and inspect coverage.