Handle request in order.

[MitchKuijpers]

Issues

*This pull request fixes issue #762

Description

I tried to find a method to check for the depends on id but could not find one. So the only fix for now would be resolving them in order. This is many times slower, but it's better then it being broken.

Checklist (Uncheck if it is not completed)

• Test cases added
• Build and test with one-click build and test script passed

[MartinTopfstedtSinc]

Does this work? I tried this myself but for some reason it waited inside the Controller for the other requests to finish until it populates the Response to the ChangeSet. (

RESTier/src/Microsoft.Restier.AspNetCore/RestierController.cs

Line 194 in 013bc06

await changeSetProperty.OnChangeSetCompleted().ConfigureAwait(false);

)

[MitchKuijpers]

I'm not sure what you mean by that. I built it with this change and tested it both locally and in our test environment. However, it's really slow now. For that batches, but it works good for a single changeset where I don't want any entities saved when one fails.

That said, even if we want a "good" fix, we should only process the entities that have dependencies in the correct order. But I don't really see the need for this added complexity.

Personally, I would prefer providing a header to make the request asynchronous or perhaps creating two separate endpoints. I'm not entirely confident about what OData expects here. (I believe the standard Microsoft batch handler doesn't process requests in parallel, but what does it do with the dependsOn ID? Nothing?)