Cartographer: investigate where a column is used
Know your environment before you change it.
Before you start
Section titled “Before you start”Read the getting-started checklist. Confirm module access, the target records and the change owner before proceeding.
Investigate where a column is used
Section titled “Investigate where a column is used”- Choose the catalogue scope and ensure a scan has completed for the components you need to inspect.
- Search for the table or column by its logical name or label.
- Open where-used results and review each dependency, its confidence and scan time.
- Check unreadable, pending or truncated results before deciding whether a change is safe.
What to check
Section titled “What to check”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.
Go further
Section titled “Go further”Developer reference and extension boundaries · Module overview