Fix for issue: CosmosDB to CosmosDB doesn't migrate "Id" field #100

AzureCosmosDB / data-migration-desktop-tool

MIT License

122 stars 46 forks source link

Fix for issue: CosmosDB to CosmosDB doesn't migrate "Id" field #100 #116

Closed adambarath closed 5 months ago

adambarath commented 6 months ago

Those who are using EntitFrameworkCore CosmosDb provider it is very important to make a difference between 'id' and 'Id' field on JSON objects. This fix handles it. I ran unit tests, all passed.

Reported Issue: https://github.com/AzureCosmosDB/data-migration-desktop-tool/issues/100

adambarath commented 5 months ago

Kindly ping.

bowencode commented 5 months ago

The existing behavior is as designed for the normal use case where some id field exists and the expectation is that it will be used as the string "id" required by Cosmos DB, and simply changing the default casing handling would break that. An additional settings option can be used to change the behavior to what you're requesting though.