Skip to main content
Duplicating, removing, and deleting drivers are different actions. Use duplicate when you want a new independent driver, remove when you only want to clean up the current table, and delete when the driver should leave the model.

​
Duplicating drivers

Duplicating a driver creates a new independent driver with the same formulas, segments, and values as the original. The copy has “Copy” appended to the name, and it has no dependency link back to the original. Any segments from the original driver are copied to the new driver. See Keyboard shortcuts for the duplicate shortcut.
If you often duplicate drivers and swap out logic, consider dimensional modeling in databases instead. It is usually more scalable.
If you want a new driver connected to an existing set of segments, create a driver with the same name, then use the driver context menu to make it a subdriver of the existing segmented set.

​
Removing vs. deleting drivers

  • Remove from block: Removes the driver only from the current view. The driver still exists in Runway, remains available in other blocks, and existing formula references continue to work.
  • Delete: Removes the driver from the model and all tables where it appears. Formulas that reference the deleted driver can break.
Driver context menu with remove and delete actions
Removing a driver from every table does not delete it. These drivers appear in Unlisted Drivers.
Unlisted Drivers page showing drivers not present on a page or model

​
What’s next