Published at: 2025-10-30
How to Verify Third-Party Data Retrieval by Filtering Work Order Report via Read API
First, you need to understand the Integration Platform’s call Report for reading third‑party APIs:
- Each time the third‑party bulk query API is called, it queries data within a specific time range — shown in the column “Query Data Time Range”.
- “Request Parameters” shows the parameters passed for this query. Here you can determine which date field the query used. For example, the standard API queries by the record’s last modified time; if the API has been adjusted, verify inside the API configuration.
- “Response” shows the data the third party returned to the Integration Platform. Use this to confirm exactly what data the third party returned.

-
Use the Data Reconciliation tool to first identify third‑party records (IDs) that were not read into the staging table. Sample several of those IDs and follow the steps below to locate the issue.
-
Because log volume is large, narrow the search by confirming the data date/time used for the query:
1) Determine which date/time field the API uses for querying. Go to the Integration Flow detail page -> Run Overview -> Read API Calls, open the latest log entry’s Details -> Request Parameters to check.

2) Using the returned record IDs, inspect those records in the third‑party system to check the relevant fields — mainly the queried fields and the business date/time field identified above. Example:
| Record ID | Item Code | Item Name | Last Modified Time (FModifyDate) |
|---|---|---|---|
| 1001 | CH1849 | Apple | 2022-12-06 11:05:51 |
3) Use the record date/time to narrow the range of call Report entries.
This indicates the record should have been returned within these three calls.

- After narrowing the log range, search the “Response” content to verify whether the record was returned.
If the search finds nothing, the API did not return that record.

If the search finds the record, the API returned data — then raise a Work Order to resolve the missing data issue.
