Sync Administration
FileMaker -> PostgreSQL synchronization status and controls
Table Sync States
Total = rows currently in the local DB · Last fetch = rows pulled from FM in the most recent sync cycle (often 0 when FM has no new changes since the watermark)
Loading...
Row-count drift (FM vs local)
Compares FileMaker’s total (via OData $count, or the Data API when FM_READ_TRANSPORT=dataapi) against Pulse’s exact local count per table. “Missing” = FM has rows Pulse never fetched (the gap an incremental sync can’t self-detect); fix with a Full Re-sync. “Stale” = Pulse retained rows FM no longer has (e.g. JOB|CTR’s UUID churn); a Full Re-sync auto-prunes these on FK-safe tables — the per-row Note says which. (Totals only: equal counts don’t prove the row sets match.)
Click Check row counts to compare every table against FileMaker.
JOB|CTR sync diagnostic
Fetches every JOB|CTR row from FileMaker and reports the ones the sync can’t persist — a required FK (__kf_job_id / __kf_ctr_id) that doesn’t resolve, or a duplicate (job, cost center) pair that collides on the unique constraint. Read-only: nothing is written to FileMaker or Postgres. Runs the same ~70s full walk a sync cycle does.
Click Run diagnostic to identify the rows blocking JOB|CTR from ever syncing clean.