dynobase-icon
Dynobase

Error: dynamodb converter not found for enhancedtype

Rafal Wilinski

Answered by Rafal Wilinski

Last updated: October 23rd, 2026

Solution

Converter not found for EnhancedType means the Java 2.x Enhanced Client has no conversion rule for a mapped property's Java type. The missing rule may be for a custom class, a collection element or a normal type whose default provider was replaced.

  1. Read the full EnhancedType in the exception, including generic parameters. Avoid raw collection types that hide element information.
  2. For a custom scalar representation, implement AttributeConverter and annotate the getter with @DynamoDbConvertedBy.
  3. For a nested document object, provide a compatible bean or static table schema instead of pretending it is a scalar.
  4. If configuring converterProviders, include DefaultAttributeConverterProvider when ordinary built-in conversions are still needed. An explicit provider list replaces the default chain.
@DynamoDbBean(converterProviders = {
    CustomConverterProvider.class,
    DefaultAttributeConverterProvider.class
})
public class Customer {
    // Public bean properties and key annotations go here.
}

CustomConverterProvider is your AttributeConverterProvider implementation; the default provider is in software.amazon.awssdk.enhanced.dynamodb. Make sure a custom converter can read existing stored values as well as write new ones. A Java v1 @DynamoDBTypeConverted annotation does not configure the v2 Enhanced Client.

See Java mapping and AWS documentation.

Dynobase is a Professional GUI Client for DynamoDB

Start your 7-day free trial today

Product Features

Download
/
Pricing
/
Member Portal
/
Privacy
/
EULA
/
Twitter
© 2026 Dynobase
+
Still using AWS DynamoDB Console?
Try Dynobase to accelerate your DynamoDB workflow. Start your 7-day free trial today.