Skip to main content

How do I resolve the "Duplicate punch pattern" alert?

Eclipse Classic does not enforce uniqueness of punch pattern names, so the same name can end up in the database more than once. Most often the copies differ only in upper/lower case (for example TRIM-24 and trim-24), usually after a pattern was re-imported or re-keyed with different casing. When this happens, Eclipse Pro raises the alert "Duplicate punch pattern in Eclipse".

Duplicated names are a problem because Eclipse Pro only syncs one of the copies — the one changed most recently — and silently hides the rest. Which copy wins can change over time, so scheduling results may not match what you see in the pattern editor.

Duplicates are never merged; the fix is to delete the copies you don't want.

Reviewing and resolving duplicates​

  1. Open Punching → Patterns in Eclipse Pro. When duplicates exist, a warning banner appears above the pattern list. (Clicking the alert in the alerts panel takes you to the same place.)
  2. Click Review Duplicates. The dialog lists every conflicting name with all of its copies, straight from the Eclipse database — including the copies Pro normally hides.
  3. For each group, compare the rows:
    • Active marks the copy Eclipse Pro currently syncs and shows in the pattern list.
    • identical content / different content indicates whether the copies have the same punches. When the content is identical it does not matter which copy you keep.
    • On Orders shows how many order items reference that exact spelling of the name.
  4. Click the delete button on the copy you want to remove and confirm. The remaining copy immediately becomes the pattern Eclipse Pro uses.
info

A copy that is referenced by order items cannot be deleted. Delete the other copy, or update the orders to reference the surviving name first.

warning

Deleting a pattern removes it from the Eclipse database (including its punches and stored solutions) and cannot be undone. If the copies have different content, verify which version is correct — for example by checking the punch count and the last-used date — before deleting.

Deleting patterns requires the pattern-editor role.