infrADAC user manualAsset data

Attach and Export Supporting Files

Keep supporting documents associated with the correct asset identity and project, then package them predictably during export.

Software covered ACADinfrADAC ACADBCADinfrADAC BCADDCADinfrADAC DCAD
Attach and Export Supporting Files in infrADAC Video walkthroughAttach and Export Supporting FilesWatch on YouTube

1Overview

Supporting files are selected in asset attribute forms, committed into the infrADAC temporary project cache under an AssetType (ADACId) folder and referenced through asset data. Export validates and packages committed files.

Use this guide when

An asset requires photographs, certificates, schedules or other receiver documents.

2Attach, commit and package files

Treat the file attachment and the asset identity as one transaction.

Step 1
01

Open the asset attributes

Create or edit the target asset.

  1. Use the asset creation form or run ADACEdit.
  2. Confirm the asset type and ADACId.
  3. Locate ComponentInfo SupportingFiles.
Open the asset attributes in the current infrADAC interface
Image placeholderOpen the asset attributesShow the current infrADAC interface and result for: Create or edit the target asset.PLACEHOLDER_IMAGE_URL_SUPPORTING_FILES_STEP_01
Open the asset attributes shown at this exact stage of the task.

3Supporting-file lifecycle

The cache, XData reference and export package must agree.

Feature or choiceCurrent behaviour
Cache layoutUses a project folder with per-asset AssetType (ADACId) subfolders.Files remain unambiguous when several assets use the same source name.
Non-colliding namesDuplicate source file names receive a safe non-colliding destination path.One upload does not overwrite another silently.
Identity changesEdit can reconcile folders and references when ADACId changes; ACAD/BCAD also provide Clean repair actions.Documents stay associated with the corrected asset.
ExportCreates a supporting-files ZIP only when committed, valid files exist; package export can include it with XML, report and DWG.Deliverables are complete without empty archives.

4Before you begin

  • Set a stable project Name and writable project context.
  • Ensure the asset has a non-blank ADACId.
  • Use final, readable file names and remove sensitive or unrelated documents.

5Product differences

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

infrADAC ACAD

Files are managed by the Windows host while asset references live in AutoCAD XData.

6Troubleshooting

The form says ADACId is blank

Assign or generate a valid ADACId before saving supporting files. The cache folder cannot be committed without an identity.

A supporting file is missing during export

Edit the asset and replace the file, or remove the stale reference. ACAD/BCAD can use Clean cache validation to identify other missing/orphan entries; DCAD uses Edit and direct cache review.

Files are under the old project or ADACId folder

Save Project Details and the asset edit again. ACAD/BCAD can also use ADACClean identity cleanup; DCAD does not expose Clean.

7Related guides

Documentation hubinfrADAC User ManualThe complete infrADAC task and command library. ReferenceComplete Command ReferenceSupported infrADAC commands and 12d macros, filtered by product. Asset creationGenerate Assets from Existing GeometryCreate a compatible standard or supplementary asset from existing CAD or 12d geometry, or attribute that geometry in place. Asset maintenanceEdit and Inspect AssetsEdit asset attributes and use the inspection tools available for the active product. Asset creationClone AssetsDuplicate assets with new identities using the placement modes supported by the active product. Asset navigationFind AssetsSearch the active design by class, asset type, ADACId or model location and frame the result.