acad-database-operations

Copy layers, blocks, and symbol-table records between Civil 3D/AutoCAD databases.

3|Updated Feb 17, 2026
One-click install
npx skills add https://github.com/hebackus/c3d-api-plugin --skill acad-database-operations
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acad-database-operations
Source: https://github.com/hebackus/c3d-api-plugin/tree/main/skills/acad-database-operations
Command: npx skills add https://github.com/hebackus/c3d-api-plugin --skill acad-database-operations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enables reliable cross-database copying, migration, and synchronization of Civil 3D/AutoCAD objects across multiple drawings and databases.

Core Features & Use Cases

  • WblockCloneObjects-based cross-database transfers with an IdMapping for matching old-to-new ObjectIds.
  • DeepCloneObjects for copying objects within a single database, and symbol-table-aware cloning for layers, blocks, and records.
  • Support for DuplicateRecordCloning choices (Ignore, Replace, XrefMangleName, MangleName) to manage name collisions during cross-database operations.
  • Side database pattern for batch processing, auditing, and safe migration without affecting the active document.
  • Database.Purge to remove unused records, and Database.Audit to repair errors and maintain consistency.
  • Use cases include importing external drawings, migrating drawings between projects, and consolidating symbol tables across drawings.

Quick Start

Configure a source database and a destination database, then call WblockCloneObjects with the selected object IDs to migrate entities across drawings.

Frequently Asked Questions about acad-database-operations

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I copy objects between Civil 3D drawings without opening them?▼

WblockCloneObjects performs cross-database transfers using an IdMapping to match old-to-new ObjectIds, while DeepCloneObjects copies objects within a single database using symbol-table-aware cloning for layers, blocks, and records.

What's the best way to handle name collisions when migrating AutoCAD layers?▼

You can configure DuplicateRecordCloning choices including Ignore, Replace, XrefMangleName, and MangleName to manage name collisions and resolve conflicts during cross-database migration operations.

How do I safely migrate Civil 3D symbol tables across multiple databases?▼

Consolidate symbol tables across drawings by configuring a source and destination database, then calling WblockCloneObjects with selected object IDs to migrate layers, blocks, and symbol-table records with proper transaction management.

Why do I need IdMapping for AutoCAD cross-database object cloning?▼

IdMapping is required for cross-database copies to translate IDs and match old-to-new ObjectIds, ensuring references between migrated layers, blocks, and symbol-table records remain intact during WblockCloneObjects operations.

When should I use DeepCloneObjects instead of WblockCloneObjects for AutoCAD data?▼

Use DeepCloneObjects to copy objects within a single AutoCAD database, whereas WblockCloneObjects is required for inter-drawing migration and cross-database transfers across side databases and main drawings.

Can I purge unused records and audit errors during a Civil 3D database migration?▼

You can use Database.Purge to remove unused records and Database.Audit to repair errors and maintain consistency during side database batch processing, auditing, and safe migration operations.