Scenario
A custom record has been created successfully, but users cannot find it using NetSuite Global Search.
Common symptoms include:
- The record exists and can be opened directly.
- Saved searches return the record correctly.
- Administrators can find the record, but standard users cannot.
- Newly created records do not appear in search results.
This issue is commonly related to custom record configuration, permissions, or search settings.
Solution
Review the custom record setup and access configuration that controls Global Search visibility.
Common causes include:
- Global Search Setting Disabled
- Open the custom record type configuration.
- Verify the option allowing the record to appear in Global Search is enabled.
- Record Permissions
- Users must have sufficient permission to the custom record type.
- If the role cannot view the record, it typically will not appear in Global Search.
- Access Type Restrictions
- Review whether the custom record uses permission restrictions or role-based access that limits visibility.
- Record Is Inactive
- Inactive records may not appear in search results depending on account behavior and filtering.
- Search Keywords or Naming
- Global Search prioritizes record names, IDs, and indexed fields.
- Very generic or duplicate names may make records harder to locate.
- Recently Created Records
- New records or recent customization changes may not appear immediately while indexing updates.
- Custom Record Configuration
- Some custom record types are configured primarily for backend processing and may not behave like standard searchable records.
Notes
Global Search visibility can differ between users depending on role permissions and subsidiary access. A record visible to an Administrator may still be hidden from other users.
When troubleshooting:
- Test using the Administrator role.
- Verify the custom record type settings directly.
- Compare behavior across roles.
- Confirm the record itself is active and accessible.
- Test searching by exact record name or internal ID references where applicable.
Testing configuration changes in a sandbox environment is recommended before updating production customizations.