TOM (Tabular Object Model)
Last updated
Last updated
The Tabular Object Model (TOM) offers a programmatic approach to managing administrative tasks, including model creation, data import, refreshing, and role/permission assignments.
TOM provides access to native tabular metadata, such as model, tables, columns, and relationships objects. The object model tree provides an overview of how these components are interconnected.
From a logical standpoint, all tabular objects constitute a tree structure, rooted in a Model descending from Database. It's worth noting that Server and Database aren't strictly tabular because they might represent a multidimensional database on a server operating in Multidimensional mode, or a lower-compatibility tabular model not utilizing tabular metadata for object definitions.
Except for AttributeHierarchy, KPI, and LinguisticMetadata, each child object can be part of a collection. For instance, the Model object contains a collection of Table objects (via the Tables property), where each Table object houses a collection of Column objects, and so forth.
The lowest level descendant in this hierarchy for any parent object is an Annotation object. This object can be employed to optionally expand the schema provided that the necessary code is implemented to manage it.
