Error: dynamodb unable to locate property for key attribute

Answered by Rafal Wilinski
Last updated: October 23rd, 2026
Solution
“Unable to locate property for key attribute” comes from the .NET DynamoDB object persistence model when it cannot map a table key attribute to a model member. It does not mean the item is missing. Compare the model’s mapping with the table’s KeySchema.
using Amazon.DynamoDBv2.DataModel;
[DynamoDBTable("Orders")]
public class Order
{
[DynamoDBHashKey("pk")]
public string PartitionKey { get; set; } = "";
[DynamoDBRangeKey("sk")]
public string SortKey { get; set; } = "";
}This example maps CLR property names to table attributes pk and sk. Keep both properties readable and writable, and use types matching the actual key types. Check overridden table names, index mappings, ignored members, and inherited properties when the error names a different attribute.
Current .NET SDK code can construct its context with DynamoDBContextBuilder; ensure the model or explicit table metadata supplies the required keys. Adding a random attribute to the stored item will not repair missing client-side mapping metadata.
See key value types and AWS SDK mapping source.
Other Common DynamoDB Errors (with Solutions)
- dynamodb system errors metric
- dynamodb unable to locate credentials
- DynamoDB GetItem no item
- dynamodb is abstract cannot be instantiated
- DynamoDB local error unable to access JAR file dynamodblocal.jar
- Unable to start DynamoDB Local process
- ConfigError: Missing region in config
- dynamodb does not accept empty set
- name key is not defined dynamodb
- dynamodb cannot read property '0' of undefined
- DynamoDB string set may not be empty
- AWS CLI DynamoDB Error Parsing Parameter
- DynamoDB No Provisioned Throughput specified for the table
- dynamodb number_value cannot be converted to string
- dynamodb-admin is not recognized as an internal or external command
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today