Skip to content

Parameter Reader

The Parameter Reader supplies an integration with two facts about itself. It emits a single record of two fields:

  • SYS.LASTRUNDATE — the date and time at which the integration last completed a run.
  • SYS.JOBID — the Integration Id.

Both are Text fields, and both are available to every transform connected beneath the reader. A Database Reader can use them to select only the rows that changed since the last run, and a reader on http(s) Url can put the date into its request. The reader is the entry point of an incremental integration.

This reader has nothing to configure. It has no Source section, because the values come from IMan's own record of the integration.

Setup

The Setup tab carries Transform Id and Description. The Source section every other reader has is absent.

Field Mapping

The Parameter Reader's Field Mapping tab: one transaction, Record, and a field grid holding SYS.LASTRUNDATE and SYS.JOBID, both Text and both ticked for import

Transaction

One transaction, Record. You cannot rename it, and it has no children because the reader is always flat.

Import

Both fields arrive ticked. Untick one through Edit to leave it out of the dataset.

Field Name and Type

The two fields are fixed: SYS.LASTRUNDATE and SYS.JOBID, both Text. You cannot add fields. If an integration needs its own parameters, keep them in a Lookup Table and reads them with a Lookup.

Where the values come from

The preview pane after a Refresh, showing one row with SYS.LASTRUNDATE 05/09/2026 22:33:12 and SYS.JOBID DOCSHTTP

SYS.JOBID is the Integration Id exactly as it appears on the Design tab.

IMan sets SYS.LASTRUNDATE at the end of a run that completed. A run that fails does not move it, and neither does a Refresh in the Designer. A preview reports the date of the last scheduled or command-line run, however many times you refresh the pane. IMan writes the date after it sends the audit report, so a run whose audit email cannot be delivered does not move the date either.

An integration that has never completed a run has no date. IMan uses the current time instead, so a first run reads "everything since now", not everything ever.

Using the values downstream

Reference the fields like any other, as %[SYS.LASTRUNDATE] and %[SYS.JOBID], in a Map, a Filter, a Database Reader's SQL Statement or an evaluated URL.

An HTTP reader that asks only for what changed

A JSON Reader connected beneath the Parameter Reader, Source http(s) Url, Evaluate Url ticked, with the Query Url:

"Invoices?Statuses=AUTHORISED&where=Date>=DateTime(" & Format(DateAdd("d", -1, %[SYS.LASTRUNDATE]), "yyyy,MM,dd") & ")"

DateAdd steps a day back from the last run and Format writes the date in the form the service wants. The preview's Trace tab shows the request that goes out:

GET https://api.xero.com/api.xro/2.0/Invoices?Statuses=AUTHORISED&where=Date>=DateTime(2026,09,04)&page=1

See Evaluate Url on the HTTP controller page for the rules an evaluated URL follows.

Audit

Supported counters

  • PROCESSED — incremented for the one record read.
  • INSERTED — incremented for the one record placed into the dataset.

Action on Transform Error

The setting and the rest of the tab are described on Transform > Audit.