Postman collection
Customers Read

pixiGetChangedCustomers

Returns customers created or changed since a given point in time, optionally up to an end date, ordered by change date and limited to a maximum row count.

Reads the customer master table and returns all customers whose change date lies in the requested time window. This call is typically used for incremental (delta) synchronisation of customers into an external system.

  • The change date of a customer is its UpdateDate, or its CreateDate if the customer has never been updated. This value is also returned as column UpdateDate.
  • If To is omitted or empty, all customers with a change date >= Since are returned.
  • If To is set, customers with a change date between Since and To (both inclusive) are returned.
  • The result is sorted by change date in ascending order (oldest change first).
  • At most Rowcount rows are returned (default 1000).

For each customer the call returns the customer key, the keys of the billing and shipping address, a shipping lock flag, the CustomerOf value, e-mail address and name.

Notes

  • The table is read WITH (NOLOCK), so uncommitted changes may be returned.
  • The limit is applied with SET ROWCOUNT. Passing Rowcount = 0 removes the limit and returns all matching rows.
  • The check for an empty To compares against '', which SQL Server converts to 1900-01-01 00:00:00. Passing exactly this date as To is therefore treated like no end date.
  • Paging pattern: use the highest returned UpdateDate as the next Since. Because the filter is >=, the last record(s) are returned again; deduplicate by CustKey. There is no secondary sort key, so if more than Rowcount customers share the same change date, the loop cannot advance past them – increase Rowcount in that case.
  • ShipLock is 1 when the customer field SLocked is Y, otherwise 0.

Tables used

Customers · Read
SQL object:
dbo.pipiGetChangedCustomers
Updated at 2026-10-30