Skip to content
PlaidCloud

Import Acumatica Entity

Description

Section titled “Description”

Imports one Acumatica contract-based REST entity over your Acumatica connection into a project table. Pick the connection, the entity type, and any filters; the step pulls matching records and writes them, with no OData query to author.

This is a generic canned step — one step type covers 18 entities, from master/reference data (accounts, subaccounts, customers, vendors, stock items) to transactional records (sales invoices, bills, sales orders, shipments).

Configuration

Section titled “Configuration”
Field Required Notes
Acumatica Connection Yes The Acumatica connection to read through.
Target Table Yes The project table the results are written to. It is overwritten in full on every run.
Entity Type Yes Which entity to pull. Default account. One of account, ledger, financial_period, branch, currency, currency_rate, subaccount, customer, vendor, stock_item, warehouse, employee, tax_category, sales_invoice, bill, sales_order, shipment, project.
Active Only No Default on. Filters to Active = true for entities that carry an Active flag.
Updated After No ISO date or datetime. Only rows changed after this are returned. This is a request-side filter with no persisted cursor — supply the cutoff yourself on every run. Blank pulls everything.
Filters No An array of {field, operator, value} clauses (eq, ne, gt, ge, lt, le, contains) or {field, from, to} ranges. Each entity restricts filters to the fields Acumatica can actually evaluate server side — an unsupported field is rejected, not silently dropped.
Section titled “Related”