1Overview
Export requires initialisation and valid Project Attributes, runs the same profile audit used by ADACAudit and enables export only when the audit passes. Outputs can be written individually or in a consolidated ZIP package. DCAD scans infrADAC and native nested Adac elements, groups them by logical ADACId, removes exact duplicate geometry and passes current live 12d geometry to the same XML writer used by ACAD and BCAD.
Submitting, reviewing or archiving an ADAC project deliverable.
2Before you begin
- Save and back up the project.
- Run audit under the receiver profile and resolve intended failures.
- Choose an export folder and base file name that meet receiver conventions.
- Close old report/output files that may lock the destination.
3Export outputs and gates
The chosen package mode changes paths and packaging, not the underlying audit requirement.
| Feature or choice | Current behaviour |
|---|---|
| Audit gate | Export remains disabled until the selected-profile audit passes and a location exists.Invalid submissions are not produced accidentally. |
| Individual outputs | Writes XML and report plus the active product's supported model and supporting-file outputs.Each available deliverable can be transmitted separately. |
| Package ZIP | Packages the generated output files and stores package-relative references in export metadata.One controlled file can contain the complete submission. |
| Export metadata | Writes output paths or package references, ADAC version and current date/time into the project/export context.Deliverable provenance remains inspectable. |
| DCAD materialization | Groups native elements once by ADACId, removes exact duplicate native geometry, requires current live vertices and sends the remaining objects through the shared XML writer.Stored compatibility geometry is not substituted when a native element no longer supplies live geometry, and no separate 12d-only XML schema is produced. |
4Audit and build the deliverable set
Configure the submission scope in the audit panel, then verify the contents of every generated file.
Start export and validate project data
The command blocks uninitialised projects.
- Run
ADACExport. - If required Project Attributes are missing, choose Yes and correct them.
- Choose the export XML path and file name.
Pass the export audit
Configure the exact submission scope.
- Select the receiver profile.
- Choose Full Technical Report or concise report.
- Set the Audit Report/XML feature-class filter.
- Review failures until Audit Status passes.
Choose output options
Packaging and any available conversion controls are enabled only after a pass.
- Use Convert Complex Geometry only when the active product offers it, complex assets were detected and conversion is required.
- Enable Package Export (Zip) for one consolidated package, or leave it off for individual files.
- Select Export.
Verify every deliverable
Do not rely only on the success message.
- Confirm the XML and AuditReport DOCX plus the model/supporting-file outputs offered by the active product.
- Package export: open the ExportPackage ZIP and confirm the expected entries.
- Use Report or Open Folder from the success dialog.
- Retain output and audit evidence together.
5Product differences
The task is shared where possible, but selection, interface integration and model operations follow the host shown below.
Exports selected/filtered AutoCAD assets to DWG and generates XML/report/supporting outputs.
BCAD produces the corresponding DWG-compatible output through Teigha and shared export helpers.
DCAD normalises infrADAC and native nested Adac records, groups them once by ADACId, removes exact duplicate current geometry and passes live native objects to the shared XML writer. Missing live geometry is reported rather than synthesised, and no separate 12d XML format is used.
6Troubleshooting
Export is disabled
Complete the output path and resolve every audit failure under the selected profile. Conversion/package options also require a passed audit.
The report or ZIP is in use
Close the destination in Word, Explorer preview or another archive tool, then retry so infrADAC can replace it safely.
Supporting files are absent
No valid committed files were found. Repair asset references/cache first; empty supporting archives are intentionally removed.