This topic describes the ingestion behavior and limits of the connector.

• The connector follows an All or None ingestion model when processing transactions from the NetSuite dataset.

  Either all transactions in the dataset are successfully ingested into Revenue or none of the transactions are ingested. Partial ingestion, where some transactions are processed successfully and others fail is not supported.

• The connector does not update transaction records back in NetSuite after ingestion. If updates are required in NetSuite, you must configure a workflow within NetSuite to perform those updates.

  You can use the information available in the Revenue Inbound Transaction staging table and leverage Revenue APIs to identify transactions that were successfully ingested into Revenue and transactions that encountered errors.