John Gathogo

Hi @KaterynaKateryna. It has been long and I don't know if you're still tracking this issue. I finally got round to thoroughly investigating the issue. I created sample OData services...

Hi @KaterynaKateryna. Did you get a chance to review my latest update on this issue?

I'll go ahead and close this issue. Please go ahead and reopen it if you feel it hasn't been adequately addressed.

@SViradiya-MarutiTech In your scenario, you wouldn't need to create another controller method.

@mansurdegirmenci Like @julealgon pointed out, you need to have an endpoint that is mapped to the `/api/Users/{key}/Photos` route template. If you're using conventional routing and you have a `UsersController` implemented:...

@mansurdegirmenci I'm glad to hear that it worked. You don't need to add the following functions: ```csharp userDto.Function("Get") .ReturnsFromEntitySet("Users") .Parameter("key").Required(); userDto.Function("GetPhotos") .ReturnsFromEntitySet("Users") .Parameter("key").Required(); photoDto.Function("Get") .ReturnsFromEntitySet("Photos") .Parameter("key").Required(); ``` The `Get` and...

Hi @corranrogue9. This issue was created following your review comment here https://github.com/OData/AspNetCoreOData/pull/710#discussion_r986274966 I'd like to know if what you had in mind is 1. an interface containing properties that are...

Thank you @emjotnau for reporting the issue. Could you please confirm if it works in .NET7 and .NET6?

@emjotnau Please also confirm if you were using EF Core or EF6 before it stopped working. It'd help if you can share a repro for us to look at.

Thank you @senioroman4uk for your pull request contribution. It looks like a great optimization. However, I don't know if applying the `Obsolete` attribute to some of the constructors without a...