Records created through your NetSuite integration go through NetSuite's API, not through NetSuite's own screens. Because of that, NetSuite's built-in duplicate-warning popup doesn't apply here — that feature only checks records entered directly into a NetSuite form. A separate check built into your NetSuite script is what actually prevents this for API-created records.

This article covers V10/V11 (LiveFluence). If you're on Velaro Workspace V20, see Automatic Duplicate Prevention for NetSuite Records (V20) instead — V20 handles this differently.

What this does

Before creating a new Lead, Prospect, or other record, the check looks for an existing record that already matches on a field you choose (commonly phone number). If a match is found, the existing record is used instead of creating a new one. If no match is found, a new record is created as usual.

Do you need this?

The search and record-creation settings described in Getting Accurate Names and Phone Matches in Your CRM Integration already solve the most common cause of duplicates: a phone number typed one way not matching a record saved a different way. If that's the pattern you're seeing, turning those on may be all you need.

This check adds coverage for the cases those two can't reach: a record entered into NetSuite by someone on your team rather than through a chat, or two records created close enough together that no search, however good, could have caught the second one in time. It runs inside NetSuite itself, at the moment a record saves, so it catches a duplicate regardless of what caused it.

Installing it

This check is part of the same NetSuite script your account already runs (velaro_restlet_v2.js, distributed as Bundle 107044). Confirm you're on the latest release of Bundle 107044 — the current v2 script build includes more sophisticated duplicate-prevention logic than earlier versions, and this check requires that current build. If you're not sure which version is installed, ask your account contact to confirm, then update it in your NetSuite File Cabinet the same way you installed the original script. Installing the latest version by itself changes nothing — it does nothing differently until turned on for a specific field.

Turning it on

Once the script is updated, turn on duplicate checking yourself in your NetSuite integration settings in the console. Three settings across two articles can all be used together with no conflict, since each acts at a different point in the flow:

1. Phone number country-code matching (search time) — from Getting Accurate Names and Phone Matches in Your CRM Integration
2. Combined-name field splitting (record creation) — also from that same article
3. This NetSuite-side duplicate check (save time, inside NetSuite itself) — described above, this article