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: graph/articles/coreTypes.md
+44-4
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,8 @@ The following types are identified as core types, and will require strong justif
19
19
Instead of adding a structural property to the existing type (`user`, `group` or `device`), create a new type that models the information captured in the proposed structural property(s).
20
20
Then, do one of the following:
21
21
- Add a navigation property on the existing type to the new type, containing the new type.
22
-
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
23
22
- Contain the new type in an entity set elsewhere, and add a navigation property to the new type on the existing type.
23
+
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
24
24
25
25
## Example:
26
26
@@ -39,19 +39,59 @@ Don't add new properties to core types such as `user`.
39
39
40
40
### Do:
41
41
42
-
First, create a new type that models the information captured in the desired structural property(s).
42
+
Do one of the following:
43
43
44
+
#### Add a navigation property on the existing type to the new type, containing the new type.
45
+
46
+
Define the new entity type:
44
47
```xml
45
48
<EntityTypename="bankAccountInformation">
46
49
<PropertyName="accountNumber"Type="Edm.string"/>
47
50
<PropertyName="routingNumber"Type="Edm.string"/>
48
51
</EntityType>
49
52
```
50
53
51
-
Then, for example, add a navigation property on the existing type, containing the new type:
52
-
54
+
Add a contained navigation from user to the new entity type:
0 commit comments