An import field depends on an inaccessible saved search
Check whether the saved search still exists and whether the importing role can access it.
A saved search cannot be accessed
Message looks like
A Saved Search with Internal ID xxx does not exist
What it means
A custom field on the form pulls its value from a saved search that is inactive, deleted, or private to someone else.
Import context: General imports.
Check this first
Ask an admin to confirm the search exists, is active, and is visible to the importing user.
Show the steps
Steps for this error
- This appears when a custom field pulls its value from a saved search that is inactive, deleted, or private.
- Ask the administrator to confirm the search exists, is active, and that the importing user is in its audience or the search is public.
- Retry after access is confirmed.
Documentation checked September 16, 2026.
Related errors
- NetSuite import failed after the record was created
- NetSuite reports an unexpected error during import
- A language warning may be slowing the import
Book a free 30-minute look at your import error
Bring the error and your file to a screen share and I will dig into it live. Thirty minutes is usually enough to find what is wrong and tell you what fixing it takes. Sometimes that settles it on the call; when it does not, you leave with a straight answer instead of a mystery. No cost and no obligation.
An import that keeps failing is often the first visible sign of a larger setup problem. Most of my client work starts exactly here: somebody mid-import, a file that will not load, and nobody on their side to email. If a migration or implementation sits behind this error, that is the work I do every week.