dynobase-icon
Dynobase

Error: DynamoDB aliasing is not supported

Rafal Wilinski

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.

See reserved words and aliases and AWS documentation.

Dynobase is a Professional GUI Client for DynamoDB

Start your 7-day free trial today

Product Features

Download
/
Pricing
/
Member Portal
/
Privacy
/
EULA
/
Twitter
© 2026 Dynobase
+
Still using AWS DynamoDB Console?
Try Dynobase to accelerate your DynamoDB workflow. Start your 7-day free trial today.