OData API Explorer Does Not Support Complex Model Substitution

[commonsensesoftware]

The OData API Explorer automatically substitutes types for Swagger integration when they do not exactly match the EDM for the current API version. The current implementation only supports primitive properties.

The following structural properties should be supported:

• Complex Types
• Contained Entity Types
• Navigation Properties

In addition, very complex or deep object graphs might contain multiple sublevels, which should also be supported.

Workaround

The only current, possible workaround is for service authors to create Swagger-specific models that match the EDM for each corresponding API version when the structural type is complex.