The platform decides what a delete takes with it one relationship at a time. Account has forty-seven, each with its own delete behavior: some delete the related records, some only clear the link. By hand, you follow every one that deletes into that table's relationships, and theirs.
Not unlinked. Deleted. So are their emails, tasks, appointments and notes. Pathix starts from the table and reads the cascade from each relationship's delete behavior, four levels down.
Engagements stay, and so do permit applications and the account's child accounts. Their link is cleared, and nothing below them is touched, so Pathix doesn't follow them any further. Most of what's left is the platform's own bookkeeping: sync errors, duplicate-detection results, mailbox tracking folders.
Two levels down, feedback a contact created is set to restrict. If one of those contacts ever left feedback, the platform refuses the delete, and because a cascade delete is one transaction, one refusal rolls all of it back. Pathix reads relationships, not records, so it can't say whether that feedback exists. Only that, if it does, the delete stops.
One Pathix call returns the cascade, and the relationships that can refuse it. The Dataverse MCP can read each relationship's settings. Following them four levels down is left to your agent.
A read-only metadata scan of your environment that reads the logic inside the components: compiled plugins, flow definitions, workflow XAML and scripts.
How it works →A 30-minute walkthrough on a pre-scanned demo environment. No access to your tenant, nothing to install.