Overwrites section in full: what overwrites are, what creates a dimension/component/annotation overwrite, and how to scale a single overwrite across many objects using *operations.
Prerequisites
A dynamic dimension exists (horizontal, vertical, or aligned), with a static or parametric x/y/z-offset applied if needed.
Steps
General
1.) Understand what Overwrites are. Every change made to a view frame — annotation changes, component changes, dimension changes — is stored in an Overwrites list. It's essentially a report of everything changed on that view frame, and also offers functions to make the view frame more dynamic so it adapts better to project changes. Each view frame has its own overwrite list.
2.) Open the Overwrites docking window. Activate it via the corresponding item in the View Frame ribbon group.
3.) Understand overwrite naming. An overwrite's name matches the Data tree name of the corresponding object — built from the object's name and its parents', e.g. "Shaft0.Car.Door1.".
4.) Use the Overwrites toolbar, and reset an entry. The toolbar lets you: 1. select the object in the drawing linked to the chosen overwrite entry; 2. copy and paste a selected entry/entries; 3. replace a term in the selected entry/entries (without copying); and 4. switch between entries (highlighted yellow). To reset an overwrite, select it (highlighted yellow) and remove it with the Delete key.
To reset an overwrite, select it (highlighted yellow) and remove it with the Delete key.
Dimension, component, and annotation overwrites
5.) Know what creates a dimension overwrite. For example: deleting a dimension from the view, changing dimension settings, changing extension lines, changing dimension text settings, changing a dimension's position, moving a dimension, changing a dimension prefix, or creating your own dynamic dimension.
6.) Know what creates a component overwrite. For example: deleting a component from the view, changing its presentation or LOD (Dashed, DashDotDot, LOD 100–500, LOD MAX), or enabling extended component dimensions.
7.) Know what creates an annotation overwrite. Adding a component annotation, or adding a view annotation.
*Operations
8.) *Understand what a Operation does. A *Operation lets you assign a single overwrite to all children of a tree-list object, instead of repeating it individually. It works for any object type — dimensions, annotations, BIM components.
9.) Replace the index number with the *Operator. Replace an entry item's index number (e.g. E0) with the *operation form (E*).
10.) *Use the automatic operation functions. One function replaces only the shaft index; another replaces any available index.
11.) Practical example — remove a line from every ceiling. Replace indices individually first, for clarity, then delete the symbol/object with the Delete key or button.
12.) Practical example — a dynamic dimension on every floor level. Add a dynamic dimension in Design Mode by selecting a hole, then replace the index with an asterisk (*) to apply it to every floor level — delete everything after E0, including the dot, in both rows. Repeat the same replacement for the layout entry to match the first dimension's extension line settings.
Extended *Operations
12.) *Use extended operation index references. For more dynamic view frames (e.g. shaft groups), reference an index relative to position rather than a fixed number: *{Last}, *{IndexFromEnd, -2}, or *{IndexFromStart, +3}.
14.) *Combine extended operations. Extended *operations can also be combined — for example *{Bank1} / *{Bank2} — to address more specific combinations across shaft groups.
Result
You understand what the Overwrites list records and how entries are named; you know what everyday actions create a dimension, component, or annotation overwrite; and you can scale a single overwrite across every matching object — a whole shaft, every floor level, or a whole shaft group — using *operations and their extended, position-relative forms.
Next Step