Testing Autodesk Assistant in Civil 3D 2027.1: Drawing Health, DREFs, XREFs, and the Future of Proactive CAD QA and Help

MASTER DWG & CIVIL 3D DATASET HEALTH CHECK — FULL REFERENCE AUDIT · XRef · DRef · Mixed Loops · Underlays · Point Clouds · Data Links
Perform a fully autonomous, multi-pass health check on the current drawing and every file in its complete reference tree — XRef, DRef, and all other reference
types. Do not stop at the first level; recursively walk every branch of every reference tree until all leaves are reached or a loop is detected.
Execute all checks below in order. Do not skip any section. Report every finding
using the exact flag symbols defined. Produce all output as structured markdown
tables with a written summary per section.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 0 — DRAWING IDENTITY & CONTEXT
━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Report the following for the root drawing before any reference checks begin:
Full absolute file path of the current (root) drawing
Drawing filename
Drawing units (length unit, angle unit)
Civil 3D Data Shortcut project folder path (if configured)
Data Shortcut XML file path (_Shortcuts folder location)
Total block definition count
Total XRef count (DWG references)
Total DRef count (Civil 3D data references — isReferenceObject = true)
Total underlay/image/point cloud/data link count
This section establishes the audit baseline. Flag if:
⚠️ Data Shortcut folder is not configured or cannot be found
⚠️ Drawing is stored on a mapped drive (risk of path resolution failure)
⚠️ Drawing path contains spaces or special characters (known path risk)
❌ Drawing units are inconsistent with project standard
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 1 — XREF HEALTH (External DWG References)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Query ALL block definitions where isFromXref = true across the root drawing.
For each XRef found, recursively open its resolved file path and repeat the
same query to discover nested XRefs. Build a complete multi-level XRef tree.
For every XRef node in the tree, report:
Reference Name (block definition name as stored)
Attachment Type (Attachment | Overlay)
Load Status (Resolved | Unresolved | Unloaded | Not Found)
Saved Path (xrefPathName — as stored in the drawing)
Resolved File Path (xrefResolvedFileName — actual located path)
Path Type (Absolute | Relative | No Path / Filename Only)
Nesting Level (0 = direct child of root, 1 = grandchild, etc.)
Parent Drawing (which .dwg hosts this XRef directly)
Propagates to Root (Yes | No — Attachment type at any level propagates)
FLAG RULES — apply to every XRef row:
❌ xrefIsResolved = false AND xrefIsUnloaded = false → Missing / Not Found
❌ xrefStatus = FileNotFound or FileAccessError → Broken reference
❌ Saved Path ≠ Resolved File Path → Path mismatch (drawing may break
when moved or shared)
❌ Resolved File Path is null or empty → Cannot locate file
⚠️ Attachment Type = Attachment → Propagation risk; can cause loops when
this drawing is itself XRef'd into a parent
⚠️ Path Type = Relative → Will break if root drawing is relocated
⚠️ Path Type = Filename Only (no folder) → Relies on search path; fragile
⚠️ xrefIsUnloaded = true → Intentionally unloaded; may hide issues
⚠️ Nesting Level ≥ 3 → Deep nesting increases loop and performance risk
✅ Resolved = true, paths match, Overlay type, absolute path → Healthy
Output format — one row per XRef per drawing it appears in:
| Level | Reference Name | Type | Status | Saved Path | Resolved Path |
Path Type | Parent Drawing | Propagates | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 2 — DREF HEALTH (Civil 3D Data References)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Query ALL Civil 3D objects where isReferenceObject = true across the root
drawing AND every drawing reachable via the XRef tree. Check the following
Civil 3D object types for DRef status:
civil3d_surface, civil3d_alignment, civil3d_profile, civil3d_corridor,
civil3d_pipenetwork, civil3d_pressurepipenetwork, civil3d_parcel,
civil3d_catchment, civil3d_featureline, civil3d_samplelinegroup,
civil3d_pointgroup, civil3d_cogopoint, civil3d_surveyfigure
For each DRef object found, report:
DRef Name (object name)
Object Type (surface | alignment | profile | corridor | etc.)
isReferenceObject (must be true — confirms it is a DRef)
isReferenceStale (true = out of date; false = current)
Source Drawing Path (the .dwg the data shortcut points to)
Data Shortcut Folder (project _Shortcuts folder path)
Sync Status (Up to Date | Out of Date | Broken | Not Found)
Parent Drawing (which .dwg holds this DRef)
Source Object Exists (can the source drawing and named object be found)
FLAG RULES — apply to every DRef row:
❌ isReferenceStale = true AND source drawing not found → Broken DRef
❌ Source drawing path resolves to a file that no longer exists
❌ Source drawing exists but the named object no longer exists within it
❌ Data Shortcut XML entry exists but points to a deleted/renamed .dwg
⚠️ isReferenceStale = true but source exists → Out of date; needs sync
⚠️ Source drawing is itself an XRef in another drawing → Mixed
XRef/DRef dependency (see Section 4)
⚠️ Source drawing path is relative or uses mapped drive
⚠️ Multiple DRefs point to the same source object from different drawings
→ Redundant reference risk
✅ isReferenceObject = true, isReferenceStale = false, source found → OK
Output format — one row per DRef per drawing it appears in:
| DRef Name | Object Type | Stale | Source Drawing | Shortcut Folder |
Sync Status | Parent Drawing | Source Exists | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 3 — OTHER REFERENCE HEALTH
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Check all non-DWG, non-DRef external references in the root drawing AND in
every drawing reachable via the XRef tree. Query each type separately:
TYPE A — PDF Underlays (pdfunderlaydefinition)
TYPE B — DWF/DWFx Underlays (dwfunderlaydefinition)
TYPE C — DGN Underlays (dgnunderlaydefinition)
TYPE D — Raster Images (rasterimagedefinition)
Includes: JPG, PNG, TIF, BMP, ECW, SID, IMG
TYPE E — Point Clouds (pointclouddefinitionex)
Includes: RCP, RCS (ReCap format only)
Note: Legacy PCG/FLT formats not queryable
TYPE F — Data Links (datalinkdefinition)
Includes: Excel XLSX/XLS, OLE objects
Check: isValid field and connectionString path
For each reference found, report:
Reference Name (itemName or name field)
File Type (PDF | DWF | DGN | Raster | Point Cloud | DataLink)
Source File Path (sourceFileName as stored)
Active File Path (activeFileName — resolved path)
Load Status (Loaded | Unloaded | Not Found)
Clipping Active (Yes | No — if clipping boundary is applied)
Parent Drawing (which .dwg holds this reference)
For Data Links only: dataAdapterId, isValid, connectionString
FLAG RULES:
❌ isLoaded = false AND activeFileName is null → File not found / broken
❌ isValid = false (Data Links) → Excel connection broken
❌ sourceFileName ≠ activeFileName → Path mismatch
⚠️ isLoaded = false but file exists → Manually unloaded
⚠️ Path uses mapped drive or relative path → Fragile reference
⚠️ Point cloud file size = 0 or totalPointsCount = 0 → Empty or corrupt
✅ Loaded, paths match, file accessible → Healthy
Output format — one table per reference type, one row per reference:
| Reference Name | File Type | Source Path | Active Path | Status |
Clipping | Parent Drawing | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 4 — XREF CIRCULAR LOOP DETECTION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Using the complete XRef tree built in Section 1, perform a full directed graph
cycle detection analysis. Treat each drawing file path as a node and each XRef
relationship as a directed edge: A → B means "Drawing A references Drawing B".
Algorithm:
Build the full directed adjacency list from all XRef relationships found
Run Depth-First Search (DFS) with a visited + recursion-stack tracker
For every back-edge detected (node already on the current DFS stack),
record the full cycle path
Deduplicate cycles (A→B→A and B→A→B are the same loop)
Report every unique loop found
For each loop detected, report:
Loop ID (Loop 1, Loop 2, etc.)
Full Chain (DrawingA.dwg → DrawingB.dwg → DrawingC.dwg
→ DrawingA.dwg)
Loop Length (number of drawings in the cycle)
Attachment Types (list the Attachment/Overlay type of each edge)
Active Loop (Yes = all edges are Attachment type and resolved;
No = at least one edge is Overlay or unresolved)
Risk Level (Critical | High | Medium)
Critical = all Attachment, all resolved
High = mixed types, at least one Attachment
Medium = all Overlay (does not propagate but
still a structural issue)
FLAG RULES:
❌ Active Loop with all Attachment edges → Will cause AutoCAD load failure
❌ Loop involves the root drawing directly → Immediate load risk
⚠️ Loop involves Overlay edges only → Structural issue, lower runtime risk
⚠️ Loop detected in nested drawings not directly attached to root →
Latent risk if attachment types change
✅ No loops detected in any branch of the XRef tree
Output format:
| Loop ID | Full Chain | Length | Edge Types | Active | Risk | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 5 — DREF CIRCULAR LOOP DETECTION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Using the complete DRef map built in Section 2, perform a directed graph cycle
detection analysis on the Civil 3D data reference dependency chain.
Treat each drawing file path as a node. A directed edge A → B means
"Drawing A contains a DRef whose source is Drawing B" (i.e., A consumes
data published by B).
Algorithm: same DFS cycle detection as Section 4.
For each DRef loop detected, report:
Loop ID
Full Chain (DesignDwg.dwg → SourceDwg.dwg → DesignDwg.dwg)
Object Types Involved (which Civil 3D object types are in the loop:
surface, alignment, corridor, etc.)
Loop Length
Stale Edges (how many DRef edges in the loop are stale)
Risk Level (Critical | High | Medium)
Critical = loop is fully resolved and active
High = loop involves corridor or surface objects
Medium = loop involves labels or annotation only
FLAG RULES:
❌ Fully resolved DRef loop → Civil 3D will fail to regenerate correctly
❌ Loop involves corridor or surface consuming its own source data
⚠️ Loop involves stale DRefs → May not be active yet but will trigger
on next sync
⚠️ Loop chain length > 3 → Complex dependency; hard to untangle
✅ No DRef loops detected
Output format:
| Loop ID | Full Chain | Object Types | Length | Stale Edges | Risk | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 6 — MIXED XREF / DREF LOOP DETECTION
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
This is the most complex and dangerous loop type. A mixed loop occurs when
a cycle exists across BOTH XRef and DRef edges in the same dependency chain.
Example of a mixed loop:
DesignDwg.dwg ──[XRef]──► SurveyDwg.dwg
SurveyDwg.dwg ──[DRef]──► DesignDwg.dwg (references a surface from it)
→ LOOP: DesignDwg → SurveyDwg → DesignDwg (mixed XRef + DRef edges)
Build a UNIFIED dependency graph combining:
All XRef edges from Section 1 (directed: host → referenced)
All DRef edges from Section 2 (directed: consumer → source)
Label each edge with its type: [XRef-Attachment], [XRef-Overlay], or [DRef].
Run DFS cycle detection on the unified graph.
For each mixed loop detected, report:
Loop ID
Full Chain with edge types annotated:
DrawingA.dwg ──[XRef-Attachment]──► DrawingB.dwg
──[DRef: Surface]──► DrawingA.dwg
Loop Length
Edge Type Breakdown (how many XRef-Attachment / XRef-Overlay / DRef
edges are in the loop)
Object Types in DRef edges (surface, alignment, corridor, etc.)
Active Loop (Yes | No — all edges resolved and non-stale)
Risk Level (Critical | High | Medium | Low)
Critical = XRef-Attachment + active DRef in loop
High = XRef-Overlay + active DRef in loop
Medium = any stale DRef in loop
Low = all edges unresolved or unloaded
FLAG RULES:
❌ Mixed loop with XRef-Attachment + active DRef → Highest severity;
will cause both AutoCAD load failure AND Civil 3D regen failure
❌ Mixed loop where root drawing is a node → Immediate project risk
❌ Mixed loop involving corridor or surface DRefs → Data corruption risk
⚠️ Mixed loop with XRef-Overlay + DRef → Does not propagate via XRef
but DRef cycle will still cause Civil 3D regen issues
⚠️ Mixed loop detected but all DRefs are stale → Latent risk on sync
⚠️ Mixed loop chain length > 4 → Extremely difficult to resolve manually
✅ No mixed loops detected
Output format — annotated chain per loop:
| Loop ID | Annotated Chain | Length | XRef Edges | DRef Edges |
Object Types | Active | Risk | Issues |
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
SECTION 7 — OVERLAY vs. ATTACHMENT PROPAGATION ANALYSIS
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
For every XRef in the full tree (all nesting levels), analyse whether its
Attachment type creates a propagation risk when this drawing is itself used
as an XRef by a parent drawing.
Report:
Drawing Name
Attachment Type of this XRef edge
Does this drawing appear as an XRef in any other drawing? (Yes | No)
If Yes: what is the parent drawing, and what type is that edge?
Propagation Chain: list the full upward chain to the root
Will this XRef be visible in the root drawing? (Yes = Attachment
propagates; No = Overlay stops here)