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)
- dynamodb is abstract cannot be instantiated
- dynamodb could not connect to the endpoint url
- DynamoDB BatchSave not working
- DynamoDB table not updating
- dynamodb update fail if not exists
- dynamodb the parameter cannot be converted to a numeric value
- DynamoDB console unable to delete this item
- dynamodb-admin not working
- DynamoDB Mapper Could Not Instantiate Class
- DynamoDB ConditionalCheckFailedException
- DynamoDB is missing the key id in the item
- error updating dynamodb table time to live
- KMS Key Access Denied Error DynamoDB
- dynamodb 1 validation error detected value
- DynamoDB query is slow
Tired of AWS Console? Try Dynobase.
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2026 Dynobase