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.
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.
Inspect the current identity
Use the inspection route available in the active product.
- ACAD/BCAD: use
ADACXDataandADACFindfor detailed drawing inspection. - DCAD: use
ADACEditto review one exact native element andADACAuditto identify duplicate or invalid IDs. - Confirm the ADACId belongs to the intended asset before changing it.
Create or clone safely
Let the allocation service reserve identities.
- Normal/bulk creation generates and reserves available IDs.
- ADACClone increments a compatible identity, uses an alias sequence or allocates an eight-digit value.
- When entering a custom ID, resolve any conflict shown by the form.
Import with reconciliation
XML, and CSV where supported, must preserve unique identities.
- Review duplicate groups in the import audit.
- Allow the importer to generate replacements where the workflow offers that choice.
- Check the final row or asset summary.
Correct deliberately
Identity changes affect audit results and attached files.
- ACAD/BCAD: use targeted Edit or the supported Clean renumber/revalue action.
- DCAD: edit the exact native element with
ADACEdit;ADACCleanis not available. - Confirm supporting-file references still follow the intended asset.
- Rerun audit.
3Identity allocation paths
Normal creation, clone and bulk/import operations use different candidate strategies but the same uniqueness goal.
| Feature or choice | Current behaviour |
|---|---|
| Uniqueness | Custom 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 allocation | Clone can use an asset alias plus the next available number when direct increment is not suitable.Readable organisation naming can be preserved. |
| Fallback allocation | Uses an available eight-digit numeric value when no increment/alias path succeeds.Every clone can still receive a valid identity. |
| Linked data | SupportingFiles 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.
Identity values are stored in AutoCAD XData and project-local reservation data.
BCAD uses the same allocation rules and Teigha XData storage.
Native 12d assets retain ADACId and exact model/element identity through bridge synchronization. Use ADACEdit, ADACFind and ADACAudit for inspection and correction; the DWG XData viewer and Clean workflow are not available.
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.