1Overview

ADACId is the project-facing identity that ties an asset's geometry, attributes, report entry and supporting-file folder together. infrADAC reserves generated values, rejects duplicate custom values and preserves the native object mapping used by each host.

Use this guide when

Planning an ID convention, resolving duplicates, importing data or diagnosing supporting-file and audit mismatches.

2Identity tasks

Choose the task that matches the identity issue; inspection, creation, import and repair are separate workflows.

01

Inspect the current identity

Use the inspection route available in the active product.

  1. ACAD/BCAD: use ADACXData and ADACFind for detailed drawing inspection.
  2. DCAD: use ADACEdit to review one exact native element and ADACAudit to identify duplicate or invalid IDs.
  3. Confirm the ADACId belongs to the intended asset before changing it.
Inspect the current identity in the current infrADAC interface
Image placeholderInspect the current identityShow the current infrADAC interface and result for: Use the inspection route available in the active product.PLACEHOLDER_IMAGE_URL_ADAC_ID_AND_DATA_INTEGRITY_STEP_01
Inspect the current identity shown at this exact stage of the task.
02

Create or clone safely

Let the allocation service reserve identities.

  1. Normal/bulk creation generates and reserves available IDs.
  2. ADACClone increments a compatible identity, uses an alias sequence or allocates an eight-digit value.
  3. When entering a custom ID, resolve any conflict shown by the form.
Create or clone safely in the current infrADAC interface
Image placeholderCreate or clone safelyShow the current infrADAC interface and result for: Let the allocation service reserve identities.PLACEHOLDER_IMAGE_URL_ADAC_ID_AND_DATA_INTEGRITY_STEP_02
Create or clone safely shown at this exact stage of the task.
03

Import with reconciliation

XML, and CSV where supported, must preserve unique identities.

  1. Review duplicate groups in the import audit.
  2. Allow the importer to generate replacements where the workflow offers that choice.
  3. Check the final row or asset summary.
Import with reconciliation in the current infrADAC interface
Image placeholderImport with reconciliationShow the current infrADAC interface and result for: XML, and CSV where supported, must preserve unique identities.PLACEHOLDER_IMAGE_URL_ADAC_ID_AND_DATA_INTEGRITY_STEP_03
Import with reconciliation shown at this exact stage of the task.
04

Correct deliberately

Identity changes affect audit results and attached files.

  1. ACAD/BCAD: use targeted Edit or the supported Clean renumber/revalue action.
  2. DCAD: edit the exact native element with ADACEdit; ADACClean is not available.
  3. Confirm supporting-file references still follow the intended asset.
  4. Rerun audit.
Correct deliberately in the current infrADAC interface
Image placeholderCorrect deliberatelyShow the current infrADAC interface and result for: Identity changes affect audit results and attached files.PLACEHOLDER_IMAGE_URL_ADAC_ID_AND_DATA_INTEGRITY_STEP_04
Correct deliberately shown at this exact stage of the task.

3Identity allocation paths

Normal creation, clone and bulk/import operations use different candidate strategies but the same uniqueness goal.

Feature or choiceCurrent behaviour
UniquenessCustom entries are checked against drawing/reserved IDs; bulk and clone workflows reserve candidates before commit.Concurrent or partial operations are less likely to collide.
Alias allocationClone can use an asset alias plus the next available number when direct increment is not suitable.Readable organisation naming can be preserved.
Fallback allocationUses an available eight-digit numeric value when no increment/alias path succeeds.Every clone can still receive a valid identity.
Linked dataSupportingFiles cache folders include AssetType and ADACId; supported edit or repair workflows reconcile identity-linked paths.Documents should not remain tied to a stale ID.

4Before you begin

  • Agree an organisation/project identity convention when custom IDs are allowed.
  • Audit before mass renumbering and back up the project/cache.
  • Do not edit raw asset data or unique-ID files outside infrADAC.

5Product differences

The task is shared where possible, but selection, interface integration and model operations follow the host shown below.

infrADAC ACAD

Identity values are stored in AutoCAD XData and project-local reservation data.

6Troubleshooting

The form says the ADACId already exists

Choose a genuinely unique project value. Do not delete the existing asset merely to reuse its identity without checking deliverable history.

Audit finds duplicates after import

Identify every duplicate using the tools available for the active product, decide which identity is authoritative and correct each affected asset with a supported edit or repair workflow.

Supporting files disappeared after an ID change

Inspect the cache for the old AssetType (ADACId) folder, then use a supported Edit or repair workflow to reconcile paths or reattach the files. Avoid manual folder renames without updating asset data.

7Related guides