Endpoint results
See which endpoint completed, returned no data, was skipped or reported an issue.
Full and incremental pulls
Datplan can use the last saved position or checkpoint where a source endpoint supports it, reducing unnecessary repeat downloads while preserving a controlled full re-pull option.
Best for routine reporting. Datplan requests the data needed after the saved checkpoint where supported, merges the refreshed result into local data and records the run outcome.
Best for a deliberate clean rebuild. It can use more allowance and provider quota, so use it for stale or incomplete data, material source changes or support-led recovery.
Review the evidence
See which endpoint completed, returned no data, was skipped or reported an issue.
Review downloaded volume, completion state and notes that may affect the reporting dataset.
Compare the pull and transformed output where the source workflow provides reconciliation evidence.
Export sanitised run reports and diagnostic ZIP files for support without casually sharing raw business data.
Sync questions
No. Datplan uses the saved checkpoint only where the provider and endpoint support a reliable incremental behaviour. Other data may need a full or provider-specific refresh.
No. It can reduce repeated download volume, but all pulls remain subject to Datplan allowances, provider quotas, permissions and service availability.
Use it when local data appears incomplete or stale, a schema or source state has materially changed, or Datplan support recommends a clean rebuild. A standard sync is preferable for routine work.
The Windows app is free to download and includes Datplan Demo data, so you can test sync, dashboards, reporting grains and exports first.