Row model is plan's agile driver framework for building driver-based planning models. It transforms the rows in a planning sheet into dynamic planning elements called drivers. Instead of depending on a complex semantic model or prebuilt measures, a row model lets you build planning logic directly in the planning layer.
A row model uses a single row hierarchy, where each member in the hierarchy becomes a potential driver. Typical row hierarchies include:
Key concept: Every row is a potential driver.
Each driver can represent an input, calculation, subtotal, or business outcome. You define relationships between rows by using formulas and aggregations to create a connected planning model.
A row model starts with a row hierarchy that represents the planning dimension. Every member in that hierarchy becomes a planning driver.
For example, a single row hierarchy can contain the following rows:
Each row acts as an individual driver. You can define formulas and relationships between these rows so that changes to one driver automatically update the related business outcomes. The row hierarchy is usually evaluated across planning versions (such as Actual and Forecast), business KPIs, and other scalar measures.
Unlike traditional spreadsheet models that distribute formulas across multiple cells, a row model organizes planning logic into a connected hierarchy of rows, making it easier to maintain and extend.
A row model is ideal for organizations that use lightweight semantic models, such as flat tables, star schemas, or row transactional views, but need sophisticated planning logic.
Because the planning logic resides in the planning layer, you don't need a complex semantic model or numerous calculated measures in the underlying database.
A row model provides the following benefits:
Use row models for the following use cases:
