Data Management, Integration, and Reporting
This domain tests moving data into and out of NetSuite, integrating external systems, and building reliable reports. Expect questions on CSV import behavior, external IDs, APIs, authentication, saved searches, and analytics datasets.
Data management
- CSV Import Assistant maps source columns to fields; select fields usually need internal IDs or exact names, and dates must match account formats.
- Duplicate detection and external IDs control whether an import adds or updates records. External IDs are integration keys, not internal IDs.
- Data imports should run in sandbox first; large imports need chunking and error review.
Integration
- SuiteTalk SOAP/REST web services, RESTlets, and SuiteAnalytics Connect support different patterns. Use an integration user with a least-privilege role and OAuth 2.0 or token-based authentication.
- Concurrency and governance limits apply; handle retries and idempotency with external IDs.
Reporting
- Saved searches support criteria, results, formulas, summary types, and drill-down. SuiteAnalytics Workbook uses datasets for pivots and charts.
- Report access depends on role permissions and subsidiary restrictions.
Worked example
Load 5,000 vendor records from a legacy ERP. Reasoning: map the vendor external ID to a unique legacy key, use an Add/Update import, test 50 rows in sandbox, validate subsidiary and currency mappings, then run the full import and reconcile counts. Without external IDs, reruns create duplicates.
Traps
- Using display names for select fields can fail or create wrong matches.
- An Add import ignores existing records; Update requires a matching key.
- Saved search formula syntax differs by field type.
- Integration failures often come from permissions, not API syntax.