Use this article to troubleshoot common issues when using NetSuite with Zapier. Find your problem below and follow the steps to fix it.
Available on plans:
Free
Professional
Team
Enterprise
Issues in Zap workflows
These issues relate to trigger and action behavior specific to Zap workflows.
Symptom
Your Zap using NetSuite's New Record (Saved Search) trigger fails during a poll, or the trigger step fails when you click Test trigger in the Zap editor. The error message reads something like Invalid API Response: Got two or more results with primary key of {"id":"..."}.
Causes
- Your saved search returns more than one row for the same record. For example, it returns one row per line item on a shipment, bill, or transaction.
- The trigger deduplicates on the record's Internal ID by default, so every row that shares the same Internal ID collides.
How to fix it
- In the Zap editor, open your New Record (Saved Search) trigger step.
- Under Unique Key Fields, select the columns that together identify a row uniquely. This is usually the record's Internal ID plus a line-level column, such as a line item ID.
- If a suitable line-level column is not available in the dropdown, add it to the saved search in NetSuite, then reselect the saved search in the trigger step to refresh the list of available columns.
- If you're using a Transaction-type saved search, also add a filter for Main Line with Description set to true. If your search includes Journal records, add a Line filter with Description set to 0.
- Retest the trigger.
Avoid selecting fields that change over time (such as a status or date) for Unique Key Fields. Editing a field used in the unique key causes that row to trigger again as if it were new.
Still need help?
If this article did not fix the issue:
- Ask in the Zapier Community. Get advice from experienced Zapier users.
- Learn more about getting help and support with Zapier.