1. Support arrow-right
  2. What's the difference between Manual Run and Manual Pull?

What's the difference between Manual Run and Manual Pull?

In ItemPath, you don't always have to wait for a scheduled sync to update your records. You can use Manual Run or Manual Pull to bring data in immediately.

While they both start an import, the main difference is where the data comes from.

Comparison:

Feature

Data Source

Use Case

Manual Run

Provided by User

You paste JSON data directly into ItemPath to be processed. ItemPath does not talk to your ERP during this.

Manual Pull

Fetched from ERP

ItemPath reaches out to your ERP to "search" for specific IDs you've requested.

Manual Run

Think of this as a "Bypass & Process" tool. You are providing the data yourself, which allows ItemPath to create/update records without needing to connect to your ERP.

  • How it works: You paste a block of JSON data into the Manual Run tab. ItemPath takes that data, "normalizes" it, and runs your mapping rules against it as if it had just come from the ERP.
  • Best for:
    • Fixing Errors: Re-running specific orders that failed previously by pasting their data back in.
    • Testing: Sending a small sample of data to see if your field mappings are working correctly.
    • Working around Downtime: If your ERP is temporarily down or slow, but you have the data exported, you can still use ItemPath to pass it to Power Pick.
  • Result: ItemPath creates records based solely on the text you pasted.

Manual Pull (OData)

This is a "Search and Fetch" tool. It's used when you don't want to run the entire integration, but instead need to grab one or two specific items.

  • How it works: You provide a specific identifier (like Order #12345). ItemPath reaches into the external system and asks specifically for that record, ignoring everything else.
  • Best for: Troubleshooting a single missing order or pulling in a specific high-priority record without waiting for a full system scan.
  • Requirement: Only available for OData integrations.