Garrett DeBruin

@MScheleo, I was trying to go through point-by-point, but I think maybe there are fewer questions if I try to address the biggest confusion. Moving `unknownFutureValue` is a breaking change....

We need to make sure that the client can handle these responses before supporting this on the service side.

Can we make sure to also create the other issues where needed?

Glad this worked for you @spencershoell, I'm going to re-open so that we can avoid future consumers from needing to use the same workaround.

Thanks @julealgon, I wasn't intending to leave it open forever, but instead to address the fact that the intended design leaves consumers of the library confused after taking a natural...

After working through the issue and discussing with the team, I have created [this](https://github.com/OData/AspNetCoreOData/issues/653) issue to track instead, since the change requires some additional feature work in a couple of...

Sam sent me [this](https://github.com/OData/AspNetCoreOData/blob/main/src/Microsoft.AspNetCore.OData/Extensions/ActionModelExtensions.cs#L92) pointer for when the routes are built, I will look at what updates we can make so that this is more intuitive in the future. The...

@austinheinrichs , this is a really great idea. I am working on what this would look like for our next big release, and I'm running into two possible issues: 1....

1. From triage, we decided that both test cases should pass 2. Sam suggested adding `[FromODataUri]` to the parameter in the controller method to get the deserialization to work correctly

Hi @cxc256, can you please share your CSDL for this? If `personAttribute` is not a contained navigation property, then maybe the issue is that there is a missing navigation property...