OpenUI5 Documentation Update 18.10.2024

SAP · Oct 18, 2024 · 093fb7b · 093fb7b
1 parent e517198
commit 093fb7b
Show file tree

Hide file tree

Showing 7 changed files with 370 additions and 352 deletions.
diff --git a/docs/Data_Aggregation_and_Recursive_Hierarchy_7d91431.md b/docs/Data_Aggregation_and_Recursive_Hierarchy_7d91431.md
@@ -31,7 +31,7 @@ For every aggregatable property, you can provide the name of the custom aggregat
 
 `CASE WHEN min(Unit) = max(Unit) THEN min(Unit) END` 
 
-Normally, there is also a structural property of the same name as the custom aggregate, providing type information, etc.
+Normally, there is also a structural property of the same name as the custom aggregate, providing type information, etc. In case of a multi-unit situation, [`v4.Context#getFilter`](https://sdk.openui5.orgapi/sap.ui.model.odata.v4.Context%23methods/getFilter) may be helpful to send a request for more details.
 
 The following client-side instance annotations can be used to access a node level or expansion state. For property bindings, a syntax like `{= %{@$ui5.node.level} }` is usually helpful, because automatic type determination is not available.