[Copilot]

Why make this change?

REST table mutations for entities in linked data-source-files configs use the root datasource’s metadata, causing HTTP 500 errors. Mutations should work for entities across all configured datasources.

What is this change?

• Select the REST mutation datasource using the target entity’s configured datasource.
• Add a regression test verifying a linked entity uses its linked metadata provider.

How was this tested?

• Integration Tests
• Unit Tests

Sample Request(s)

POST /api/Db2Customers
Content-Type: application/json

{ "Name": "test" }

• Fixes [Bug]: Table writes fail (HTTP 500) for entities defined in a linked data-source-files config #3701

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[Copilot]

🟢 Approval recommended

No active review issues are recorded for the change routing REST mutations through the target entity’s configured datasource.

No open issues 🎉

What changed in this PR

Fixes REST table mutations for entities in linked datasource configurations by selecting the entity’s configured datasource instead of the root datasource, addressing the failure reported in #3701.

Changes:

• Resolve the mutation datasource from the target entity.
• Add a regression test verifying that a linked entity’s DELETE mutation uses the linked metadata provider, not the root provider.

File	Description
src/​Service.Tests/​UnitTests/​SqlMutationEngineHelperTests.cs	Adds regression coverage for linked-datasource mutation routing.
src/​Core/​Resolvers/​SqlMutationEngine.cs	Selects the entity-specific datasource for REST mutations.

_{Review effort: Balanced}