Skip to content

Commit 940da66

Browse files
fix: added warning
1 parent 31bf6d1 commit 940da66

File tree

1 file changed

+6
-2
lines changed

1 file changed

+6
-2
lines changed

sml-reference/composite-model.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,7 @@
33
Composite models are made up of multiple other models that all share a dimension, as well as calculations specific to the composite model itself. They are defined by `composite_model` files in SML.
44

55
When you deploy a composite model, all of its referenced objects are deployed as a single model. Note, however, that deployed composite models do not include the following objects from their referenced models:
6+
67
- Partitions
78
- Perspectives
89
- Drill-throughs
@@ -15,7 +16,7 @@ object_type: composite_model
1516
label: TPCDS - Composite
1617
description: This is a composite model that combines TPC-DS subject-area models.
1718

18-
models:
19+
models:
1920
- TPC-DS Catalog Sales
2021
- TPC-DS Inventory
2122
- TPC-DS Store Promotion
@@ -119,6 +120,9 @@ The `metrics` property supports the following properties:
119120
- **Type:** array
120121
- **Required:** N
121122

123+
> [!WARNING]
124+
> Any UDA's defined on the models referenced by the composite will not be used. They will not be automatically added
125+
122126
The `aggregates` property in a composite model file enables you to add
123127
user-defined aggregates (UDAs).They include metrics or attributes from different
124128
models within the composite model.
@@ -222,4 +226,4 @@ Supported properties:
222226
- `distribution`: String, optional. The distribution keys to use when
223227
creating the aggregate table. If your aggregate data warehouse
224228
supports distribution keys, then the semantic engine uses the specified keys when
225-
creating the aggregate table.
229+
creating the aggregate table.

0 commit comments

Comments
 (0)