Skip to main content

Troubleshooting: "A resource with the same name or identifier already exists" error when uploading in ExtendInsights

Fix the "A resource with the same name or identifier already exists" upload error in ExtendInsights when no duplicate record exists in NetSuite, caused by leftover hidden helper columns in the upload sheet.

If you upload records from ExtendInsights and see "A resource with the same name or identifier already exists" even though the Internal ID is blank and the External ID or Transaction ID does not exist in NetSuite, the error is often not a real duplicate.

Why this happens

ExtendInsights adds a few hidden helper columns to the end of the table during an upload, refresh or delete. If they are not removed when the operation finishes, the next upload tries to create them again and fails with this error. Leftover content just outside the template range, such as formulas, #REF columns or stray text, can cause the same error.

Fix 1: Clear the extra columns

  1. Save a backup copy of your workbook.

  2. Unhide all columns on the upload sheet.

  3. Delete any columns to the right of the template table, including columns that look empty and any that contain formulas or #REF errors.

  4. Try the upload again.

Fix 2: Rebuild the template on a new sheet

If the error continues, refresh the template fields, load the template onto a new worksheet, and copy only your data values into it (not formulas or formatting). Then retry the upload.

Fix 3: Refresh the record metadata

If your organization uses ExtendInsights metadata customizations, such as field dependencies or account search workarounds stored in the Celigo CENS Metadata Setting Record, ExtendInsights may be working from outdated cached metadata for that record type. Refreshing the record metadata reloads all standard fields, custom fields, and customizations for the record type, and does not affect your existing data. Then retry the upload.

See FAQ: How to Refresh Metadata in ExtendInsights (Fields, Picklists, and Customizations) (Option 2) for step-by-step details.

Still seeing the error?

Also check that the External ID and Transaction ID are not already used by another record in NetSuite. You can paste the ID into NetSuite's global search to confirm. If the error persists after the steps above, contact support and tell us which record type you are uploading and which of these steps you have already tried.

Related Articles
Did this answer your question?