NetSuite saved searches with a Type of System Note or Login Audit Trail cannot be used in an integrator.io NetSuite export because NetSuite does not expose these record types through the APIs used by integrator.io. Use this article if either record type is unavailable in the export's Record type list. It explains this limitation and provides three supported alternatives for including this data in your flows.
System Notes and Login Audit Trail availability in the Record Type dropdown
You can create and run a NetSuite saved search with a Type of System Note or Login Audit Trail directly in the NetSuite UI. But when you try to use that same saved search in an integrator.io NetSuite export:
- The record type doesn't appear in the export's Record type dropdown list.
- The saved search can't be selected or executed from the export.
NetSuite API limitations for System Notes and Login Audit Trail
NetSuite doesn't expose System Note or Login Audit Trail as standalone record types through its Web Services (SOAP) or REST APIs, which are the same APIs integrator.io uses to enumerate record types and execute saved searches. Because these record types aren't exposed there, integrator.io can't list or run saved searches based on them.
This is expected behavior, driven by NetSuite's API capabilities rather than an integrator.io configuration issue. There's no export setting that makes these record types appear.
Workarounds for exporting System Notes and Login Audit Trail Data
Depending on the data you need, one of the following three approaches usually works.
Option 1: Access System Note fields through a parent record
Some System Note fields are available as joined fields when you export a supported parent record, such as a transaction or entity record.
- In the saved search's column list for the parent record, expand the System Notes join.
- Add the fields you need. For example: Date, Set by, Field, Old value, and New value.
Use this option when:
- You need audit context for a specific record or record type that integrator.io can export.
- You don't need the full system-wide audit history.
This option isn't sufficient when:
- You need a complete audit trail across all record types, or audit events for record types that aren't directly exportable.
Option 2: Schedule the saved search in NetSuite, then ingest the file
NetSuite can schedule a saved search to deliver its results as a CSV file, either by email or to the NetSuite file cabinet. You can then retrieve that file in integrator.io with a file-based export and process it like any other data source.
Use this option when:
- You need the full result set that the System Note or Login Audit Trail saved search returns.
- A scheduled cadence, rather than real-time sync, is acceptable.
Option 3: Use SuiteAnalytics or NetSuite Analytics Warehouse
If your account has SuiteAnalytics Workbook or NetSuite Analytics Warehouse, audit-related datasets are typically available there for querying or extraction. Use this option when you need ongoing, analytics-grade access to audit data and a scheduled CSV export doesn't fit your use case.