Accessing PropertyName@odata.type on TableEntity?
See original GitHub issueUsing Azure.Data.Tables, and pulling TableEntity
objects using TableClient.QueryAsync <T>
, how can we include the property type information on each entity returned?
The RESTful spec defines the property type returned as PropertyName@odata.type
- how is that accessible?
Issue Analytics
- State:
- Created 3 years ago
- Comments:10 (5 by maintainers)
Top Results From Across the Web
TableEntity Class (Azure.Data.Tables)
A generic dictionary-like ITableEntity type which defines an arbitrary set of properties on an entity as key-value pairs.
Read more >TableEntity Class (Microsoft.Azure.Cosmos.Table)
Returns a custom entity instance which is recomposed using the specified IDictionary<TKey,TValue> of property names to EntityProperty data typed values.
Read more >Determining the data type of a value from an Azure Storage ...
I need to update the property values of some rows in an Azure Storage Table using Azure.Data.Tables . I use a query to...
Read more >Using the new C# Azure.Data.Tables SDK with ...
In this article, I'll show you how we can perform simple operations against a Azure Cosmos DB Table API account using the new...
Read more >Upgrading a .NET standard 2.0 Azure function using Table ...
using Microsoft.WindowsAzure.Storage.Table; namespace TableUpgrade.Data.Storage { public class FlightSetEntity : TableEntity { public string ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for your feedback. Tagging and routing to the team member best able to assist.
Crap, sorry @christothes - didn’t mean to waste your time with a JSON.NET issue.