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 BatchSave not working
- could not lookup table in dynamodb
- dynamodb could not instantiate class
- dynamodb query is null
- dynamodb number_value cannot be converted to string
- DynamoDB - The Security Token Included In The Request Is Invalid
- can't pickle thread.lock objects typeerror boto3 python dynamodb
- dynamodb does not support null values
- error dynamodb streams must be enabled on the table
- DynamoDB Delete Not Working
- dynamodb query not returning the full item
- DynamoDB Expression Not Null
- DynamoDB Local Docker Not Working
- dynamodb list_append if_not_exists not working
Tired of switching accounts and regions? Use Dynobase.
First 7 days are on us. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2025 Dynobase