Door Schedule and XREF Overrides in a Hospital Model
A mechanical team maintains a 240-room hospital project as six XREFs: core, north wing, south wing, equipment, ceilings, and site. Each door is a dynamic block with attributes DOOR_NO, WIDTH, FIRE_RATING, and HARDWARE_SET; the door schedule is a table in a separate sheet file that uses data extraction. The XREFs are attached with relative paths to a project folder. After a vendor sends a revised door block, a drafter redefines the block in the source file by inserting the vendor DWG and using ATTSYNC. The schedule now shows 38 blank FIRE_RATING cells, several doors display the default visibility state, and one wing's xref layers lose their halftone settings whenever the file is reloaded. The team also needs to issue a transmittal to the architect, who uses a different drive letter.
1. Diagnose the 38 blank FIRE_RATING cells and describe a safe procedure for updating the door block across all six XREFs.
Read the worked answer
The blank cells are a data problem, not a display problem. Compare the block attribute tags in BATTMAN with the data extraction column names; a tag change or duplicate tag leaves the column unmatched. Check whether the new FIRE_RATING attribute was added with no default; existing inserts will not have a value until populated. ATTSYNC only synchronizes definitions and can reset attribute positions, so test on a copy. Back up the source XREF, open the block in Block Editor, preserve existing tags, add the new attribute with a default, run ATTSYNC, then use ATTEDIT and QSELECT to fill missing values from the door schedule or a controlled LISP. Refresh the extraction table and verify 10 sample doors against the schedule.
2. Explain why xref layer halftone settings are lost on reload and how to make them persistent.
Read the worked answer
VISRETAIN controls whether xref-dependent layer changes in the host are retained when the xref reloads. If it is 0, colors, halftone, lineweights, and on/off/freeze settings revert to the source file. Set VISRETAIN to 1 in each sheet file and save; then reapply the halftone overrides and save a layer state. Keep the source XREF layers unchanged so the architect's copy is predictable. If sheets are produced through a sheet set, confirm the setting in the sheet template, because a new sheet from an old template can reintroduce VISRETAIN=0.
3. What is the safest way to send the six XREFs and schedule to the architect on a different drive letter?
Read the worked answer
Use eTransmit from the sheet file with the XREFs included, and choose Make relative paths or Keep files in folders so the different drive letter does not break links. Include fonts, plot style tables, and the data extraction source; test the package on a machine with a different drive mapping. If the architect only needs to review, send a bound set or PDFs; if they need to edit the door schedule, keep the XREFs live and send the source files. Do not bind before checking that the data extraction table still resolves.