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 scan does not return all items
- AWS DynamoDB CredentialsError: Missing credentials in config
- DynamoDB Update Not Working
- dynamodb can not resolve withkeyconditionexpression
- Boto3 DynamoDB KeyError
- DynamoDB Errors InvalidSignatureException Signature Expired
- sls dynamodb install not working
- CORS Error DynamoDB
- aws.dynamodb.documentclient is not a constructor
- dynamodb attribute does not exist
- DynamoDB Delete Not Working
- dynamodb no range key value present
- dynamodb scan missing values
- ExpressionAttributeValues contains invalid value: One or more parameter values were invalid: An AttributeValue may not contain an empty string
- DynamoDB FilterExpression Not Working
Better DynamoDB experience.
Try 7-day free trial. No strings attached.
Product Features
DynamoDB Tools
DynamoDB Info
© 2024 Dynobase