You are here:
Semantic Model Folder Structure
When you retrieve a model, the extension creates a folder with organized JSON files.
Folder Layout
My_Sales_Model/
├── model.json
├── dataObjects.json
├── relationships.json
├── calculatedDimensions.json
├── calculatedMeasurements.json
├── logicalViews.json
├── dimensionHierarchies.json
├── metrics.json
├── parameters.json
├── modelInfo.json
├── fieldsOverrides.json
├── modelFilters.json
├── groupings.json
└── metadata/
├── orgInfo.json
├── positions.json
└── groups.jsonCore Model Files
model.json— Model metadata including API name, label, and dataspace (required)dataObjects.json— Data Model Objects (DMOs) and Data Lake Objects (DLOs) with dimensions and measurementsrelationships.json— Joins between data objects with cardinality and join conditionsmodelInfo.json— Model permissions and settings
Calculated Fields and Business Logic
calculatedDimensions.json— Dimension fields computed from expressionscalculatedMeasurements.json— Measurement fields with aggregation logicmetrics.json— Business metrics definitionslogicalViews.json— Virtual tables created from HardJoin or Union operations
Navigation and Filters
dimensionHierarchies.json— Drill-down hierarchies for dimensionsparameters.json— User-input variables for calculated fieldsmodelFilters.json— Model-level filter definitionsfieldsOverrides.json— Field-level property overrides
Visualization and Metadata
groupings.json— ERD grouping definitions for visual organizationmetadata/orgInfo.json— Source org tracking informationmetadata/positions.json— Saved ERD node positionsmetadata/groups.json— ERD group configuration
model.json is required. Missing files are treated as empty. Most
files use { "items": [...] } format, except groupings.json,
which uses { "groupings": [...] }, and modelInfo.json, which
is a bare object.