Error: dynamodb does not accept empty set

Answered by Rafal Wilinski
What's Causing This Error
This used to be an error that occurred before 20th May 2020. However, if you are running into this error in 2022, it is most likely that you are running on an old SDK version, or you have not enabled empty value conversion in the Document Client.
Solution: Here's How To Resolve It
Firstly, upgrade your AWS SDK to the latest version.
npm i aws-sdk@latest
Hereafter, set the convertEmptyValues property to true when initializing an instance of Document Client, as shown below.
const aws = require('aws-sdk');
const documentClient = new aws.sdk.DynamoDb.DocumentClient({
convertEmptyValues: true
});
Other Common DynamoDB Errors (with Solutions)
- One or more parameter values were invalid: some AttributeDefinitions are not used
- CORS Error DynamoDB
- is not authorized to perform dynamodb:* on resource
- dynamodb number_value cannot be converted to string
- dynamodb unable to locate property for key attribute
- Could not connect to the endpoint URL https:dynamodb.singapore.amazonaws.com
- DynamoDB scan does not return all items
- DynamoDB could not invoke null on class
- DynamoDB scan filter not working
- dynamodb query key condition not supported
- DynamoDB Scan Not Working
- ConfigError: Missing region in config
- DynamoDB validation error
- dynamodb the table does not have the specified index
- DynamoDB Errors InvalidSignatureException Signature Expired
Dynobase is a Professional GUI Client for DynamoDB
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase