# PestRoutes tables and deletion checks

Review table and column choices, run resource refreshes, and understand future/full deletion checks and quota impact.

## Where to find it

Open **Account > Data Sources**, choose the connector when adding a source, or open its saved source detail.

## Select tables and columns

Open the PestRoutes source and choose **Edit tables and columns**. Review the recommended bundles or individual resources and selected columns, then choose **Save table choices**.

Existing enabled tables remain enabled. Unchecking a table in this chooser is not a pause or removal action; the save adds newly chosen resources and refines supported column selections. Inspect each existing sync's own controls when it should stop running.

## Choose the operation

| Operation | Purpose |
| --- | --- |
| Refresh | Update the selected table's source data through its refresh sync. |
| Future deletes | Reconcile the supported future-from date range for that resource. |
| Full deletes | Compare every source ID to find missing/restored records across the resource. |

Review the exact table, date boundary, and latest run before starting an operation. **Full deletes** requires a confirmation that the scan compares every source ID and can use substantial API quota. It is not an ordinary incremental refresh. Some operation cadence controls can be unavailable; use the controls offered for that operation rather than assuming every sync has editable cron settings.

Deletion checks update deletion and restoration markers in Topline's mirror; they do not delete records in PestRoutes. Future checks are supported for appointments and routes. Check the displayed future-from date before starting the scan.

## Inspect the result

The deletion-check impact shows records marked deleted or restored and, for future checks, the future-from boundary. Inspect those counts and errors before retrying. A successful scan does not mean other tables or file archives are complete. Use the source's API quota display when deciding when to run another full scan.

## Related guides

- [Source details](/docs/source-details)
- [Table details](/docs/table-details)
- [PestRoutes file and reporting context](/docs/data-sources-guide)