Skip to content

Imports one Sage Intacct object over your Sage Intacct connection into a project table, using the Intacct XML Gateway’s readByQuery/readMore operations to page through the full result set automatically. Pick the connection, the object, and any filters; the step pulls matching records and writes them, with no manual pagination to manage.

This is a generic canned step — one step type covers seven objects, from GL transaction and balance detail (GLDETAIL, GLACCOUNTBALANCE, GLENTRY) to dimension masters (LOCATION, DEPARTMENT, CLASS) and order documents (SODOCUMENT).

Field Required Notes
Sage Connection Yes The Sage Intacct connection to read through.
Target Table Yes The project table the results are written to. It is overwritten in full on every run.
Object Yes Which Intacct object to pull. One of GLDETAIL, GLACCOUNTBALANCE, GLENTRY, LOCATION, DEPARTMENT, CLASS, SODOCUMENT.
Filters No An array of {field, operator, value} clauses. Operators include eq, ne, gt, ge, lt, le. A range is expressed as two clauses on the same field — one ge, one le. Each object restricts filters to its own field+operator allowlist; an unsupported field or operator combination is rejected, not silently dropped.
Object What it pulls Common range filters
GLDETAIL GL transaction-line detail posting date (ge/le), amount (ge/le)
GLACCOUNTBALANCE Account balances by period period end date (ge/le)
GLENTRY Posted journal entry lines posting date (ge/le)
LOCATION Location dimension master — (equality filters only)
DEPARTMENT Department dimension master — (equality filters only)
CLASS Class dimension master — (equality filters only)
SODOCUMENT Sales order documents document date (ge/le)

Intacct’s XML Gateway returns results one page at a time. This step issues the initial readByQuery call, then follows with readMore calls using the result set ID Intacct returns, until every page has been read — so a GLDETAIL pull spanning tens of thousands of lines completes in one step run with no page-size tuning required from you.