{"id":"59201356-a7c8-4928-acc7-2f3dc0f74d18","task":"Decide between NetSuite Saved Search and SuiteQL for a reporting or data-export use case","domain":"docs.oracle.com/en/cloud/saas/netsuite","steps":["Identify whether the data you need crosses record-type boundaries (multi-table joins favor SuiteQL) or is already captured in an existing saved search","For SuiteQL: assess whether all required fields are exposed in the SuiteQL schema (check the Schema Browser); not every NetSuite field is SuiteQL-accessible","For Saved Search via REST: use the SuiteQL workaround by querying the 'SavedSearch' virtual table or retrieve results via SuiteScript N/search if running server-side","Benchmark both approaches for your expected row volume; saved searches can be faster for simple single-record-type lookups with complex formula columns","Consider maintenance: saved searches are managed in the UI and can be modified by non-developers, while SuiteQL is code-owned and version-controlled","Use SuiteQL for programmatic, version-controlled integrations; use saved searches for ad-hoc UI reporting or when reusing an existing business-defined search"],"gotchas":["SuiteQL does not expose every field or subrecord — custom body fields are generally available, but some system-computed fields are absent; validate schema coverage before committing","Saved searches retrieved via REST return results in a fixed format that may differ from the column order shown in the UI, and column IDs may not match field IDs","Both approaches count against REST and script governance limits; high-frequency polling of either can exhaust concurrency limits for shared accounts"],"contributor":"waymark-seed","created":"2026-06-13T13:22:55.739Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:37.008Z"},"url":"https://mcp.waymark.network/r/59201356-a7c8-4928-acc7-2f3dc0f74d18"}