Skip to content

Commit

Permalink
@agoerler's suggestion
Browse files Browse the repository at this point in the history
  • Loading branch information
HeikoTheissen committed Feb 21, 2025
1 parent 00badf5 commit 0ae8299
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion vocabularies/Analytics.json
Original file line number Diff line number Diff line change
Expand Up @@ -197,7 +197,7 @@
"$Name": "SiblingOrder",
"$Collection": true,
"$Type": "Analytics.MultiLevelExpandSiblingOrder",
"@Core.Description": "Sort specification to apply to all direct descendants of a given entry in the resulting leveled hierarchy"
"@Core.Description": "Sort specification to apply to all direct descendants of a given entry (so-called siblings) in the resulting leveled hierarchy"
},
{
"$Name": "ShowLevels",
Expand Down
2 changes: 1 addition & 1 deletion vocabularies/Analytics.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Parameter|Type|Description
**[InputSet](Analytics.xml#L213)**|\[EntityType\]|**Binding parameter:** Entity set to be processed
[Levels](Analytics.xml#L216)|\[[MultiLevelExpandLevel](#MultiLevelExpandLevel)\]|Collection of aggregation levels forming a leveled hierarchy<br>Each element in the collection defines the properties that constitute one level. A property must not be referenced by more than one level. The first element in the collection defines the property names of the coarsest level, the following elements define the property names of consecutively finer-grained aggregation levels. The function result is the leveled hierarchy with these levels in preorder, entries on the finest-grained level cannot be expanded further. All referenced properties must be groupable.
[Aggregation](Analytics.xml#L228)|\[String\]|Properties to aggregate for all result entries on all levels<br>All properties in this collection must be custom aggregates.
[SiblingOrder](Analytics.xml#L234)|\[[MultiLevelExpandSiblingOrder](#MultiLevelExpandSiblingOrder)\]|Sort specification to apply to all direct descendants of a given entry in the resulting leveled hierarchy
[SiblingOrder](Analytics.xml#L234)|\[[MultiLevelExpandSiblingOrder](#MultiLevelExpandSiblingOrder)\]|Sort specification to apply to all direct descendants of a given entry (so-called siblings) in the resulting leveled hierarchy
*[ShowLevels](Analytics.xml#L237)*|Int64|*Optional parameter:* Number N of levels to be shown in the initial expansion<br>The initial expansion shows the first N levels as defined in `Levels` (0 ≤ N ≤ length of `Levels`). If this parameter is omitted, all levels are shown.
*[ExpandEntries](Analytics.xml#L247)*|\[[MultiLevelExpandEntry](#MultiLevelExpandEntry)\]|*Optional parameter:* Entries with exceptional expansion
*[SubtotalsAtBottom](Analytics.xml#L253)*|Bool|*Optional parameter:* Whether to duplicate the group headers so that they appear before and after their descendants<br>The entry before has [DrillState](Hierarchy.md#HierarchyType) `expanded`, the entry after has DrillState `subtotal`.
Expand Down
2 changes: 1 addition & 1 deletion vocabularies/Analytics.xml
Original file line number Diff line number Diff line change
Expand Up @@ -232,7 +232,7 @@ $apply=filter(Industry in ('IT','AI'))
</Annotation>
</Parameter>
<Parameter Name="SiblingOrder" Type="Collection(Analytics.MultiLevelExpandSiblingOrder)" Nullable="false">
<Annotation Term="Core.Description" String="Sort specification to apply to all direct descendants of a given entry in the resulting leveled hierarchy" />
<Annotation Term="Core.Description" String="Sort specification to apply to all direct descendants of a given entry (so-called siblings) in the resulting leveled hierarchy" />
</Parameter>
<Parameter Name="ShowLevels" Type="Edm.Int64" Nullable="false">
<Annotation Term="Core.Description" String="Number N of levels to be shown in the initial expansion" />
Expand Down

0 comments on commit 0ae8299

Please sign in to comment.