Practical method, written for people who already know Dynamics. Each guide shows the manual approach in full, including where it runs out. Nothing here needs Pathix to be useful.
The platform tracks declared metadata references, not logic. What that covers, what it cannot see, and a 90-second experiment to check it in your own environment.
The full manual method, worked against a real solution export: workflow XAML, flow definition JSON, canvas app PowerFx, plugin registrations, form scripts, and the two surfaces you cannot inspect by hand at all.
A diagnostic walkthrough: what audit attribution actually tells you, narrowing by deployment time and by what is bound to the table, the patterns usually responsible, and where the trail goes cold.
How service accounts accumulate privilege over the years, and what a role shared between humans and integrations actually grants once you work it through.
Renaming, retyping and deleting columns. Which changes are reversible, which are one-way doors, and how to order the work.
A dev-time linter and an environment-wide dependency graph answer different questions. Where the boundary sits, including what Solution Checker does better.
More on the way. If there is a question you keep having to answer the hard way, tell us and we will write it up: brian@pathix.app.