SETravis
commented
6 years ago There appears to be an issue in creating the nested write context (ODataSerializerContext) inside of ODataResourceSerializer.WriteComplexAndExpandedNavigationProperty. The write context contains a NavigationSource which is used to determine the NavigationSource of the next nested write context. The first time a nested write context is created the context used to create it points to "user" and contains an 'unknownNavigationPropertyCache' which includes the CreatedBy navigation property. This property is placed into the newly created nested write context. It does not however contain any navigationProperties in the Cache. When the next nested write context is created the NavigationSource of the write context is null which prohibits the 3rd level of "CreatedBy" from be serialized out.
robward-ms
SchlenkR
When attempting to nest more than 2 expands nothing shows up after the first 2. No error is given. I have added [EnableQuery(MaxExpansionDepth = 0)] so not getting an error about exceeding limit.
Assemblies affected
Reproduce steps
A simple example is a User object that has a self referencing "CreatedBy" navigation property.
OData/Users?$expand=CreatedBy($expand=CreatedBy) works as expected returning: User { ... CreatedBy { ... Createdby { ... } } }
Adding another level: OData/Users?$expand=CreatedBy($expand=CreatedBy($expand=CreatedBy)) returns the same result as above without error.
Expected result
The second request should return a third 'CreatedBy" nested under the second.
Actual result
The 3rd expansion level was not serialized.
Additional detail
I saw previous post about making sure any navigation properties were EntitySets. I have used this simple example so there is only one Entity involved which does expand correctly at the first two levels. The actual issue I'm having is more complex and does not involve self references.