History Window Overview
The History window is PrimeConnect's built-in audit trail. It automatically records every operation you perform — imports, exports, and deletions — with full details about what was processed, when, and what the outcome was.
You can access the History window in two ways:
- Click "History" in the top navigation bar from any screen in PrimeConnect.
- Click the "View History" link on the home screen, located below the main action buttons.
The History window opens as a dedicated view showing your complete operation log. No configuration is needed — history tracking is automatic and always on. Operations are stored in PrimeConnect's local database and persist across app restarts and updates.
Viewing Past Operations
Operations are displayed in a chronological list with the most recent operation at the top. Each entry in the list shows a summary row with the following information at a glance:
| Column | Description |
|---|---|
| Operation Type | The type of operation — Import, Export, or Delete. Each type is visually distinguished with a color-coded badge. |
| Entity Type | What was processed — e.g., Invoices, Customers, Bills, Journal Entries. |
| Filename | For imports: the name of the uploaded file. For exports: the name of the generated file. For deletions: not applicable. |
| Timestamp | The date and time the operation was performed, displayed in your local time zone. |
| Record Count | The total number of records processed in this operation (imported, exported, or deleted). |
| Status | The overall outcome — Success, Partial Success, or Error. See the Operation Statuses section below for details. |
The list supports scrolling through your entire operation history. There is no limit to how many operations are stored — every operation since you first installed PrimeConnect is available.
Operation Details
Click any operation in the list to drill down into the details for that specific batch. The detail view shows the individual record-level results, giving you complete visibility into what happened during the operation.
For imports: Each row shows the record that was processed and its status — whether it was successfully imported (created as a new record), updated (matched an existing record and was modified), skipped (duplicate or validation issue), or errored (could not be imported). Error rows include a specific error message explaining what went wrong. Rows skipped by a mapping rule show "Skipped by mapping rule: …" and count as neither imported nor failed. PrimeConnect also records which saved mapping (name and version) the import used, together with a snapshot of the mapping as it was applied, with the import's history entry.
For exports: The detail view shows the list of records that were included in the export file. Exports are read-only (they do not modify QuickBooks data), and each export entry is marked Completed, Partial, or Failed. A Partial export means QuickBooks stopped answering part-way — for example, a later page of a large export failed — so the rows fetched so far were kept and the QuickBooks error was recorded in the entry's notes.
For deletions: Each row shows the record that was targeted and whether it was successfully deleted or encountered an error. Error messages explain why a specific record could not be removed (e.g., active dependencies). Rows whose outcome QuickBooks could not confirm are shown separately from failed rows and carry the "QuickBooks outcome unknown" message — verify them in QuickBooks before retrying (see Interrupted Deletes).
Import details also show Reference created items for customers, vendors, classes, and other references created by that import. Each item keeps its QuickBooks identity and the first source row that needed it. These items are separate from the imported row totals and can be included in rollback.
Filtering History
As your operation history grows, filters help you find specific past operations quickly. The History window provides several filter options:
- By operation type: Show only imports, only exports, or only deletions. Useful when you want to review all imports without scrolling past exports and deletions.
- By entity type: Filter to show operations for a specific entity type — for example, only Invoice operations or only Customer operations.
- By date range: Narrow the history to operations performed within a specific time period. Helpful for finding operations from a particular day, week, or month.
- By status: Show only successful operations, only operations with errors, or only partial successes. This is particularly useful for identifying operations that had issues.
Filters can be combined — for example, you can show only "Import" operations for "Invoices" in "January 2026" that had "Partial Success" status. This makes it easy to locate specific operations even in a long history.
Operation Statuses
Every operation in the history log has an overall status that summarizes the outcome at a glance. The main statuses are:
| Status | Color | Meaning |
|---|---|---|
| Success | Green | All records in the batch were processed successfully. Every record was imported, exported, or deleted without errors. This is the ideal outcome. |
| Partial Success | Amber / Yellow | Some records in the batch succeeded, but others failed. For example, 95 out of 100 invoices were imported, but 5 had validation errors. Click into the operation details to see which records failed and why. |
| Error | Red | All records in the batch failed, or the operation was aborted before any records could be processed. This typically indicates a systemic issue — such as a QuickBooks connection failure or a fundamentally incompatible file format. |
| Recovery Required | Amber / Yellow | An import was interrupted after a request was sent, and QuickBooks could not confirm the result for one or more rows. Nothing is retried automatically — see Recovery Required below for how to resolve it. |
Export entries use Completed, Partial, or Failed. Partial means some rows were fetched before QuickBooks stopped answering; the error is saved in the entry's notes.
Retry entries exclude rows and transaction lines that completed in an earlier import. Those rows remain in the earlier entry; the retry's notes state how many were skipped. If an interrupted reference request stops submissions, unsent eligible rows count as errors and the entry records the stop reason. A confirmed not-processed request finishes with errors; an uncertain outcome remains Recovery Required. Only a user Stop action represents a cancellation.
The status is determined automatically when the operation completes. It cannot be manually changed. If you see a Partial Success or Error status, click into the operation details to review the per-record error messages.
Recovery Required
An import or delete batch is marked Recovery Required when a request was sent to QuickBooks but the reply never came back — for example, QuickBooks closed or a dialog interrupted the session. PrimeConnect does not resend the request, because the mutation may already have taken effect. The affected rows show "QuickBooks outcome unknown" and any later rows show "Not attempted".
A reply alone does not finish recovery. If a delete, rollback, or reference-creation reply is missing a requested result, cannot be matched to the request, or its outcome cannot be saved locally, PrimeConnect keeps the QuickBooks recovery information and stops further requests. Outcomes already confirmed and saved stay recorded; unresolved rows remain unknown. Verify those rows in the original company file before trying the operation again.
If an interruption happened after reference creation but before any import transaction was sent, recovery closes the batch as Failedwith the note "Interrupted after reference creation; no transactions were sent." Source-row totals stay at zero. Confirmed references remain visible as created items and are eligible for rollback when their identities and types are verified. Any reference with an unknown outcome still requires recovery first.
PrimeConnect saves the interrupted request's recovery identity before sending it, so automatic recovery can find the same QuickBooks request after an app restart or reconnect. Open the company file used for that request before retrying recovery. If you see a message asking you to open that company file first, switch to it and reconnect QuickBooks. A previous unresolved request can also block a new import, delete, rollback, or reference creation before anything is sent.
To resolve an interrupted import:
- Filter the list by status Recovery Required and open the import.
- Click Retry automatic recovery. PrimeConnect asks QuickBooks for the outcome of the interrupted request and resolves any rows it can confirm.
- For anything still pending, open QuickBooks and check whether the record exists. Then select the row and click Resolve selected item to record what you found.
- Re-import only the rows marked "Not attempted" or the rows you confirmed were never created.
To resolve an interrupted delete:
- Open the original QuickBooks company file. In Activity History, filter by Recovery Required and open the delete batch.
- Check each planned or unknown record in QuickBooks, select its row, and click Resolve selected item.
- Choose deleted only when you verified the record is gone. Choose error when it is still present or its outcome remains unknown, and explain your check in the operator note. The decision and note stay visible in the row's resolution details.
- Resolve every pending row. The batch then completes, and its recorded deleted and error counts are retained. Recovery Required batches have no completion time until their pending outcomes are resolved.
Delete batches have no Retry automatic recovery button; Activity History cannot retry a delete. After recovery is resolved, start a new delete only for records you confirmed are still present. If an outcome remains unknown, keep that uncertainty in the note and verify it before any retry. An interrupted delete can also appear here after an app restart when its submitted requests still have planned or unknown outcomes.
