Node

When you select a node object in a derived property expression or a sourceNode object in a property transformation expression, you can select node attributes depending on the data type of the node object:

• AllAncestors: All ancestor node objects, combined from all node locations, in the node set. For attributes, see Node List.
• Ancestors: Ancestor node objects for a node instance in the node set. For attributes, see Node List.
• BoundAncestors: In hierarchy set bound viewpoints, returns a list of ancestor nodes for a node in the bound viewpoint. In node type bound or unbound viewpoints, returns ancestor node objects for a node instance (the same result as when using Ancestors). For attributes, see Node List.
• BoundLocations: In hierarchy set bound viewpoints, returns a list of locations for a node in the bound viewpoint. In node type bound or unbound viewpoints, returns node locations (the same result as when using Locations). Optional: Enable Exclude Implicit Shares to filter the returned list of bound locations to only node instances under unique parents. For attributes, see Node List.

  Tip:

  Using the bound versions of Ancestors and Locations enables you to access the full scope of the bound viewpoint when using an expression in a maintenance viewpoint.
• Children: Child node objects for a node. For attributes, see Node List.
• CompareTo: Compare two node locations with these options:
  • SAME_LOCATION: Node location is the same as a specified node location
  • SAME_PARENT_AND_NODE: Node location has the same parent as a specified node location
  • SUBSET_LOCATION: Node location has a set of contiguous ancestors that is the same as a specified node location

  Tip:

  This enables you to build an expression that returns different results based on a comparison of node locations. For example, you can derive the value of a Data Storage property as stored or shared based on whether a particular node is the first location in the hierarchy and whether it shares a parent or ancestors with other node locations.

• Dimension: Node dimension. You can select the name attribute.
• HierarchySet: Identifies the hierarchy set of a node in a viewpoint. For a hierarchy set, you can select the name attribute.
• Locations: Node locations (can contain node instances).
  • Optional: Enable Exclude Implicit Shares to filter the returned list of locations to only node instances under unique parents.

  • Optional: Enable Sort to return the locations in the order in which they appear in a hierarchy viewpoint. This allows business logic for shared nodes based on hierarchy order to be implemented. For example, you can create a derived Data Storage property for Planning dimensions which assigns the first member instance a Stored value and other member instances in the hierarchy a Shared value.

  For attributes, see Node List.

• Name: Node name. For attributes, see Strings, Numeric Strings, and Sequences.
• NextSibling: Node sibling after a node in the hierarchy. If this is the last node, then the NextSibling attribute returns Null. The parameters that you can add are:
  • dimension
  • name
  • nodeType
  • properties
• NodeType: Node type for a node. For a node type, you can select the name attribute.
• Parent: Node parent. Parent also has the node data type, which means that you can select other node attributes such as the dimension or the node type of the parent. However, you cannot select the parent of a parent.
• PreviousSibling: Node sibling before a node in the hierarchy. If this is a first node without a previous sibling, then the PreviousSibling attribute returns Null. The parameters that you can add are:
  • dimension
  • name
  • nodeType
  • properties
• Properties: Node properties. For attributes, see Properties.
• Siblings. Sibling node objects for a node instance. For attributes, see Node List.