SuiteAnalytics Datasets Can Now Be Transferred to NetSuite Data Intelligence (OAC)
SuiteAnalytics datasets can be imported into NetSuite Data Intelligence (Oracle Analytics Cloud) via the Data Transfer Setup page, but filters lose their criteria during transfer and custom fields must be pre-registered.
NetSuite Data Intelligence — the Oracle Analytics Cloud (OAC) integration layer — now supports importing existing SuiteAnalytics datasets so they can be analyzed alongside standard Data Intelligence data. This avoids manually recreating dataset definitions inside OAC.
What changed
- A new SuiteAnalytics Dataset tab appears on the Data Transfer Setup page.
- From that tab you can select one or more SuiteAnalytics datasets, review and cherry-pick individual fields, then trigger a transfer.
- Each transferred dataset automatically generates a corresponding workbook in Oracle Analytics Cloud. You can open it directly via Open Details → View in OAC.
- The Transferred Datasets list on the SuiteAnalytics Dataset tab shows transfer status and last-transfer timestamp for every dataset you have pushed.
Key limitations
Oracle's documentation is light on internals, but three constraints are explicit and worth flagging:
- Custom fields must be pre-registered. Any custom field that is not already available in NetSuite Data Intelligence will be silently dropped during transfer. You must first add those fields through Data Transfer Setup → Transferring Custom and Supplemental Fields before transferring the dataset.
- Filters transfer without criteria. Filter definitions are carried over, but the actual criteria values are stripped. After the transfer completes you must reapply every filter's criteria manually inside the Data Intelligence workbook or dataset. This is easy to miss and will produce unfiltered (potentially enormous) result sets in OAC until corrected.
- No automatic sync. Changes made to the source SuiteAnalytics dataset are not propagated to Data Intelligence. You must manually click Update Data on the transferred dataset to push changes. There is no webhook, scheduled sync, or SuiteScript hook mentioned in the documentation.
What to do
- Audit custom fields first. Before transferring any dataset, compare its field list against what is already available in Data Intelligence. Add missing custom/supplemental fields via Data Transfer Setup so they are not silently excluded.
- Document filter criteria. Because criteria are lost on transfer, record every filter's criteria values from the source SuiteAnalytics dataset before you initiate the transfer. Reapply them in OAC immediately after.
- Establish a refresh cadence. Since there is no automatic sync, decide on a manual refresh schedule. If your source dataset changes frequently, assign someone (or build a reminder) to click Update Data periodically. The documentation does not mention a SuiteScript or REST API endpoint to trigger this programmatically — verify with Oracle support if automation is required.
- Validate row counts post-transfer. Given the silent filter-criteria drop, compare record counts between the SuiteAnalytics dataset and the OAC workbook to confirm the transfer is returning expected results.
Open questions
The source documentation does not clarify several points that matter for larger implementations:
- Whether there is a record or field count ceiling per transfer.
- Whether the transfer respects role-based record-level permissions or transfers all data visible to the initiating user.
- Whether the Update Data action can be triggered via REST, SOAP, or SuiteScript (no API surface is documented).
- The exact SuiteAnalytics dataset types supported (e.g., whether datasets built on
N/queryworkloads, analytics-only record types, or cross-subsidiary joins qualify).
If any of these are blocking for your use case, open a case with Oracle Support or test in a sandbox account before relying on this in production.
Source: Oracle NetSuite Release Notes