Error: DynamoDB aliasing is not supported

Answered by Rafal Wilinski
Last updated: October 23rd, 2026
Solution
DynamoDB supports attribute-name aliases through ExpressionAttributeNames. An “aliasing is not supported” message therefore needs context: SQL-style result renaming and expression placeholders are different features. Do not remove a required alias for a reserved attribute name.
const params = {
TableName: "Orders",
Key: { id: "123" },
ProjectionExpression: "#state",
ExpressionAttributeNames: { "#state": "status" }
};
// SDK v3 GetCommand returns Item.status, not Item.state.An alias substitutes an attribute name inside an API expression; it does not change the attribute name in the returned item. Rename fields in application code when building a response. Map a literal dotted name to one alias, or alias each document-path segment when you intend a nested field.
If the error comes from PartiQL, reproduce the statement using DynamoDB’s documented SELECT syntax without the unsupported alias construct. ExpressionAttributeNames belongs to APIs such as Query and GetItem; it is not a parameter for ExecuteStatement. Without the original statement and client, the exact producer of this wording is not established.
Other Common DynamoDB Errors (with Solutions)
- dynamodb cannot read property 'push' of undefined
- DynamoDB ValidationException: Query condition missed key schema element
- dynamodb stream missing fields
- requested resource not found aws dynamodb
- ConfigError: Missing region in config
- DynamoDB string set cannot be empty
- dynamodb system errors metric
- DynamoDB - The Security Token Included In The Request Is Invalid
- dynamodb table did not stabilize
- error dynamodb streams must be enabled on the table
- DynamoDB scan does not return all items
- dynamodb global secondary index not working
- DynamoDB stream not working
- DynamoDB Internal Server Error
- is not authorized to perform dynamodb:* on resource
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today