whatagraph-deleting

To safely delete a Whatagraph data source, you must first verify usage status and evaluate dependency chains to identify any widgets, blends, or custom metrics relying on that entity, preventing unintended gaps in your marketing dashboards.

Removing a custom field from a Whatagraph report can cause dependent widgets and blends to break. A risk assessment evaluates dependency chains and validates user intent before executing destructive API calls to prevent accidental data loss.

Recovery depends on whether the deleted Whatagraph entity is soft-deletable or permanently removed. The framework distinguishes between soft-deletable items that can be restored and permanent actions that cannot be undone, guiding recovery paths.

The best way to check if a Whatagraph source is safe to remove is to validate its usage status and assess dependency chains, confirming whether any reports or custom metrics rely on that source before executing deletion.

Deleting a source in Whatagraph affects marketing analytics workflows because destructive API calls cascade across connected reports, blends, and custom fields. Evaluating dependency chains before deletion prevents system breakage and accidental data loss.