This begins the Data Tree & Project References section: how the Data tree represents a project, how project references are built, and where the most commonly referenced project values live.
Prerequisites
You can add view frame and component annotations.
Steps
Date tree structure
1.) Understand what the Data tree represents. Project-specific values and objects are created via the DigiPara Liftdesigner Data tree, which represents the project as a text structure — for example, the landing door of Entry1 (the 2nd floor).
Understand what gets a node.
Every component/object and every dimension has its own node.
List objects — such as entrances/landing doors, or rail brackets — each get an individual node.
2.) Understand how major objects and list indexing work. Major objects (e.g. one elevator/shaft, 5 floors, 3 loaded sheets) are represented at the top; list objects always start with index 0.
3.) Understand project references. Project references are built from the names of the selected object and its parents — for example, the car frame object's reference is "Shaft0.Car.Frame.". Object-related references typically end with a dot.
Elevator project value nodes
4.) Know the L_Projects. and L_StandardTab. nodes. Typically referenced project values are located under these nodes.
5.) Know the Shaft. and FLL. nodes. Also commonly referenced — the Shaft. node and the FLL. node.
6.) Edit project specification values via Main Project Data. Values under the L_Projects. node (used mainly in title blocks) can be edited via the Main Project Data… dialog.
Result
You understand how the Data tree represents a project as text, how objects and list items get their nodes, and how project references are built from an object's name and its parents — and you know where to find the most commonly referenced project value nodes and how to edit the ones used in title blocks.
Next Step