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
+9-8Lines changed: 9 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,12 +16,11 @@ The following types are identified as core types, and will require strong justif
16
16
17
17
## Alternatives to Adding Structural Properties
18
18
19
-
Instead of adding a structural property to an existing type, do the following:
20
-
1. Create a new type that models the information captured in the proposed structural property.
21
-
2. Create a navigation property linking the new type to the existing type, doing one of the following:
22
-
- Contain the new type in an entity set elsewhere, and add a navigation property to the existing type on the new type.
23
-
- Contain the new type in an entity set elsewhere, and add a navigation property to the new type on the existing type.
24
-
- Add a navigation property to the new type on the existing type, containing the new type.
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
+
Then, do one of the following:
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
+
- Contain the new type in an entity set elsewhere, and add a navigation property to the new type on the existing type.
25
24
26
25
## Example:
27
26
@@ -40,16 +39,18 @@ Don't add new properties to core types such as `user`.
40
39
41
40
### Do:
42
41
43
-
Instead, create a new entity modeling the concept that you wish to introduce, and create a navigation property connecting that entity to the desired type.
42
+
First, create a new type that models the information captured in the desired structural property(s).
44
43
45
44
```xml
46
45
<EntityTypename="bankAccountInformation">
47
46
<PropertyName="accountNumber"Type="Edm.string"/>
48
47
<PropertyName="routingNumber"Type="Edm.string"/>
49
48
</EntityType>
49
+
```
50
50
51
-
...
51
+
Then, for example, add a navigation property on the existing type, containing the new type:
0 commit comments