NETSUITE_2

Issue

NetSuite rejected a SuiteQL query used to validate your connector setup. This can indicate restricted record access or an incompatible query, not necessarily a missing permission.

Resolution

1. Read the failed scope in the validation details. It identifies the employee connectivity check, role or permission queries, or an enabled content scope such as customers, vendors, transactions, or transaction lines.
2. In NetSuite, verify that REST Web Services is enabled for Representational State Transfer (REST) requests and that the OAuth 2.0 Client Credentials (M2M) mapping uses the intended application, certificate, service account, and role. See the NetSuite search connector setup guide.
3. Review the mapped role's access to the records named in the failed scope. Check role restrictions and related records used by the query. Access to transactions doesn't establish access to transaction lines.
4. If the response indicates rejected authentication, verify the M2M mapping and follow NETSUITE_1.
5. Retry validation after correcting access. If the role already has the required access, contact Glean Support to investigate query compatibility with your account's enabled features. Include the failed scope and HTTP status, but don't include credentials or record contents.

Timeouts, rate limits, temporary service failures, and inconclusive feature checks don't establish a missing permission. Wait and retry validation rather than granting broader access solely because of those failures.

For additional assistance, contact Glean Support.