What syncs from Vantagepoint
| Entity | What it populates in FieldTime |
|---|---|
| Employees | Employee directory: name, ID, email, title, org, status, supervisor |
| Firms / Clients | Client names linked to projects |
| Organizations | Org names linked to employees and projects |
| Projects | Project list: code, name, WBS, client, org, type, status, dates |
| Phases | Phase codes and names nested under each project (WBS2) |
| Tasks | Task codes and names nested under each phase (WBS3) |
| Project PWDs | Per-project labor classification budgets and rates |
Initial setup
Open VP Sync settings
Go to Admin → VP Sync. If no credentials have been saved, you will see a Not connected state with a form to enter your VP details.
Enter your VP credentials
Fill in the following fields:
| Field | Description |
|---|---|
| Base URL | The root URL of your Vantagepoint API, e.g. https://vp.example.com/api/. |
| Username | Your VP service account username. |
| Password | The service account password. |
| Client ID | The OAuth2 client ID registered in Vantagepoint. |
| Client Secret | The OAuth2 client secret. |
| Integrated Database | The Vantagepoint database name (used for authentication). |
Test and save
Click Test & Save Credentials. FieldTime automatically tries all supported auth strategies to find one that works with your VP configuration. On success, it saves the working strategy and displays a Connected status with the auth strategy name and token expiry.
Supported auth strategies
FieldTime automatically detects the correct authentication strategy for your Vantagepoint instance. Supported strategies include Deltek password grant (integrated and non-integrated), HTTP Basic with various database parameter names, and form-body variants. You do not need to select a strategy manually.Configuring auto-sync
Auto-sync runs each entity on its own schedule. Enable it per entity or globally.Global switch
Toggle Automatic Sync Enabled to turn scheduled syncs on or off across all entities. When off, syncs only run when you click Sync Now.Per-entity settings
For each entity (Employees, Firms, Organizations, Projects, Phases, Tasks, Project PWDs), you can:- Enable or disable auto-sync independently.
- Set the frequency in hours (default: every 24 hours). FieldTime will run that entity’s sync when the configured interval has elapsed since the last successful run.
Incremental syncs
After the first full sync, FieldTime uses the last sync timestamp to request only records modified since the previous run (incremental sync). This makes recurring syncs much faster for large datasets. The first sync — or any sync where there are no local records yet — always fetches everything.Failure email notifications
Enable Email on Sync Failure and enter a Notification Email address to receive an email when any automatic sync finishes with afailed or partial status. The email includes the run ID, sync type, and up to 25 error details.
Running a manual sync
To sync any entity on demand:- In the VP Sync panel, find the entity row (Employees, Projects, etc.).
- Click Sync Now. A new sync run starts immediately in the background.
- The status badge updates to Running and a progress counter shows fetched/created/updated/skipped/errors in real time.
- When complete, the status changes to Completed, Partial, or Failed.
Cancelling a running sync
If a sync is taking too long or was started in error, you can cancel it:- Find the running sync run in the Sync Run Log (status: Running).
- Click the Cancel button on that row.
- FieldTime marks the run as
cancelledand stops processing as soon as the current batch finishes.
Sync run log
The Sync Run Log below the settings panel shows the most recent sync runs (up to 200). Each row includes:| Column | Description |
|---|---|
| Type | The sync entity and trigger type (e.g., automatic_employees, projects_manual). |
| Status | running, completed, partial, failed, or cancelled. |
| Started | When the run started. |
| Completed | When the run finished (blank if still running). |
| Fetched | Total records retrieved from Vantagepoint. |
| Created | New records added to FieldTime. |
| Updated | Existing records updated. |
| Skipped | Records skipped due to missing required fields or duplicate keys. |
| Errors | Records that caused an error during processing. |
| Error details | Up to 25 error messages from the run, visible on expansion. |
Sync run statuses
| Status | Meaning |
|---|---|
completed | All records processed without errors. |
partial | Some records succeeded and some failed (errors > 0 and created or updated > 0). |
failed | The run encountered errors and no records were successfully created or updated, or the run threw an unhandled exception. |
cancelled | An admin cancelled the run before it finished. |
