🚀 NEW — B45 Library is here. Free, like everything we ship.

    Get it

    Detail Library

    Overview

    Detail Library (also called Detail Sync) keeps drafting views and legends standardized across projects. From a master project you Publish details, stamping each with a stable identity and a published version. On the project side the tool classifies every managed detail against your open masters into five states, then Sync updates the outdated ones in place — the view keeps its Element Id, so its viewport, detail number, and every "5/A-501" reference survive — and Promote pushes a corrected project detail back up into the master. Details are tracked by GUID plus a SHA-256 content hash rather than by name, so a rename never breaks the link.

    Publish

    The authoring side. From the open master project you stamp drafting views and legends with a per-library GUID, a per-detail GUID, a content hash, and a version. Auto only bumps the version when the content hash actually changed, so projects holding an identical detail never flip to Outdated; Manual jumps a detail to a version number you type.

    Check Details & the five states

    Read-first classification against your open masters, evaluated in order: Local (never managed), Orphan (stamped but its GUID is gone from every master), Locally modified (drift — the live content no longer matches the stamp, flagged before version so it is caught as a standards violation), Outdated (behind the master — the swap target), and Up to date. Only Outdated is auto-written; the rest are reported.

    Sync

    Write-first, in place. The checked Outdated details are swapped by clearing the project view's content and copying the master's into the same view, then re-stamping to the new version. A swap that would land nothing rolls back so a view is never emptied, and one bad detail never aborts the batch — the whole run is one undo step.

    Promote

    The reverse of Sync. When a project holds the corrected version, Promote copies its content up into the master in place, bumps the master version, and re-stamps the project to Up to date. The fix made in one project becomes the new library standard that every other project then pulls on its next Sync.

    How to use

    1. Open the Library pane and use the side-rail buttons — Publish, Check Details, Sync Details — with the relevant master document open.
    2. Publish (from the master): pick the drafting views or legends and, per row, choose Auto (bump the version only when the content changed) or Manual (set a version number).
    3. Check Details (in a project): classify local details against every open master to see which are Up to date, Outdated, Locally modified, Orphan, or Local — and export the report.
    4. Sync: update the checked Outdated details to the latest master version, in place.
    5. Promote: push a corrected, locally modified detail back up into the master, bump its version, and re-stamp the project so it reads Up to date again.

    Tips & Notes

    • Masters are discovered from the master documents you have open — and, where configured, from your Library library paths.
    • Because identity is GUID- and hash-based, teams can rename details freely without breaking synchronization.
    • Each face has two tabs — drafting views and legends — so legends ride the exact same publish/check/sync pipeline.

    Limitations

    • Works with drafting views and legends — model views are out of scope.
    • To classify a project, the relevant master must be open (or configured as a library path).