Duplicate name in HaloPSA

What to do when a product cannot sync to HaloPSA because another item already uses the same name and HaloPSA requires unique product names.

Written By Victor Raessen

Last updated 9 days ago

What this error means

Error code: SB-HL-SYNC-000004

This error applies to products only. It appears when Salesbuildr tries to create or update a product in HaloPSA, but HaloPSA rejects it because another product (item) already uses that name.

This happens only when your HaloPSA instance has the setting that requires unique product names turned on. With that setting enabled, HaloPSA does not allow two items to share the same name. Salesbuildr cannot override that rule.

You may see a message like:

A record with this name already exists in HaloPSA. Names must be unique. This error originates in the HaloPSA PSA.

This is a HaloPSA validation rule, not a Salesbuildr bug. The product sync stops until the name conflict is resolved.

Where you see it

Open the product that failed to sync. On the product page, the sync status card shows the error and the product name HaloPSA rejected.

You may also see the error immediately after you save or edit a product that triggers a sync to HaloPSA.

Why it happens

Common situations:

  • A new Salesbuildr product matches an existing HaloPSA item — you created a product in Salesbuildr, but an item with the same name already exists in HaloPSA.

  • A renamed product now clashes — you changed a product name in Salesbuildr or HaloPSA and it now matches another item.

  • Duplicate data after imports or manual entry — the same product was added in both systems under the same name without being linked.

Salesbuildr cannot create a second HaloPSA item with the same name when unique product names are required in HaloPSA.

How to fix it

Choose the approach that matches your situation.

Option 1: Use the existing HaloPSA item

If the HaloPSA item is the correct one and Salesbuildr should use it (not create a duplicate):

  1. In HaloPSA, search for the name shown in the error and open the existing item.

  2. In Salesbuildr, open the product that failed to sync.

  3. Make sure Salesbuildr is linked to that HaloPSA item instead of trying to create a new one — for example by importing the product from HaloPSA if it already exists there, rather than creating a separate catalog entry with the same name.

  4. On the product page, click Retry on the sync status card.

Option 2: Rename the product to make it unique

If Salesbuildr and HaloPSA should keep two separate products:

  1. Decide which product should keep the current name and which should change.

  2. Rename the product in Salesbuildr or HaloPSA so the names no longer match.

  3. Return to the product page and click Retry on the sync status card.

Tip: Small, consistent naming differences help avoid future clashes — for example adding a location, internal reference, or MPN to one of the names.

After you fix it

  1. Open the affected product.

  2. On the sync status card, click Retry.

  3. Confirm the error clears and the sync status shows success.

When you need help

You can usually resolve this yourself by renaming or linking products. Contact Salesbuildr support if:

  • You cannot find the duplicate item in HaloPSA but the error keeps returning.

  • You are not sure whether to merge products or keep them separate.

  • Retrying after a rename or link still fails with the same error.

Include the error code (SB-HL-SYNC-000004), the product name shown in the sync status, and confirm that unique product names are enabled in your HaloPSA instance.

See also