Custom fields pulling as internal IDs
If your saved search includes custom fields that have a dropdown or list of options, those fields will often return the internal ID of the selected option instead of the label. So instead of seeingIn Transit, you might see 3.
This happens because NetSuite stores custom field options as ID/label pairs — and the API returns the ID by default.
Workaround:
- In NetSuite, navigate to the custom field in question and export its options (internal ID + label) to a spreadsheet
- In Parabola, load that reference file alongside your saved search results
- Use a Combine Tables step (lookup join) to map the IDs to their labels
Summary saved searches (not supported)
A saved search becomes a “summary” search when any field in the Results tab has a Summary Type set (e.g., Group, Sum, Count, Max, Min). Summary searches aggregate data in the NetSuite UI, but that aggregation can’t be passed through the API. How to identify a summary search: Open the saved search in NetSuite and look at the Results tab. If any field has a value in the Summary Type column, it’s a summary search. Fix: Remove all summary types from every field in the Results tab. Save the search and re-run it in Parabola. If you need aggregated data, you can recreate the grouping logic in Parabola using the Sum by Group, Count by Group, or Merge Duplicate Rows steps after pulling in the raw records.Removing summary types may cause the search to return more rows than before (since grouping is what collapses duplicates). That’s expected — Parabola’s transform steps can handle the aggregation instead.
Large searches timing out
Saved searches that return too many rows will sometimes time out before the data fully loads. This is a NetSuite API limitation, not a Parabola issue. Signs of a timeout: The step runs but returns no data, or fails with a timeout error. Solutions:- Narrow the criteria — Add more filters to your saved search to reduce the number of rows returned. For example, filter by date range, status, or location.
- Split into multiple searches — If you need all the data, break one large search into several smaller ones (e.g., by month or by subsidiary) and stack the results in Parabola using a Stack Tables step.
Missing rows or columns
If your search runs successfully but returns fewer rows or columns than you expected, the most common cause is permissions.| Symptom | Where to check |
|---|---|
| Rows are missing | Transactions permissions on the role — make sure the relevant transaction types are included |
| Columns are missing | Lists and Custom Records permissions — the role may not have access to the related record types those columns reference |
Pulling custom fields via the API step (advanced)
The built-in Pull from NetSuite step can’t pull custom fields directly from the API — only the fields that are surfaced through saved searches. If you need to read or update custom fields that aren’t accessible via saved searches, an alternative is to use the Pull from API or Send to API step with OAuth authentication and NetSuite’s REST API directly. This is an advanced pattern and requires some API knowledge, but it’s worth knowing exists if you hit a ceiling with the built-in step.What’s next
With a solid Pull from NetSuite setup, we’ll shift to the other direction: sending data back into NetSuite. The next lesson covers the key prerequisite — understanding why internal IDs are required and how to build a lookup flow to handle them.FAQs
How do I tell if a saved search is a summary search?
How do I tell if a saved search is a summary search?
Open the search in NetSuite and go to the Results tab. Look at the Summary Type column — if any field has a value there (Group, Sum, Count, Max, Min), it’s a summary search. A search with even one summarized field will fail to load in Parabola.
Can Parabola pull formula fields from a saved search?
Can Parabola pull formula fields from a saved search?
No — formula fields are calculated inside the NetSuite UI and aren’t exposed through the API. If your saved search includes formula columns, those columns will simply be absent from the data Parabola receives. Recreate the calculation in Parabola using transform steps instead.
My search returns results in NetSuite but comes back empty in Parabola. What's wrong?
My search returns results in NetSuite but comes back empty in Parabola. What's wrong?
The most common causes:
- The search isn’t public — double-check the Public checkbox in the search settings
- Permissions — the integration role doesn’t have access to the record type the search is querying. Review the role setup from Lesson 2.
- Summary types — even one summarized field will cause the step to error or return nothing. Check the Results tab for any Summary Type values.
Is there a row limit for Pull from NetSuite?
Is there a row limit for Pull from NetSuite?
There’s no hard row limit, but large searches will time out before the data fully loads — this is a NetSuite API constraint. In practice, searches returning tens of thousands of rows are the most likely to cause timeouts. If you’re hitting this, narrow your criteria (date ranges, status filters, subsidiary filters) or break the search into multiple smaller ones and stack the results in Parabola.
Building challenge
Inspect the saved search you built in Lesson 3 for common data issues.You’re done when: Your saved search runs in Parabola without errors and the data looks reasonable — sensible row counts, readable values in the key columns.
Check for summary types
Open the saved search in NetSuite and go to the Results tab. Scan the Summary Type column — if anything is set, clear it and re-run the search in Parabola.
Look for ID-only columns
In your Parabola step, review the result columns. Any column showing raw numbers where you’d expect labels (like a Status, Class, or Vendor field) is returning an internal ID. Note which fields these are — you’ll map them using a reference table in Lesson 5.