"Document Unique Name" / "Developer Name must be unique" error when importing Apsona Items

Two causes & their fixes

1. The name is invalid. Salesforce requires the name to use only letters/numbers/underscores, start with a letter, have no spaces, no consecutive __, no trailing underscore, be ≤ 80 characters, and be unique.
→ Fix: Correct the offending names in the import file and re-run.

2. The name already exists (duplicate). The Apsona Items import does not de-duplicate — it creates new records. If the target org already has a component with that Developer Name, the import collides (common in export → import → sandbox-refresh → re-import pipelines). The document fails to store and the merge action can't link.
→ Fix (choose one before importing):

• a) Rename the existing components in the target org, or
• b) Rename the incoming components in the source org before exporting, or
• c) Use a naming convention with a date/time-stamp suffix (≤ 80 chars) on all merge actions and components in any export/import pipeline. (Recommended for teams that move items between orgs regularly.)

After importing

Re-open any filters that reference lookup fields and re-select the values — lookup IDs are org-specific and don't survive a cross-org import.