NetSuite’s global search is powerful, but it can sometimes return large result sets, especially in accounts with many records. ExtendSync uses NetSuite’s global search APIs, so optimizing your NetSuite search practices will also improve ExtendSync’s performance when fetching records.
Below are tips to help you filter results more effectively and speed up search behavior in both NetSuite and ExtendSync.
🔎 Tip 1: Use Global Search Prefixes
NetSuite supports record-type prefixes that help narrow your search to specific record categories. Adding these prefixes before your search term ensures NetSuite returns only the intended record type.
Example
Searching for a customer named John Wick:
❌ Search:
John→ returns many results❌ Search:
cu: jo→ still broad✔️ Search:
cu: John Wick→ returns only matching customers
Why this helps
Using prefixes:
Reduces the size of the result set
Improves response time
Helps ExtendSync more accurately suggest relevant records
Common Global Search Prefixes
Here are some frequently used NetSuite prefixes that ExtendSync supports for Outlook and Gmail:
Prefix | Record Type |
opp: | Opportunity |
par: | Partner |
ph: | Phone Call |
sales: | Sales Order |
cam: | Campaign |
cash: | Cash Sale |
con: | Contact |
cust: | Customer |
emp: | Employee |
est: | Estimate |
ev: | Event |
exp: | Expense Report |
invo: | Invoice |
iss: | Issue |
it: | Item |
👉 Learn more about NetSuite Global Search Prefixes here.
Tip 2: Use More Characters
Provide as much detail as possible when searching. Longer search queries significantly reduce false matches.
Example
Instead of:
cu: jocu: john
Use:
cu: John Wick
This helps NetSuite precisely match names or IDs and speeds up the search process, especially helpful when ExtendSync attempts to match records automatically.
Tip 3: Transaction Number search
NetSuite searches work best when you provide specific identifiers such as full transaction numbers, prefixes, or unique details.
Because ExtendSync uses NetSuite’s global search, these same techniques improve Suggested Records, Autopilot accuracy, and manual search speed.
Instead of searching vaguely:
❌
sales 123❌
order 123❌
so 123
Use the proper prefix and full transaction number:
✔️
sales:12345✔️
sales: SO12345(if your org prefixes document numbers)✔️
SO12345(if SO is part of the actual number)
Why it works:
NetSuite matches the exact Sales Order and returns a single record instead of a long list.
Tip 4: Configure Search Filter + Adding Transaction Number in the Email Subject)
If an email subject includes a transaction number, ExtendSync can automatically match it.
Example subject:
Re: Invoice INV-20945 ready for approval
ExtendSync (and NetSuite) match optimally when the number is clearly formatted:
✔️
inv:20945✔️
INV-20945✔️
20945(if unique number pattern)
Learn about how you can configure what record types you want to be displayed on the auto-fetch:
Summary
ExtendSync relies on NetSuite’s search engine. Optimized searches:
Improve the speed of Suggested Records
Increase search accuracy when scanning email subjects and bodies
Reduce the chance of irrelevant results being returned