DT_3LD_IMPORT

Beta feature — hidden until an admin turns on Enable 3LD beta in MANAGE_TEMPLATE.

Imports a 3LD netlist — the design tool's machine-readable description of the project's three-line diagram — and validates it against the open drawing: is the netlist well-formed, did the design tool's own pre-checks pass, and does this drawing's block library actually contain every block the diagram needs?

On the ribbon (when the beta is on): JobEngine → Drawing Tools → 3LD Import

It does not place anything yet — placement via the ELDCOMPILE engine is the next phase. Today's command is the pre-flight: it tells you, before any drawing work, exactly what would block the diagram.

Two ways to feed it

When you start the command it asks Loaded session/File:

• Loaded session (default when available) — uses the netlist that LOAD_DT cached from the project session, echoing which revision it is and how old the cache is. Re-run LOAD_DT to refresh. If the cached netlist belongs to a different session than the one stamped on this drawing, the command says so.
• File — pick a netlist JSON exported from the design tool (Step 3's export button). This path works offline and needs no session.

Both paths run the exact same checks.

Reading the report

The report is honest about three different outcomes:

• Refused by the design tool's pre-checks — the netlist itself says it isn't ready (e.g. equipment the block catalog doesn't cover yet). The reasons print verbatim. This is the system working, not an error to work around: the design decided, the drawing just hears about it.
• Drawing can't place it — the netlist is fine but this drawing's block library is missing blocks or appearance variants the diagram needs. The missing-block list doubles as the drafting team's to-do list.
• Ready — every check passed; the diagram is placeable once the placement phase ships.

Prerequisites

The 3LD beta enabled, an open drawing, and either a LOAD_DT-loaded session or an exported netlist file. The Loaded session path needs sign-in (it came from LOAD_DT); the File path doesn't. The ELDCOMPILE drawing engine itself is managed from MANAGE_TEMPLATE's 3LD Engine section.