You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/04_Essentials/property-metadata-binding-f5aa4bb.md
+12-2Lines changed: 12 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -27,6 +27,18 @@ The binding must then know the metadata part of the binding expression. The path
27
27
var myLabel =newsap.m.Label({text:"{/#Company/CompanyName/@sap:label}"});
28
28
```
29
29
30
+
To use the absolute binding for a property that doesn't occur in a EnttityType of the default model, the reference to the correct model defined in the manifest can be added as a prefix.
31
+
If you’re not adding the model the framework will tell you in the development console that the mentioned Entity is not present.
32
+
Defining the target model can be done by adding `myModel>` in the beginning of the binding string.
33
+
34
+
35
+
Example:
36
+
37
+
```js
38
+
39
+
var myLabel = new sap.m.Label({text:"{myModel>/#Company/CompanyName/@sap:label}"});
40
+
```
41
+
30
42
- Relative Binding
31
43
32
44
A relative binding path can be resolved relative to a data path/context.
@@ -39,5 +51,3 @@ The binding must then know the metadata part of the binding expression. The path
39
51
var myLabel2 = new sap.m.Label({text:"{City/#@sap:label}"});
0 commit comments