Skip to content

Cartographer: investigate where a column is used

Know your environment before you change it.

Read the getting-started checklist. Confirm module access, the target records and the change owner before proceeding.

  1. Choose the catalogue scope and ensure a scan has completed for the components you need to inspect.
  2. Search for the table or column by its logical name or label.
  3. Open where-used results and review each dependency, its confidence and scan time.
  4. Check unreadable, pending or truncated results before deciding whether a change is safe.
The references behind a change.Planned view of a column’s usages, their sources and confidence.Screenshot placeholder
Reserved for an approved product capture. No demonstration is available here yet.

No matches is not proof that a component is unused. Dynamic references, unreadable components and incomplete scans can leave gaps.

Record the expected result and compare it with the actual outcome. Keep the configuration in draft or paused if the result or permissions are unclear. A screenshot slot is not evidence of release acceptance.

Developer reference and extension boundaries · Module overview