Error: dynamodb does not accept empty set
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 index does not exist
- dynamodb put fail if exists
- boto3 dynamodb client error
- DynamoDB VPC endpoint not working
- DynamoDB error cannot find module build/Release/DTraceProviderBindings
- DynamoDB Scan Not Working
- DynamoDB Update Not Working
- DynamoDB stream lambda error
- DynamoDB Expression Not Null
- DynamoDB throttling error
- DynamoDB sorting is not supported for scan expressions
- dynamodb 1 validation error detected value
- ConfigError: Missing region in config
- dynamodb global secondary index not working
- cognitoidentitycredentials is not authorized to perform dynamodb describetable
Tired of switching accounts and regions? Use Dynobase.
Start your 7-day free trial today
Product Features
DynamoDB Tools
DynamoDB Info
© 2023 Dynobase